* Use of libstdc++.so is not transparent
@ 1998-02-08 13:45 Marc ESPIE
0 siblings, 0 replies; only message in thread
From: Marc ESPIE @ 1998-02-08 13:45 UTC (permalink / raw)
To: egcs
I've got egcs-980205 up and running with a shared libstdc++ on solaris and
on dec-osf4.0a.
However, since I am not root on either machine, I have to put everything
in a directory which is not visited by ldconfig.
Any C++ program will link against the shared libstdc++.so, as expected, but
the resulting executable will hold no library path information.
Under dec-osf4.0a, linking occurs as:
/users/algo/espie/pub/lib/gcc-lib/alpha-dec-osf4.0a/egcs-2.91.07/ld -G 8 -O1 -call_shared /usr/lib/cmplrs/cc/crt0.o -L/users/algo/espie/pub/lib/gcc-lib/alpha-dec-osf4.0a/egcs-2.91.07 -L/users/algo/espie/pub/alpha-dec-osf4.0a/lib -L/usr/lib/cmplrs/cc -L/users/algo/espie/pub/lib /tmp/ccaaBmoa1.o -lstdc++ -lm -lgcc -lc -lgcc
(missing -rpath /users/algo/espie/pub/lib)
Under solaris, linking occurs as:
/usr/local/util/packages/egcs-980205/lib/gcc-lib/sparc-sun-solaris2.5/egcs-2.91.07/ld -V -Y P,/usr/ccs/lib:/usr/lib -Qy /usr/local/util/packages/egcs-980205/lib/gcc-lib/sparc-sun-solaris2.5/egcs-2.91.07/crt1.o /usr/local/util/packages/egcs-980205/lib/gcc-lib/sparc-sun-solaris2.5/egcs-2.91.07/crti.o /usr/ccs/lib/values-Xa.o /usr/local/util/packages/egcs-980205/lib/gcc-lib/sparc-sun-solaris2.5/egcs-2.91.07/crtbegin.o -L/usr/local/util/packages/egcs-980205/lib/gcc-lib/sparc-sun-solaris2.5/egcs-2.91.07 -L/usr/local/util/packages/egcs-980205/sparc-sun-solaris2.5/lib -L/usr/ccs/bin -L/usr/ccs/lib -L/usr/local/util/packages/egcs-980205/lib /var/tmp/cca0063S1.o -lstdc++ -lm -lgcc -lc -lgcc /usr/local/util/packages/egcs-980205/lib/gcc-lib/sparc-sun-solaris2.5/egcs-2.91.07/crtend.o /usr/local/util/packages/egcs-980205/lib/gcc-lib/sparc-sun-solaris2.5/egcs-2.91.07/crtn.o
ld: Software Generation Utilities (SGU) SunOS/ELF (LK-2.0 (S/I) - versioning)
(missing -R /users/local/util/packages/egcs-980205/lib)
I don't know what to modify during the configuration/build process,
but I surmise g++ should build so that no reference to g++ internal should
be necessary to compile and run programs.
--
Marc Espie
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~1998-02-08 13:45 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1998-02-08 13:45 Use of libstdc++.so is not transparent Marc ESPIE
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).