This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Build gcc-4.8.2 error -- gcc-4.8.1/x86_64-unknown-linux-gnu/libgomp


On Tue, Oct 22, 2013 at 6:42 AM, Andrew Haley <aph@redhat.com> wrote:
> On 10/22/2013 02:00 PM, Ian Lance Taylor wrote:
>> On Mon, Oct 21, 2013 at 11:35 PM, GHui <ugiwgh@gmail.com> wrote:
>>>
>>> -lc (/lib/../lib64/libc.so)
>>
>> /lib64/libc.so is an implausible file on a GNU/Linux system.
>
> No.  It exists on my Red Hat Enterprise Linux system.  It looks like
> this:
>
>  $ cat /lib64/libc.so
> /* GNU ld script
>    Use the shared library, but some functions are only in
>    the static library, so try that secondarily.  */
> OUTPUT_FORMAT(elf64-x86-64)
> GROUP ( /lib64/libc.so.6 /usr/lib64/libc_nonshared.a  AS_NEEDED ( /lib64/ld-linux-x86-64.so.2 ) )


I can tell from the -Wl,-t output posted above that that is not what
the file looks like on GHui's system.  On GHui's system /lib64/libc.so
is a shared library.  That is wrong.  On a GNU/Linux system there
should not be any files named libc.so that are shared libraries.  Any
files named libc.so should be text files similar to what Andrew listed
above.

GHui: the distro provides ways to verify that your system is installed
correctly.  If there is a chance that people have been adding random
symlinks, you should use those tools.

Ian


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]