|
|
| Line 1: |
Line 1: |
| − | Error messages when attempting to make a shared library on 64-bit Fedora Core 7.
| + | How about OS-specific "tools"? Say, [http://developer.apple.com/documentation/Darwin/Reference/ManPages/man1/DeRez.1.html DeRez] under Mac OS X for resource fork meta data? --[[User:JohnJ|JohnJ]] 08:00, 4 September 2008 (UTC) |
| | | | |
| − | <tt>[root@localhost lib]# g++ -shared -o libaff.so -g -O2 aff_db.o aff_toc.o afflib.o afflib_os.o afflib_pages.o afflib_stream.o afflib_util.o base64.o lzma_glue.o s3_glue.o vnode_aff.o vnode_afd.o vnode_afm.o vnode_ewf.o vnode_raw.o vnode_s3.o vnode_split_raw.o aftimer.o LzmaBench.o LzmaRam.o LzmaRamDecode.o LzmaDecode.o BranchX86.o LZMADecoder.o LZMAEncoder.o LZInWindow.o LZOutWindow.o RangeCoderBit.o InBuffer.o OutBuffer.o StreamUtils.o Alloc.o CommandLineParser.o CRC.o String.o StringConvert.o StringToInt.o Vector.o -lssl -lcrypto -lz -lexpat -lcurl -lncurses
| + | Perhaps a few introductory words as to what kind of file analysis is intended would be helpful. |
| − | | + | I was looking for a mention of the http://www.fileadvisor.bit9.com service, and could not decide |
| − | /usr/bin/ld: aff_db.o: relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC | + | if it was suitable for this page, or if it should go somewhere else. It's a collection of |
| − | | + | file hashes, very useful for deciding if a file is reasonably well known by its file hash.[[User:Athulin|Athulin]] 02:41, 29 October 2007 (PDT) |
| − | aff_db.o: could not read symbols: Bad value
| + | |
| − | | + | |
| − | collect2: ld returned 1 exit status
| + | |
| − | | + | |
| − | [root@localhost lib]# g++ -shared -fPIC -o libaff.so -g -O2 aff_db.o aff_toc.o afflib.o afflib_os.o afflib_pages.o afflib_stream.o afflib_util.o base64.o lzma_glue.o s3_glue.o vnode_aff.o vnode_afd.o vnode_afm.o vnode_ewf.o vnode_raw.o vnode_s3.o vnode_split_raw.o aftimer.o LzmaBench.o LzmaRam.o LzmaRamDecode.o LzmaDecode.o BranchX86.o LZMADecoder.o LZMAEncoder.o LZInWindow.o LZOutWindow.o RangeCoderBit.o InBuffer.o OutBuffer.o StreamUtils.o Alloc.o CommandLineParser.o CRC.o String.o StringConvert.o StringToInt.o Vector.o -lssl -lcrypto -lz -lexpat -lcurl -lncurses
| + | |
| − | | + | |
| − | /usr/bin/ld: LzmaRamDecode.o: relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC
| + | |
| − | | + | |
| − | LzmaRamDecode.o: could not read symbols: Bad value
| + | |
| − | | + | |
| − | collect2: ld returned 1 exit status
| + | |
| − | | + | |
| − | [root@localhost lib]#
| + | |
| − | </tt>
| + | |
| − | | + | |
| − | Well, why don't you add -fPIC to the CFLAGS and see what happens.
| + | |
| − | | + | |
| − | Are you doing this with the stock distribution? Did you make any changes? This doesn't happen for me. Would you be interested in trying the 3.0 version?
| + | |
Latest revision as of 03:00, 4 September 2008
How about OS-specific "tools"? Say, DeRez under Mac OS X for resource fork meta data? --JohnJ 08:00, 4 September 2008 (UTC)
Perhaps a few introductory words as to what kind of file analysis is intended would be helpful.
I was looking for a mention of the http://www.fileadvisor.bit9.com service, and could not decide
if it was suitable for this page, or if it should go somewhere else. It's a collection of
file hashes, very useful for deciding if a file is reasonably well known by its file hash.Athulin 02:41, 29 October 2007 (PDT)
