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]

Re: Undefined symbols at run time for gcc-2.95.3


?= <718D38CAB6E0D011B2C90060970C28A57E1A1D@exchangeserver.pixelpower.com>
MIME-Version: 1.0
Message-Id: <01103023591300.18799@redman>
Content-Transfer-Encoding: quoted-printable

Hi Dave,

I do have a -nostdlib in build.log file:
-------------------------------------------------------------------------=
-----------------
/usr/local/obj/gcc2.95.3-ppc/gcc/xgcc -B/usr/local/obj/gcc2.95.3-ppc/gcc/=
=20
-B/usr/local/crossgcc-2.95.3/ppc/powerpc-wrs-vxworks/bin/=20
-I/usr/local/crossgcc-2.95.3/ppc/powerpc-wrs-vxworks/include -DCROSS_COMP=
ILE=20
-DIN_GCC -DHAIFA    -g -O2 -I./include  -I.=20
-I/usr/local/src/gcc-2.95.3-vxWorks/gcc=20
-I/usr/local/src/gcc-2.95.3-vxWorks/gcc/config=20
-I/usr/local/src/gcc-2.95.3-vxWorks/gcc/../include -msoft-float -mno-eabi=
=20
-mstrict-align -mbig -mcall-sysv -mlongcall -c scrti.S -o tscrti.o
gmake[3]: Leaving directory `/usr/local/obj/gcc2.95.3-ppc/gcc'
gmake[3]: Entering directory `/usr/local/obj/gcc2.95.3-ppc/gcc'
/usr/local/obj/gcc2.95.3-ppc/gcc/xgcc -B/usr/local/obj/gcc2.95.3-ppc/gcc/=
=20
-B/usr/local/crossgcc-2.95.3/ppc/powerpc-wrs-vxworks/bin/=20
-I/usr/local/crossgcc-2.95.3/ppc/powerpc-wrs-vxworks/include -DCROSS_COMP=
ILE=20
-DIN_GCC -DHAIFA    -g -O2 -I./include  -I.=20
-I/usr/local/src/gcc-2.95.3-vxWorks/gcc=20
-I/usr/local/src/gcc-2.95.3-vxWorks/gcc/config=20
-I/usr/local/src/gcc-2.95.3-vxWorks/gcc/../include -msoft-float -mno-eabi=
=20
-mstrict-align -mbig -mcall-sysv -mlongcall -c scrtn.S -o tscrtn.o
gmake[3]: Leaving directory `/usr/local/obj/gcc2.95.3-ppc/gcc'
gmake[2]: Leaving directory `/usr/local/obj/gcc2.95.3-ppc/gcc'
touch stmp-multilib
/usr/local/obj/gcc2.95.3-ppc/gcc/xgcc -B/usr/local/obj/gcc2.95.3-ppc/gcc/=
=20
-B/usr/local/crossgcc-2.95.3/ppc/powerpc-wrs-vxworks/bin/=20
-I/usr/local/crossgcc-2.95.3/ppc/powerpc-wrs-vxworks/include -DCROSS_COMP=
ILE=20
-DIN_GCC -DHAIFA    -g -O2 -I./include     -c=20
/usr/local/src/gcc-2.95.3-vxWorks/gcc/libgcc1-test.c
/usr/local/src/gcc-2.95.3-vxWorks/gcc/libgcc1-test.c:101: warning:=20
conflicting types for built-in function `memcpy'
Testing libgcc1.  Ignore linker warning messages.
/usr/local/obj/gcc2.95.3-ppc/gcc/xgcc -B/usr/local/obj/gcc2.95.3-ppc/gcc/=
=20
-B/usr/local/crossgcc-2.95.3/ppc/powerpc-wrs-vxworks/bin/=20
-I/usr/local/crossgcc-2.95.3/ppc/powerpc-wrs-vxworks/include -DCROSS_COMP=
ILE=20
-DIN_GCC -DHAIFA    -g -O2 -I./include  libgcc1-test.o -o libgcc1-test \
  -nostartfiles -nostdlib `/usr/local/obj/gcc2.95.3-ppc/gcc/xgcc=20
-B/usr/local/obj/gcc2.95.3-ppc/gcc/=20
-B/usr/local/crossgcc-2.95.3/ppc/powerpc-wrs-vxworks/bin/=20
-I/usr/local/crossgcc-2.95.3/ppc/powerpc-wrs-vxworks/include=20
--print-libgcc-file-name`
gcc -c -DCROSS_COMPILE -DIN_GCC -DHAIFA    -g -O2  -DHAVE_CONFIG_H    -I.=
=20
-I/usr/local/src/gcc-2.95.3-vxWorks/gcc=20
-I/usr/local/src/gcc-2.95.3-vxWorks/gcc/config=20
-I/usr/local/src/gcc-2.95.3-vxWorks/gcc/../include=20
/usr/local/src/gcc-2.95.3-vxWorks/gcc/cp/g++spec.c
gcc -DCROSS_COMPILE -DIN_GCC -DHAIFA    -g -O2  -DHAVE_CONFIG_H  -o g++ \
  gcc.o g++spec.o intl.o prefix.o version.o   obstack.o       =20
=2E./libiberty/libiberty.a
=2E./libiberty/libiberty.a(choose-temp.o): In function `choose_temp_base'=
:
/usr/local/src/gcc-2.95.3-vxWorks/libiberty/choose-temp.c:138: the use of=
=20
`mktemp' is dangerous, better use `mkstemp'
rm -f g++-cross
cp g++ g++-cross
rm -f cxxmain.c
ln -s /usr/local/src/gcc-2.95.3-vxWorks/gcc/../libiberty/cplus-dem.c cxxm=
ain.c
-------------------------------------------------------------------------=
-
I will see how this flag is making its way in.




Thanks,
Ernest





On Tuesday 30 October 2001 06:36, David Korn wrote:
> >-----Original Message-----
>
> From: Ernest L. Williams Jr. [mailto:ernesto@ornl.gov]
>
> >Sent: 30 October 2001 04:02
> >
> >
> >Hi Dave,
> >
> >Still trying to use gcc-2.95.3 with vxWorks headers
> >I get some undefined symbols under vxWorks:
> >--------------------------------------------------------------
> >Undefined symbol: __start_cp_handler (binding 1 type 0)
> >Undefined symbol: __eh_rtime_match (binding 1 type 0)
> >Undefined symbol: __eh_alloc (binding 1 type 0)
> >value =3D 28671088 =3D 0x1b57c70
> >---------------------------------------------------------------
> >
> >Dave, have you seen this behavior?  What am I missing in terms of
> >exception handling?
>
>     Hi Ernest,
>
>
>   You progably stil have -nostdlib in your build flags somewhere.  You
> need to link with libgcc.a, which would be done automatically without
> that flag.  Alternatively if you aren't actually using the C++ exceptio=
n
> system, you can save a whole load of executable file size and runtime
> overhead by specifying -fno-exceptions.
>
>    cheers,
>      DaveK

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com


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