gcc: `-b' must come at the start of the command line <-- how to fix this error

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Kenneth Klein
> Sent: Wednesday, June 29, 2005 8:46 AM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] gcc: `-b' must come at the start of the
command
> line <-- how to fix this error
> 
> So far I have dl'ed the files and run configure. "make all" ran fine
until
> I ran into this:
> 
> 
> ken at f2sys1
> (1959)[/usr/local/sbin/nagios-2.0b3]# make all
>         cd ./base && make
> Target "all" is up to date.
>         cd ./cgi && make
> Target "all" is up to date.
> Target "cgis" is up to date.
>         cd ./html && make
> Target "all" is up to date.
> Target "html" is up to date.
>         cd ./module && make
>         gcc -g -O2 -DHAVE_CONFIG_H  -o helloworld.o helloworld.c -G -
> bM:SRE -bno
> entry -bexpall
> gcc: `-b' must come at the start of the command line

Details about what hardware, OS and configure line you're compiling
under would probably be in order. You have extra arguments to gcc that
don't exist under linux with ./configure && make all --

cd ./module && make
make[1]: Entering directory `/home/mpowell/nagios-2.0b2/module'
gcc -g -O2 -DHAVE_CONFIG_H -fPIC -o helloworld.o helloworld.c -shared 
make[1]: Leaving directory `/home/mpowell/nagios-2.0b2/module'


--
Marc


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null