This is the mail archive of the gcc@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: Building glibc for a mult-lib --target=m68k-linux


Peter,
    Which version of gcc are you using to build glibc? Keep in
mind that with gcc >= 3.1, symbols in libgcc went .hidden. This
may cause you breakage of old binaries when you install the
gcc >= 3.1 built glibc. If you are staying at gcc < 3.1 it
is not an issue. Someone on the m68k arch will need to 
determine if there is a problem with the libgcc symbols on your
arch and if a sysdeps/m68k/libgcc-compat.c needs to be created.
Jakub's description of this process is appended below. If you
explore this issue on m68k, please share your findings...

>Basically, you take the list of libgcc.a (formerly) exported symbols
>and scan all binaries/libraries if they have undefined references to any
>of these symbols (as libc.so exports those on ia32/sparc and a few
>others only, they will not be exported on other arches from libc, thus
>are resolved to some unintentionally exported symbol in some other library
>which is going away after rebuild with 3.2).
>
>        Jakub

Just a heads up on this.
                        Jack


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