Sponsored Content
Operating Systems Solaris Why is gcc missing from </usr/sfw/bin> Post 302554328 by gabam on Sunday 11th of September 2011 01:37:49 PM
Old 09-11-2011
Quote:
Originally Posted by steve701
dude, that's the first thing I tried!! no gcc. i think it was manually removed to prevent development on the machine
Shit, that's was my very first attempt to solve someone's problem on this forum, sorry mate, that was all that I could do. I myself have some problems with my gcc. It is located in /usr/sfw/bin/gcc, but when I try to a compile a c++ hello program, it doesn't compile, giving several errors.
Here is my program, maybe you can lend a hand now.
Code:
 
#include <iostream>
using namespace std;
int main()
{
         cout << "Hello, world!\n";
         return 0;
}

I compile it like this

Code:
 
$ /usr/sfw/bin/gcc hello.cpp -o hello

But it fails!
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

/bin/sh: /usr/bin/vi: No such file or directory when doing crontab

I just set up an ftp server with Red Hat 5.2. I am doing the work, I'm baby stepping, but it seems like every step I get stuck. Currently, I'm trying to set up a crontab job, but I'm getting the following message: /bin/sh: /usr/bin/vi: No such file or directory. I see that vi exists in /bin/vi,... (3 Replies)
Discussion started by: kwalter
3 Replies

2. UNIX for Dummies Questions & Answers

Difference between /bin, /usr/bin, /sbin ?

Hi All, Can somebody tell me the difference between /bin, /usr/bin, /sbin ? Thanx in advance, Saneesh Joseph (3 Replies)
Discussion started by: saneeshjose
3 Replies

3. Solaris

How do I link ld in /usr/ucb/ to /usr/ccs/bin?

Hi all, below is the problem details: ora10g@CNORACLE1>which ld /usr/ucb/ld ora10g@CNORACLE1>cd /usr/ccs/bin ora10g@CNORACLE1>ln -s /usr/ucb/ld ld ln: cannot create ld: File exists ora10g@CNORACLE1> how to link it to /usr/ccs/bin? (6 Replies)
Discussion started by: SmartAntz
6 Replies

4. UNIX for Dummies Questions & Answers

Alias /usr/bin to /bin in profile

Hi! All the basic linux commands, ie. echo, find, etc, are located in /bin. I have a couple of programs that have these commands pointed towards /usr/bin, ie, /usr/bin/echo (even though the actual 'echo' command is in /bin). How can I alias or redirect or link the /usr/bin to /bin just for this... (6 Replies)
Discussion started by: dancerat
6 Replies

5. Red Hat

/usr/bin/find && -exec /bin/rm never work as expected

hi there, Would you able to advise that why the syntax or statement below couldn't work as expected ? /usr/bin/find /backup -name "*tar*" -mtime +2 -exec /bin/rm -f {} \; 1> /dev/null 2>&1 In fact, I was initially located it as in crontab job, but it doesn't work at all. So, I was... (9 Replies)
Discussion started by: rauphelhunter
9 Replies

6. OS X (Apple)

When to use /Users/m/bin instead of /usr/local/bin (& whats the diff?)?

Q1. I understand that /usr/local/bin means I can install/uninstall stuff in here and have any chance of messing up my original system files or effecting any other users. I created this directory myself. But what about the directory I didn't create, namely /Users/m/bin? How is that directory... (1 Reply)
Discussion started by: michellepace
1 Replies

7. Solaris

What is the difference between xpg4/bin and usr/bin?

Hi Experts, I found that the same commands(sort, du, df, find, grep etc.) exists in both dir. What is the difference to use them? i.e: to use xpg4/bin/grep and usr/bin/grep My OS version is SunOS 5.10 Regards, Saps (7 Replies)
Discussion started by: saps19
7 Replies

8. Solaris

How to link sed from /usr/bin/sed to /usr/local/bin/sed?

Hi Guys, OS:- Solaris 10 64Bit I have a small query. On one server a user is facing sed command issue. He gets error regarding sed for this location /users/hoy/2999/batch5/bin/internal.sh: /usr/local/bin/sed: not found How ever the sed is actually present at this location on server:-... (13 Replies)
Discussion started by: manalisharmabe
13 Replies

9. BSD

FreeBSD: /usr/bin/ld not looking in /usr/local/lib

I'm not sure if this is the default behavior for the ld command, but it does not seem to be looking in /usr/local/lib for shared libraries. I was trying to compile the latest version of Kanatest from svn. The autorgen.sh script seems to exit without too much trouble: $ ./autogen.sh checking... (2 Replies)
Discussion started by: AntumDeluge
2 Replies
BLHC(1) 						User Contributed Perl Documentation						   BLHC(1)

NAME
blhc - build log hardening check, checks build logs for missing hardening flags SYNOPSIS
blhc [options] <dpkg-buildpackage build log file>.. DESCRIPTION
blhc is a small tool which checks build logs for missing hardening flags. It's licensed under the GPL 3 or later. It's designed to check build logs generated by Debian's dpkg-buildpackage (or tools using dpkg-buildpackage like pbuilder or the official buildd build logs) to help maintainers detect missing hardening flags in their packages. Only gcc is detected as compiler at the moment. If other compilers support hardening flags as well, please report them. If there's no output, no flags are missing and the build log is fine. OPTIONS
--all Force check for all +all (+pie, +bindnow) hardening flags. By default it's auto detected. --arch architecture Set the specific architecture (e.g. amd64, armel, etc.), automatically disables hardening flags not available on this architecture. Is detected automatically if dpkg-buildpackage is used. --bindnow Force check for all +bindnow hardening flags. By default it's auto detected. --buildd Special mode for buildds when automatically parsing log files. The following changes are in effect: o Print tags instead of normal warnings, see "BUILDD TAGS" for a list of possible tags. o Don't check hardening flags in old log files (if dpkg-dev << 1.16.1 is detected). o Don't require Term::ANSIColor. o Return exit code 0, unless there was a error (-I, -W messages don't count as error). --color Use colored (ANSI) output for warning messages. --ignore-arch arch Ignore build logs from architectures matching arch. arch is a string. Used to prevent false positives. This option can be specified multiple times. --ignore-arch-flag arch:flag Like --ignore-flag, but only ignore flag on arch. --ignore-arch-line arch:line Like --ignore-line, but only ignore line on arch. --ignore-flag flag Don't print an error when the specific flag is missing in a compiler line. flag is a string. Used to prevent false positives. This option can be specified multiple times. --ignore-line regex Ignore lines matching the given Perl regex. regex is automatically anchored at the beginning and end of the line to prevent false negatives. NOTE: Not the input lines are checked, but the lines which are displayed in warnings (which have line continuation resolved). Used to prevent false positives. This option can be specified multiple times. --pie Force check for all +pie hardening flags. By default it's auto detected. -h -? --help Print available options. --version Print version number and license. Auto detection for --pie and --bindnow only works if at least one command uses the required hardening flag (e.g. -fPIE). Then it's required for all other commands as well. EXAMPLES
Normal usage, parse a single log file. blhc path/to/log/file If there's no output, no flags are missing and the build log is fine. Parse multiple log files. The exit code is ORed over all files. blhc path/to/directory/with/log/files/* Don't treat missing "-g" as error: blhc --ignore-flag -g path/to/log/file Don't treat missing "-pie" on kfreebsd-amd64 as error: blhc --ignore-arch-flag kfreebsd-amd64:-pie path/to/log/file Ignore lines consisting exactly of "./script gcc file" which would cause a false positive. blhc --ignore-line './script gcc file' path/to/log/file Ignore lines matching "./script gcc file" somewhere in the line. blhc --ignore-line '.*./script gcc file.*' path/to/log/file Use blhc with pbuilder. pbuilder path/to/package.dsc | tee path/log/file blhc path/to/file || echo flags missing BUILDD TAGS
The following tags are used in --buildd mode. In braces the additional data which is displayed. I-hardening-wrapper-used The package uses hardening-wrapper which intercepts calls to gcc and adds hardening flags. The build log doesn't contain any hardening flags and thus can't be checked by blhc. W-compiler-flags-hidden (summary of hidden lines) Build log contains lines which hide the real compiler flags. For example: CC test-a.c CC test-b.c CC test-c.c LD test Most of the time either "export V=1" or "export verbose=1" in debian/rules fixes builds with hidden compiler flags. Sometimes ".SILENT" in a Makefile must be removed. And as last resort the Makefile must be patched to remove the "@"s hiding the real compiler commands. W-dpkg-buildflags-missing (summary of missing flags) CPPFLAGS, CFLAGS, CXXFLAGS, LDFLAGS missing. I-invalid-cmake-used (version) By default CMake ignores CPPFLAGS thus missing those hardening flags. Debian patched CMake in versions 2.8.7-1 and 2.8.7-2 to respect CPPFLAGS, but this patch was rejected by upstream and later reverted in Debian. Thus those two versions show correct usage of CPPFLAGS even if the package doesn't correctly handle them (for example by passing them to CFLAGS). To prevent false negatives just blacklist those two versions. I-no-compiler-commands No compiler commands were detected. Either the log contains none or they were not correctly detected by blhc (please report the bug in this case). EXIT STATUS
The exit status is a "bit mask", each listed status is ORed when the error condition occurs to get the result. 0 Success. 1 No compiler commands were found. 2 Invalid arguments/options given to blhc. 4 Non verbose build. 8 Missing hardening flags. 16 Hardening wrapper detected, no tests performed. 32 Invalid CMake version used. See I-invalid-cmake-used under "BUILDD TAGS" for a detailed explanation. AUTHOR
Simon Ruderich, <simon@ruderich.org> Thanks to to Bernhard R. Link <brlink@debian.org> and Jaria Alto <jari.aalto@cante.net> for their valuable input and suggestions. COPYRIGHT AND LICENSE
Copyright (C) 2012 by Simon Ruderich This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>. SEE ALSO
hardening-check(1), dpkg-buildflags(1) perl v5.14.2 2012-06-27 BLHC(1)
All times are GMT -4. The time now is 11:51 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy