Date: Mon, 22 Jun 2015 08:53:03 +0200 From: Dimitry Andric <dim@FreeBSD.org> To: Julian Elischer <julian@FreeBSD.ORG> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: odd compile failure with both clang and gcc.. weird (standard) library install Message-ID: <CF302449-F6D5-44EE-9212-03DC967F91E3@FreeBSD.org> In-Reply-To: <55877C36.70407@freebsd.org> References: <55877C36.70407@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On 22 Jun 2015, at 05:08, Julian Elischer <julian@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? -Dimitry [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.27 iEYEARECAAYFAlWHsNIACgkQsF6jCi4glqMP0QCguAYDj7FVY8spG2XYLwKLgWDC keYAnj4uInqHwzw9LyNPMdAnylPsvqp2 =aJS2 -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CF302449-F6D5-44EE-9212-03DC967F91E3>