This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Tue, Jun 17, 2003 at 11:01:20PM -0700, Dan Kegel wrote: > Daniel Jacobowitz wrote: > >On Tue, Jun 17, 2003 at 12:56:12PM -0700, Dan Kegel wrote: > > > >>Oddly enough, objdump -p libstdc++.so.5 shows that there is indeed no > >>version info in libstdc++.so.5 built for > >>sh4-unknown-linux-gnu/gcc-3.3-glibc-2.2.5 > >>or sh4-unknown-linux-gnu/gcc-3.3-glibc-2.3.2, though there is version > >>info in that file for the other five architectures I built ... > > > >This generally is a problem with GCC's crappy attempts to autodetect > >features of the cross or target assembler and linker. Read over the > >output of configure and see if anything is looking particularly > >suspicious. > > Thanks for the encouragement. Looks like libstdc++-v3/configure > is setting SYMVER_MAP=config/linker-map.dummy because it sees that > no libgcc_s.so was generated; configure says > checking for shared libgcc... no. > This happened even though I ran gcc's configure with --enable-shared! Oh! I remember this one now. It's been on my list to fix for a while but I never got around to it. That test is broken, period. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |