gcc issue

  • Follow


Hi everyone.

Gcc has just started acting really funny on me. I am using
gcc --ver
Using built-in specs.
Configured with: FreeBSD/i386 system compiler
Thread model: posix
gcc version 3.2.2 [FreeBSD] 20030205 (release)

on FreeBSD 5.1

The problem is when users on the system try to compile any c program the 
get the error message

/usr/bin/ld: cannot find -lgcc

Does anyone know what causes this, I have searched google groups, but it 
seems that all references to this are for windows machines and lcc.
-- 
Materialised

Please note the email address this message uses in its headers is a spam 
trap.
If you wish to contact me, you can do so at the following address:
bWlja0Bjb2RlZ3VydXMub3Jn
0
Reply Materialised 1/19/2004 12:31:54 AM

Materialised <materialised@privacy.net> writes:

> Gcc has just started acting really funny on me. I am using

Did you move it from where it was installed to some other place?

> Using built-in specs.

I think that means it can't find its specs file in the place where
it is looking for it.

> /usr/bin/ld: cannot find -lgcc

That library is normally deep in the gcc install tree, e.g.
/usr/lib/gcc-lib/i486-suse-linux/2.95.3/libgcc.a

Run 'gcc -v foo.o' and look at the -L/... directives it passes to
the linker. Chances are these directories have disappeared.

> If you wish to contact me, you can do so at the following address:
> bWlja0Bjb2RlZ3VydXMub3Jn

How are we supposed to use the address above?

Cheers,
-- 
In order to understand recursion you must first understand recursion.
Remove /-nsp/ for email.
0
Reply Paul 1/19/2004 12:50:32 AM


In article <buf8i1$h06ik$1@id-220437.news.uni-berlin.de>,
	Materialised <materialised@privacy.net> writes:
> 
> The problem is when users on the system try to compile any c program the 
> get the error message
> 
> /usr/bin/ld: cannot find -lgcc
> 
> Does anyone know what causes this, I have searched google groups, but it 
> seems that all references to this are for windows machines and lcc.

Do you have these libraries

/usr/lib/libgcc.a
/usr/lib/libgcc_p.a
/usr/lib/libgcc_pic.a

What are the permissions on /usr/lib?

-- 
Steve
0
Reply kargl 1/19/2004 12:52:52 AM

Paul Pluzhnikov wrote:
> Materialised <materialised@privacy.net> writes:
> 
> 
>>Gcc has just started acting really funny on me. I am using
> 
> 
> Did you move it from where it was installed to some other place?
> 
> 
>>Using built-in specs.
> 
> 
> I think that means it can't find its specs file in the place where
> it is looking for it.
> 
> 
>>/usr/bin/ld: cannot find -lgcc
> 
> 
> That library is normally deep in the gcc install tree, e.g.
> /usr/lib/gcc-lib/i486-suse-linux/2.95.3/libgcc.a
> 
> Run 'gcc -v foo.o' and look at the -L/... directives it passes to
> the linker. Chances are these directories have disappeared.
> 
> 
>>If you wish to contact me, you can do so at the following address:
>>bWlja0Bjb2RlZ3VydXMub3Jn
> 
> 
> How are we supposed to use the address above?
> 
> Cheers,
I havent moved it, it think ts a permissions issue to be hionest, as gcc 
works fine as root, and fine under my own personal account which is a 
member of the wheel group.
0
Reply Materialised 1/19/2004 12:54:03 AM

Steven G. Kargl wrote:
> In article <buf8i1$h06ik$1@id-220437.news.uni-berlin.de>,
> 	Materialised <materialised@privacy.net> writes:
> 
>>The problem is when users on the system try to compile any c program the 
>>get the error message
>>
>>/usr/bin/ld: cannot find -lgcc
>>
>>Does anyone know what causes this, I have searched google groups, but it 
>>seems that all references to this are for windows machines and lcc.
> 
> 
> Do you have these libraries
> 
> /usr/lib/libgcc.a
> /usr/lib/libgcc_p.a
> /usr/lib/libgcc_pic.a
> 
> What are the permissions on /usr/lib?
> 
I think you might have hit on something there, all file in /usr/lib are 
-r--r--r--

and all the symlinks are

lrwxrwxrwx

Is this right?


-- 
Materialised

Please note the email address this message uses in its headers is a spam 
trap.
If you wish to contact me, you can do so at the following address:
bWlja0Bjb2RlZ3VydXMub3Jn

www.CodeGurus.org
0
Reply Materialised 1/19/2004 1:17:39 AM

Materialised wrote:
> Hi everyone.
> 
> Gcc has just started acting really funny on me. I am using
> gcc --ver
> Using built-in specs.
> Configured with: FreeBSD/i386 system compiler
> Thread model: posix
> gcc version 3.2.2 [FreeBSD] 20030205 (release)
> 
> on FreeBSD 5.1
> 
> The problem is when users on the system try to compile any c program the 
> get the error message
> 
> /usr/bin/ld: cannot find -lgcc
> 
> Does anyone know what causes this, I have searched google groups, but it 
> seems that all references to this are for windows machines and lcc.
Well I have figured out my problem.
I created the login group users in my login.conf with the following 
properties.

user:\
         :passwd_format=md5:\
         :copyright=/etc/COPYRIGHT:\
         :welcome=/etc/motd:\
         :setenv=MAIL=/var/mail/$,BLOCKSIZE=K,FTP_PASSIVE_MODE=YES:\
         :path=/sbin /bin /usr/sbin /usr/bin /usr/games /usr/local/sbin 
/usr/local/bin /usr/X11R6/bin ~/bin:\
         :nologin=/var/run/nologin:\
         :cputime=3h:\
         :datasize=unlimited:\
         :stacksize=unlimited:\
         :memorylocked=unlimited:\
         :memoryuse=20M:\
         :filesize=50M:\
         :coredumpsize=5M:\
         :openfiles=10:\
         :maxproc=10:\
         :sbsize=unlimited:\
         :vmemoryuse=75M:\
         :priority=0:\
         :ignoretime@:\
         :umask=022:

Now members of that group cant access the files needed for gcc.

To fix this should I simply add /usr/lib/ to the path?


-- 
Materialised

Please note the email address this message uses in its headers is a spam 
trap.
If you wish to contact me, you can do so at the following address:
bWlja0Bjb2RlZ3VydXMub3Jn

www.CodeGurus.org
0
Reply Materialised 1/19/2004 1:24:55 AM

In article <bufb80$h2pns$1@id-220437.news.uni-berlin.de>,
	Materialised <materialised@privacy.net> writes:
> Steven G. Kargl wrote:
>> In article <buf8i1$h06ik$1@id-220437.news.uni-berlin.de>,
>> 	Materialised <materialised@privacy.net> writes:
>> 
>>>The problem is when users on the system try to compile any c program the 
>>>get the error message
>>>
>>>/usr/bin/ld: cannot find -lgcc
>>>
>>>Does anyone know what causes this, I have searched google groups, but it 
>>>seems that all references to this are for windows machines and lcc.
>> 
>> Do you have these libraries
>> 
>> /usr/lib/libgcc.a
>> /usr/lib/libgcc_p.a
>> /usr/lib/libgcc_pic.a
>> 
>> What are the permissions on /usr/lib?
>> 
> I think you might have hit on something there, all file in /usr/lib are 
> -r--r--r--
> 
> and all the symlinks are
> 
> lrwxrwxrwx
> 
> Is this right?
> 

Yes.  However, you need the proper permission in /usr

drwxr-xr-x   4 root  wheel  -  8704 Jan 11 09:45 lib/
drwxr-xr-x   9 root  wheel  -   512 Mar 23  2003 libdata/
drwxr-xr-x   8 root  wheel  -  1536 Jan 11 09:44 libexec/

-- 
Steve
0
Reply kargl 1/19/2004 1:28:14 AM

In comp.unix.programmer Materialised <materialised@privacy.net> wrote:
> Materialised wrote:
>> Hi everyone.
>> 
>> Gcc has just started acting really funny on me. I am using
>> gcc --ver
>> Using built-in specs.
>> Configured with: FreeBSD/i386 system compiler
>> Thread model: posix
>> gcc version 3.2.2 [FreeBSD] 20030205 (release)
>> 
>> on FreeBSD 5.1
>> 
>> The problem is when users on the system try to compile any c program the 
>> get the error message
>> 
>> /usr/bin/ld: cannot find -lgcc
>> 
>> Does anyone know what causes this, I have searched google groups, but it 
>> seems that all references to this are for windows machines and lcc.
> Well I have figured out my problem.
> I created the login group users in my login.conf with the following 
> properties.
> 
> user:\
>         :passwd_format=md5:\
>         :copyright=/etc/COPYRIGHT:\
>         :welcome=/etc/motd:\
>         :setenv=MAIL=/var/mail/$,BLOCKSIZE=K,FTP_PASSIVE_MODE=YES:\
>         :path=/sbin /bin /usr/sbin /usr/bin /usr/games /usr/local/sbin 
> /usr/local/bin /usr/X11R6/bin ~/bin:\
>         :nologin=/var/run/nologin:\
>         :cputime=3h:\
>         :datasize=unlimited:\
>         :stacksize=unlimited:\
>         :memorylocked=unlimited:\
>         :memoryuse=20M:\
>         :filesize=50M:\
>         :coredumpsize=5M:\
>         :openfiles=10:\
>         :maxproc=10:\
>         :sbsize=unlimited:\
>         :vmemoryuse=75M:\
>         :priority=0:\
>         :ignoretime@:\
>         :umask=022:
> 
> Now members of that group cant access the files needed for gcc.
> 
> To fix this should I simply add /usr/lib/ to the path?
No.
The PATH-variable sets the search path for executables.
> 
> 

-- 
Ralf Becker           ralf@akk.org 
Arbeitskreis Kultur und Kommunikation / Universitaet Karlsruhe
Paulckeplatz 1        76131 Karlsruhe
Tel 0721/96403-22     Fax 0721/608-4019 
--------------------
0
Reply Ralf 5/10/2004 8:43:20 PM

7 Replies
108 Views

(page loaded in 0.135 seconds)


Reply: