On 22 Jun 2015, at 05:08, Julian Elischer <jul...@freebsd.org> wrote:
> Working on -current  as of about March 7.
> /usr/bin/ld: cannot find -lgcc_s
> clang: error: linker command failed with exit code 1 (use -v to see 
> invocation)
> *** Error code 1
> Stop.
> the same error happens with gcc as the compiler..
> so the obvious question is "why does clang want to link with libgcc?"

Because we still use libgcc for some functionality not provided by any
other library.  Yes, we would like to get rid of it.

> and another question is:
> why can't it find  it? At least for that there is an answer:
> julian@vps1:ls -la /usr/lib/libgcc_s.so
> lrwxr-xr-x  1 root  wheel  46 Apr 30 08:13 /usr/lib/libgcc_s.so -> 
> /usr/obj/usr/src-current/tmp/lib/libgcc_s.so.1
> but I've deleted /usr/obj.
> Does anyone know WHY the "make installworld" back in March just made symlinks 
> for this (and a whole bunch more) libraries?
> and has it been fixed?

I built several systems in March, and did not see anything like this.
Maybe it is due tosomething unique to your build environment?  Is it
consistently reproducible?


Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Reply via email to