On Thu, Dec 01, 2005, Doug Summers wrote:
> [...]
> >I cannot believe that both result in the same errors related to external
> >DSOs. I would expect that perhaps <prefix>/bin/ar results in them. But
> >at least the system "ar" should be totally quiet on the above commands.
> [...]
> >Can you give more information, especially the outputs of the following
> >particular commands:
> >
> $ touch sample.o
> $ ldd <prefix>/bin/ar
> libl.so.1 => /usr/lib/hpux32/libl.so.1
> libm.so.1 => /usr/lib/hpux32/libm.so.1
> libc.so.1 => /usr/lib/hpux32/libc.so.1
> libc.so.1 => /usr/lib/hpux32/libc.so.1
> libdl.so.1 => /usr/lib/hpux32/libdl.so.1
> $ <prefix>/bin/ar
> /usr/lib/hpux32/dld.so: Unsatisfied data symbol 'yylsp' in load module
> '/usr/lib/hpux32/libl.so.1'.
> /usr/lib/hpux32/dld.so: Unsatisfied data symbol 'yyolsp' in load module
> [...]
> $ <prefix>/bin/ar cru sample.a sample.o
> /usr/lib/hpux32/dld.so: Unsatisfied data symbol 'yylsp' in load module
> '/usr/lib/hpux32/libl.so.1'.
> /usr/lib/hpux32/dld.so: Unsatisfied data symbol 'yyolsp' in load module
> [...]
> $ ldd /usr/bin/ar
> libdl.so.1 => /usr/lib/hpux32/libdl.so.1
> libm.so.1 => /usr/lib/hpux32/libm.so.1
> libunwind.so.1 => /usr/lib/hpux32/libunwind.so.1
> libc.so.1 => /usr/lib/hpux32/libc.so.1
> libuca.so.1 => /usr/lib/hpux32/libuca.so.1
> libdl.so.1 => /usr/lib/hpux32/libdl.so.1
> $ /usr/bin/ar
> usage: ar [-][mrxtdpqh][ACTabcFfilsuvzSo] [posname] archive files ...
> $ /usr/bin/ar cru sample.a sample.o
Ah, as I expected: *not* the same problem with and without "binutils".
The problem is that the "ar" of OpenPKG "binutils" got incorrectly or
insufficiently linked. The "yyxxx" symbols I guess are required
either by "libl.so.1" (Flex?) and could be provided by a liby.
Anyway, the problem is how "binutils" are built on your platform.
You have to look in more depth into the build process of "binutils".
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [email protected]
