question about "invalid string offset" & "could not read symbols: Malformed archive" linker errors
Hi, Presently I am attempting to build an application on Linux with GNU ld version 2.17.50.0.6-5.el5 20061020. When I execute make, it compiles but when it reaches the linker I receive the following error messages, make[1]: Entering directory `/mnt/hgfs/pclinux/trunk/branches/testapp-xvt5.8update/testappwin' make[1]: Warning: File `../outdir/debug/libtestappwin.a' has modification time 1.7e+03 s in the future g++ -g ../outdir/debug/testappwin/testappwin.o -o ../outdir/debug/testappwin.exe -L../outdir/debug -L../winport -L../outdir/debug/xvtlib -L/usr/X11R6/lib -L../license/lib/license -lflow -ltestappwin -lcompress -lgeom3d -ltape -ltiff -lfreetype -lwinport -lxispread -lpwr -lrw -lxvtxmapi -lxvtxmhb500 -lxvtxmba500 -lxvtxmhi500 -lnxpro -lm -lGL -lGLU -lX11 -lXm -llicense -lpthread -lstdc++ /usr/bin/ld: ../outdir/debug/libxvtxmapi.a(tapp.o): invalid string offset 369098752 >= 0 for section `' /usr/bin/ld: ../outdir/debug/libxvtxmapi.a(tapp.o): invalid string offset 33554432 >= 0 for section `' /usr/bin/ld: ../outdir/debug/libxvtxmapi.a(tapp.o): invalid string offset 134217728 >= 0 for section `' /usr/bin/ld: ../outdir/debug/libxvtxmapi.a(tapp.o): invalid string offset 352321536 >= 0 for section `' ../outdir/debug/libxvtxmapi.a: could not read symbols: Malformed archive collect2: ld returned 1 exit status make[1]: *** [../outdir/debug/testappwin.exe] Error 1 make[1]: Leaving directory `/mnt/hgfs/pclinux/trunk/branches/testapp-xvt5.8update/testappwin' make: *** [debug] Error 2 [EMAIL PROTECTED] testapp-xvt5.8update]$ Do you have any suggestions as to what may the cause of the problem? Please let me know if you want to see some of the source from tapp.c. Any help at all would be greately appreciated. Thank you for your time and I look forward to hearing from you. Sincerely, Roger ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
Re: question about "invalid string offset" & "could not read symbols: Malformed archive" linker errors (fwd)
Hi, We built the libxvtmapi.a ourselves. Yes, I've tried deleting it and rebuilding but I still get the file format not recognized error message. The following lines show the size of the library file: [EMAIL PROTECTED] testapp]$ ls -l outdir/debug/libxvtxmapi.a -rw-rw-r-- 1 roger roger 358363 Aug 20 10:09 outdir/debug/libxvtxmapi.a The build procedure seems to work fine otherwise, though there are some warning messages. That said, I haven't seen any warning messages that seem to be related to this issue. Here is what I get when I attempt for perform an object dump: [EMAIL PROTECTED] testapp]$ objdump -p outdir/debug/libxvtxmapi.a In archive outdir/debug/libxvtxmapi.a: objdump: tapp.o: File format not recognized objdump: outdir/debug/libxvtxmapi.a: Malformed archive Here is the tapp.o file: [EMAIL PROTECTED] testapp]$ find . -name tapp.o ./xvtdsp55/linux_x86/src/ptk/CMakeFiles/xvtxmapid.dir/tapp.o XVT is a platform-independent API that we use for our application GUI. We have all the source code for this API. Any suggestions would be greatly appreciated. Sincerely, Roger -- Forwarded message -- Date: Wed, 20 Aug 2008 08:55:25 +0100 From: Nick Clifton <[EMAIL PROTECTED]> To: Roger Moore <[EMAIL PROTECTED]> Subject: Re: question about "invalid string offset" & "could not read symbols: Malformed archive" linker errors Hi Roger, > g++ -g ../outdir/debug/testappwin/testappwin.o -o [...] > ../outdir/debug/libxvtxmapi.a: could not read symbols: File format not > recognized > How do you tell why a file format is not recognized? Do you have any > suggestions? Did you build the libxvtmapi.a archive yourself or is it one that has been provided to you ? If you built it yourself, can you try deleting it and rebuilding it, and were there any problems during the build procedure ? How big is it ? (Sometimes a problem in a build process can create a zero-length file, which the linker cannot then process). Try running this command to find out more about the object files inside the archive: objdump -p ../outdir/debug/libxvtmapi.a Is the file format of the object files what you would expect it to be ? Cheers Nick -- Forwarded message -- Date: Mon, 18 Aug 2008 11:24:30 -0600 (MDT) From: Roger Moore <[EMAIL PROTECTED]> To: bug-binutils@gnu.org Subject: question about "invalid string offset" & "could not read symbols: Malformed archive" linker errors Hi, Presently I am attempting to build an application on Linux with GNU ld version 2.17.50.0.6-5.el5 20061020. When I execute make, it compiles but when it reaches the linker I receive the following error messages, make[1]: Entering directory `/mnt/hgfs/pclinux/trunk/branches/testapp-xvt5.8update/testappwin' make[1]: Warning: File `../outdir/debug/libtestappwin.a' has modification time 1.7e+03 s in the future g++ -g ../outdir/debug/testappwin/testappwin.o -o ../outdir/debug/testappwin.exe -L../outdir/debug -L../winport -L../outdir/debug/xvtlib -L/usr/X11R6/lib -L../license/lib/license -lflow -ltestappwin -lcompress -lgeom3d -ltape -ltiff -lfreetype -lwinport -lxispread -lpwr -lrw -lxvtxmapi -lxvtxmhb500 -lxvtxmba500 -lxvtxmhi500 -lnxpro -lm -lGL -lGLU -lX11 -lXm -llicense -lpthread -lstdc++ /usr/bin/ld: ../outdir/debug/libxvtxmapi.a(tapp.o): invalid string offset 369098752 >= 0 for section `' /usr/bin/ld: ../outdir/debug/libxvtxmapi.a(tapp.o): invalid string offset 33554432 >= 0 for section `' /usr/bin/ld: ../outdir/debug/libxvtxmapi.a(tapp.o): invalid string offset 134217728 >= 0 for section `' /usr/bin/ld: ../outdir/debug/libxvtxmapi.a(tapp.o): invalid string offset 352321536 >= 0 for section `' ../outdir/debug/libxvtxmapi.a: could not read symbols: Malformed archive collect2: ld returned 1 exit status make[1]: *** [../outdir/debug/testappwin.exe] Error 1 make[1]: Leaving directory `/mnt/hgfs/pclinux/trunk/branches/testapp-xvt5.8update/testappwin' make: *** [debug] Error 2 [EMAIL PROTECTED] testapp-xvt5.8update]$ Do you have any suggestions as to what may the cause of the problem? Please let me know if you want to see some of the source from tapp.c. Any help at all would be greately appreciated. Thank you for your time and I look forward to hearing from you. Sincerely, Roger ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
Re: question about "invalid string offset" & "could not read symbols: Malformed archive" linker errors (fwd)
Hi Nick, On Fri, 22 Aug 2008, Nick Clifton wrote: > Hi Roger, > > > We built the libxvtmapi.a ourselves. Yes, I've tried deleting it and > > rebuilding but I still get the file format not recognized error message. > > > > The build procedure seems to work fine otherwise, though there are some > > warning messages. That said, I haven't seen any warning messages that > > seem to be related to this issue. > > > [If all else fails, try fixing the warnings anyway... :-)] That is an option I will have to explore at some point, I think. :) > > [EMAIL PROTECTED] testapp]$ objdump -p > > outdir/debug/libxvtxmapi.a > > In archive outdir/debug/libxvtxmapi.a: > > objdump: tapp.o: File format not recognized > > objdump: outdir/debug/libxvtxmapi.a: Malformed archive > > > This is the cause of the problem - the tapp.o file is not recognized. > One possible cause for this is that the compiler used to build the > tapp.o file is targeted at one particular processor type and the > binutils (including objdump and the linker) are targeted at a different > system type. To check this have a look at the output of "objdump > --help" and compare the supported targets list with the target > displayed as part of the output of "gcc --verbose". Both the objdump and gcc commands indicate they support the i386 architecture, which is where I am building the testapp. Here is the output from uname: Linux randyx64-rh5 2.6.18-53.el5PAE #1 SMP Wed Oct 10 16:48:18 EDT 2007 i686 i686 i386 GNU/Linux So it is a 64-bit machine but we are running 32-bit Red Hat Enterprise 5 on it. It get identical build errors when I try to build it on 64-bit Red Hat Enterprise 5 as well. > > Here is the tapp.o file: > > > > [EMAIL PROTECTED] testapp]$ find . -name tapp.o > > ./xvtdsp55/linux_x86/src/ptk/CMakeFiles/xvtxmapid.dir/tapp.o > What does "objdump -p tapp.o" report ? Is it still unrecognized ? (If > not then this is very worrying. It would mean that placing the tapp.o > file into the libxvtxmapi.a archive has corrupted it). The results from objdump are very confusing: [EMAIL PROTECTED] xvtxmapid.dir]$ objdump -p tapp.o tapp.o: file format elf32-i386 [EMAIL PROTECTED] xvtxmapid.dir]$ So it looks like objdump thinks tapp.o is OK!? > How was tapp.o built ? (Ie what was the command line used to compile it > and to assemble it). Here are the commands in the makefile that related to tapp (please note that it is built using GNU Make 3.81, but the make is configured using cmake version 2.6-patch 1): # target to build an object file tapp.o: cd /home/roger/workspace/branches/testapp-xvt5.8update/xvtdsp55/linux_x86 && $(MAKE) -f src/ptk/CMakeFiles/xvtxmapid.dir/build.make src/ptk/CMakeFiles/xvtxmapid.dir/tapp.o .PHONY : tapp.o # target to preprocess a source file tapp.i: cd /home/roger/workspace/branches/testapp-xvt5.8update/xvtdsp55/linux_x86 && $(MAKE) -f src/ptk/CMakeFiles/xvtxmapid.dir/build.make src/ptk/CMakeFiles/xvtxmapid.dir/tapp.i .PHONY : tapp.i # target to generate assembly for a file tapp.s: cd /home/roger/workspace/branches/testapp-xvt5.8update/xvtdsp55/linux_x86 && $(MAKE) -f src/ptk/CMakeFiles/xvtxmapid.dir/build.make src/ptk/CMakeFiles/xvtxmapid.dir/tapp.s .PHONY : tapp.s As well, here is the make command in the makefile: # The main all target all: cmake_check_build_system cd /home/roger/workspace/branches/testapp-xvt5.8update/xvtdsp55/linux_x86 && $(CMAKE_COMMAND) -E cmake_progress_start /home/roger/workspace/branches/testappw-xvt5.8update/xvtdsp55/linux_x86/CMakeFiles /home/roger/workspace/branches/testapp-xvt5.8update/xvtdsp55/linux_x86/src/ptk/CMakeFiles/progress.make cd /home/roger/workspace/branches/testapp-xvt5.8update/xvtdsp55/linux_x86 && $(MAKE) -f CMakeFiles/Makefile2 src/ptk/all $(CMAKE_COMMAND) -E cmake_progress_start /home/roger/workspace/branches/testapp-xvt5.8update/xvtdsp55/linux_x86/CMakeFiles 0 .PHONY : all > Cheers > Nick FYI, here is the output from objdump and gcc that you requested earlier: [EMAIL PROTECTED] testapp-xvt5.8update]$ objdump --help Usage: objdump Display information from object . At least one of the following switches must be given: -a, --archive-headersDisplay archive header information -f, --file-headers Display the contents of the overall file header -p, --private-headersDisplay object format specific file header contents -h, --[section-]headers Display the contents of the section headers -x, --all-headersDisplay the contents of all headers -d, --disassembleDisplay assembler contents of executable sections -D, --disassemble-allDisplay assembler contents of all sections -S, --source Intermix source code with disassembly -s, --full-contents Display the full contents of all sections requested -g, --debugging Display debug information in object file -e, --debugging-tags Display debu
Re: question about "invalid string offset" & "could not read symbols: Malformed archive" linker errors (fwd)
Hi Nick,
On Tue, 26 Aug 2008, Nick Clifton wrote:
> >>> In archive outdir/debug/libxvtxmapi.a:
> >>> objdump: tapp.o: File format not recognized
>
> > [EMAIL PROTECTED] xvtxmapid.dir]$ objdump -p tapp.o
> > tapp.o: file format elf32-i386
>
>
> Oh dear. So it would appear that tapp.o is being corrupted when it is
> added to the libxvtmapi.a archive.
>
> If you extract a copy from the archive is this version also
> unreconizable ? Is it the same size as the original version ? Do they
> compare the same ?
When I attempt to extract tapp.o from libxvtxmapi.a, I get the malformed
archive problem again,
[EMAIL PROTECTED] debug]$ ar -x libxvtxmapi.a tapp.o
ar: libxvtxmapi.a: Malformed archive
When I compare tapp.o to libxvtxmapi.a in a hex editor, the only part that
is common between the two files is,
007876745F6170705F6765745F64656661756C745F63746F6F6C73007876745F6170705F6765745F66696C65007876745F6170705F7365745F66696C655F70726F636573736564007876745F6170705F6765745F66696C65735F636F756E74007876745F6170705F657363617065007876745F6170705F
Here is the tapp.o file in ASCII. When I visually compare this to what is
in libxvtxmapi.a, they *look* identical but my hex editor indicates they
are different for some reason except for the part that I indicated above,
.ELF4.(.U..S..$..f..t9...D$.ND$...a..D$..D$...$.[]..[].'U(.].u..u.$...t..4$...]..u...]D$.+D$...!..D$..D$...$.t&.U..].u.$]..u...]..v.U..S..$..[].U(.].}..}..u..u.$...tW..t..t$..<$...]..u..}...]..D$D$...!..D$...$.D$..D$...'U(.]..E.E..u.$..E..D$..E...$]u...].'U..S..[]..v.U(.].u..u..}..}t~$...t...t3.E..t$..|$..D$..E..D$..E...$...]..u..}...]..D$.b..D$...!..D$...$.D$...$f...oD$.\.U..S..$..[].xvt_app_process_pending_events../mnt/hgfs/pclinux/trunk/branches/vistanew-xvt5.8update/xvtdsp55/linux_x86/src/ptk/tapp.c.xvt_app_get_default_ctools.xvt_app_get_file.xvt_app_set_file_processed.xvt_app_get_files_count.xvt_app_escape.xvt_app_create.xvt_app_allow_quit...
GCC: (GNU) 4.1.2 20070626 (Red Hat
4.1.2-14)[EMAIL
PROTECTED](...x..."...'...,...,...G...1..._...6...n...;[EMAIL
PROTECTED]|[EMAIL PROTECTED]
...S...*...:...Q...p...1...dtapp.c.xvt_source_file..LC0..LC1..LC2..LC3..LC4..LC5..LC6..LC7.xvt_app_process_pending_events.__i686.get_pc_thunk.bx._GLOBAL_OFFSET_TABLE_.xvtv_errfrm_mark_API.xvtv_app_proc_update.xvtv_errmsg_dispatch.xvtv_errfrm_unmark_API.xvtk_app_process_pending_events.xvt_app_get_default_ctools.xvtv_app_get_default_ctools.xvt_app_get_file.xvtk_app_get_file.xvt_app_set_file_processed.xvtk_app_set_file_processed.xvt_app_get_files_count.xvtk_app_get_files_count.xvt_app_escape.xvtk_app_escape.xvt_app_destroy.xvtv_app_destroy.xvt_app_create.xvtv_mem_get_functions.xvtk_app_create.xvtv_mem_set_functions.xvt_app_allow_quit.xvtk_app_allow_quit.!...,...T...Y...d...i...!...&
..-...E...K...T...\...a"..f$..-...3...?...G...Y&..`(...*...+..<...A...Q,..u...{...
The part that my hex editor indicates is identical between libxvtxmapi.a
and tapp.o is this part,
.xvt_app_get_default_ctools.xvt_app_get_file.xvt_app_set_file_processed.xvt_app_get_files_count.xvt_app_escape.xvt_app_
Do you have any other ways I could extract tapp.o besides using ar?
> > Here is the file
> > xvtdsp55/linux_x86/src/ptk/CMakeFiles/xvtxmapi.dir/link.txt:
> >
> > /usr/bin/ar cr ../../lib/libxvtxmapi.a "CMakeFiles/xvtxmapi.dir/tapp.o"
> > [...]
> > /usr/bin/ranlib ../../lib/libxvtxmapi.a
>
> Quick question - if you intercept the libxvtmapi.a build process after
> the invocation of "ar" but before the invocation of "ranlib" is the
> version of tapp.o inside t
Re: question about "invalid string offset" & "could not read symbols: Malformed archive" linker errors (fwd)
Hi Nick, On Wed, 27 Aug 2008, Nick Clifton wrote: > > Do you have any other ways I could extract tapp.o besides using ar? > > Nope, sorry. > > > Please find libxvtxmapi.a and tapp.o > > Well that libxvtxmapi.a is definitely corrupt, and he tapp.o file is OK. > > > If I take ranlib out of the link.txt file, and then try to build, I get > > the same malformed archive message on libxvtxmapi.a, so it appears that > > the corruption occurs before ranlib is called. > > OK, then "ar" is the culprit. > > > [EMAIL PROTECTED] debug]$ ar --version > > GNU ar (GNU Binutils) 2.18.50.20080822 > > Looks good - are you sure that this the version being used by cmake ? > Ie is it possible that you have other versions of the ar program in your > search path ? It turns out there *is* another ar in the path: [EMAIL PROTECTED] pclinux]$ ls /usr/bin/ar /usr/bin/ar [EMAIL PROTECTED] pclinux]$ /usr/bin/ar --version GNU ar 2.17.50.0.6-5.el5 20061020 Copyright 2005 Free Software Foundation, Inc. This program is free software; you may redistribute it under the terms of the GNU General Public License. This program has absolutely no warranty. [EMAIL PROTECTED] pclinux]$ The ar located in /usr/local/bin is the one that is version 2.18. Interesting! > > Do you have any suggestions in terms of how to intercept the build > > process? > > First check to see if the corruption takes place if you run the "ar" > command by hand, ie not inside the cmake process. If the corruption > does happen then it is the ar program that is to blame. If the > corruption does not happen then it is the build process/cmake that is to > blame. If I explicitly run the *correct* ar command by hand, /usr/local/bin/ar cr ../../lib/libxvtxmapi.a "CMakeFiles/xvtxmapi.dir/tapp.o" "CMakeFiles/xvtxmapi.dir/tcb.o" "CMakeFiles/xvtxmapi.dir/tctl.o" "CMakeFiles/xvtxmapi.dir/tcxo.o" "CMakeFiles/xvtxmapi.dir/tdebug.o" "CMakeFiles/xvtxmapi.dir/tdlg.o" "CMakeFiles/xvtxmapi.dir/tdm.o" "CMakeFiles/xvtxmapi.dir/tdwin.o" "CMakeFiles/xvtxmapi.dir/terr.o" "CMakeFiles/xvtxmapi.dir/tevent.o" "CMakeFiles/xvtxmapi.dir/tfont.o" "CMakeFiles/xvtxmapi.dir/tfsys.o" "CMakeFiles/xvtxmapi.dir/tgmem.o" "CMakeFiles/xvtxmapi.dir/thtml.o" "CMakeFiles/xvtxmapi.dir/timage.o" "CMakeFiles/xvtxmapi.dir/tiostr.o" "CMakeFiles/xvtxmapi.dir/tlist.o" "CMakeFiles/xvtxmapi.dir/tmem.o" "CMakeFiles/xvtxmapi.dir/tmenu.o" "CMakeFiles/xvtxmapi.dir/tnav.o" "CMakeFiles/xvtxmapi.dir/tnotebk.o" "CMakeFiles/xvtxmapi.dir/tpalet.o" "CMakeFiles/xvtxmapi.dir/tpat.o" "CMakeFiles/xvtxmapi.dir/tpict.o" "CMakeFiles/xvtxmapi.dir/tpmap.o" "CMakeFiles/xvtxmapi.dir/tprint.o" "CMakeFiles/xvtxmapi.dir/trect.o" "CMakeFiles/xvtxmapi.dir/tres.o" "CMakeFiles/xvtxmapi.dir/tsbar.o" "CMakeFiles/xvtxmapi.dir/tscr.o" "CMakeFiles/xvtxmapi.dir/tslist.o" "CMakeFiles/xvtxmapi.dir/tstr.o" "CMakeFiles/xvtxmapi.dir/ttimer.o" "CMakeFiles/xvtxmapi.dir/ttreev.o" "CMakeFiles/xvtxmapi.dir/ttx.o" "CMakeFiles/xvtxmapi.dir/tvobj.o" "CMakeFiles/xvtxmapi.dir/twin.o" "CMakeFiles/xvtxmapi.dir/rotated.o" "CMakeFiles/xvtxmapi.dir/xvtcm.o" It gives me this ouput: /usr/local/bin/ar: ../../lib/libxvtxmapi.a: Malformed archive > If it is "ar" that is to blame, please could you see if you can reduce > the test to as few input object files as possible (whilst still showing > the corruption of tapp.o) and then put them together into a tarball and > email it to me, along with a copy of the exact command line that you > have been using. Ie I would like to try to reproduce the corruption locally. Okay, I'll send the files to you shortly. The command I'm using is simply 'make'. Thank you, Roger ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
Re: ***UNCHECKED*** Re: ***UNCHECKED*** Re: question about "invalid string offset" & "could not read symbols: Malformed archive" linker errors (fwd)
Hi Nick,
I think I was having some problems before with the libxvtmapi.a file
because I was mixing some of the XVT 5.50 code with the XVT 5.80 code.
Please find on my web-site the complete archive with all source and object
files,
http://www.ece.ualberta.ca/~rmoore/linux.xvt5.8update.12.sept.2008.no.malformed.tar.bz2
Please find below the output from make. First you have to type,
$ ccmake .
To properly configure the project and set it up with the proper
directories. Then in the text UI type 'c' and 'g' which should exit for
you automatically if it was successfuly. Otherwise, if you don't want to
bother with the ccmake, you can simply set you directory structure to be
the following and place the files in there,
/mnt/hgfs/pclinux/trunk/branches/xvt5.8update
And simply type,
$ make
Here is the output I'm getting,
g++ -g ../outdir/debug/vistawin/vistawin.o -o ../outdir/debug/vistawin.exe
-L../outdir/debug -L../outdir/debug/xvtlib -L/usr/X11R6/lib -lvistawin
-lxvtxmapid -lxvtxmhb580d -lxvtxmba580d -lxvtxmhi580d -lnxpro -lm -lGL
-lGLU -lX11 -lXm -lpthread -lstdc++
/usr/local/bin/ld: skipping incompatible
../outdir/debug/xvtlib/libnxpro.so when searching for -lnxpro
/usr/local/bin/ld: cannot find -lnxpro
collect2: ld returned 1 exit status
make[1]: *** [../outdir/debug/vistawin.exe] Error 1
make[1]: Leaving directory
`/mnt/hgfs/pclinux/trunk/branches/xvt5.8update/vistawin'
make: *** [debug] Error 2
[EMAIL PROTECTED] xvt5.8update]$ pushd
/mnt/hgfs/pclinux/trunk/branches/xvt5.8update/outdir/debug/xvtlib
/mnt/hgfs/pclinux/trunk/branches/xvt5.8update
[EMAIL PROTECTED] xvtlib]$ !objd
objdump -p libnxpro.so
libnxpro.so: file format elf32-i386
Program Header:
LOAD off0x vaddr 0x paddr 0x align 2**12
filesz 0x00068894 memsz 0x00068894 flags r-x
LOAD off0x00069000 vaddr 0x00069000 paddr 0x00069000 align 2**12
filesz 0x2280 memsz 0x3920 flags rw-
DYNAMIC off0x0006ab50 vaddr 0x0006ab50 paddr 0x0006ab50 align 2**2
filesz 0x00b8 memsz 0x00b8 flags rw-
Dynamic Section:
NEEDED libpthread.so.0
HASH 0x0094
STRTAB 0x558c
SYMTAB 0x181c
STRSZ0x2fe6
SYMENT 0x0010
PLTGOT 0x0006ac08
PLTRELSZ 0x0bb8
PLTREL 0x0011
JMPREL 0x00014838
REL 0x8d50
RELSZ0xbae8
RELENT 0x0008
TEXTREL 0x
VERNEED 0x8d20
VERNEEDNUM 0x0001
VERSYM 0x8572
RELCOUNT 0x122a
Version References:
required from libpthread.so.0:
0x0d696911 0x00 03 GLIBC_2.1
0x0d696910 0x00 02 GLIBC_2.0
[EMAIL PROTECTED] xvtlib]$
Could you please tell me, how do I link in the libnxpro.so file found in
outdir/debug/xvtlib? Sorry, I'm sure I'm missing something obvious.
Thank you,
Roger
On Tue, 2 Sep 2008, Nick Clifton wrote:
> Hi Roger,
>
> > Okay, you don't really need to reproduce the build process. Packed in the
> > archive I sent you is the file libxvtxmapi.a. It should be located in
> > both the ~/lib and the ~/outdir/debug directories. If you perform ar on
> > this library, it should mention something about tapp.o.
>
> It does. ("Malformed archive" etc etc).
>
> Now - how do I build this library ? Ie I want to take an uncorrupt
> tapp.o file and put it into a library and in the process corrupt it, so
> that I can try to locate exactly where the corruption is happening.
>
> Cheers
>Nick
>
___
bug-binutils mailing list
bug-binutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-binutils
