On Fri, 2003-01-03 at 19:30, Phil Edwards wrote:
> If it would help, libstdc++ also has such a file in its sources.
cp linker-map.gnu /usr/lib/gcc-lib/i386-linux/3.2.1/libstdc++_pic.map
fixed the warnings. Thank you!
Please add it to the libstdc++5-pic deb!
signature.asc
Description: This is
On Fri, Jan 03, 2003 at 06:30:52AM -0500, Anthony DeRobertis wrote:
> On Fri, 2003-01-03 at 05:13, Matthias Klose wrote:
>
> > How to avoid this?
>
> Not sure. The libc6-pic package doesn't suffer from this warning. The
> major difference I see quickly is some "libc_pic.map" file which lists
> sy
On Fri, 2003-01-03 at 05:13, Matthias Klose wrote:
> How to avoid this?
Not sure. The libc6-pic package doesn't suffer from this warning. The
major difference I see quickly is some "libc_pic.map" file which lists
symbols by version (apparently).
Having that map file appears to make mklibs call t
Anthony DeRobertis writes:
> When using mklibs w/ libstdc++5-pic to build minimal shared libs for an
> embedded system, I get warnings like this:
>
> specialmap-reader: /lib/libstdc++.so.5: no version information available
> (required by specialmap-reader)
How to avoid this?
Package: libstdc++5-pic
Version: 1:3.2.1-0pre3
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When using mklibs w/ libstdc++5-pic to build minimal shared libs for an
embedded system, I get warnings like this:
specialmap-reader: /lib/libstdc++.so.5: no version information availabl
5 matches
Mail list logo
