Re: [AVFS] Link Error on AVFS for Mac

Miklos Szeredi wrote:
> Mark,
> 
> I don't have any idea about this.  Maybe someone on the avfs list
> (CC-ed) can help.
> 
> Thanks,
> Miklos
> 
>> OK, this is bugging me to pieces.
>>
>> I got AVFS to compile on my mac using ./configure --enable-fuse && make 
>> all && sudo make install
>>
>> So I go to make a Portfile, so I can share this lovely little tool with 
>> the rest of the interested Mac Users out there.
>> And for the life of me I can't get it to compile, I keep getting link 
>> errors like this.
>>
>> Making all in test
>> if /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I. -I../include   
>> -I/opt/local/include -D_FILE_OFFSET_BITS=64 -D_REENTRANT 
>> -D_POSIX_PTHREAD_SEMANTICS -I../include -O2 -I/opt/local/include 
>> -D_FILE_OFFSET_BITS=64 -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -O2 -MT 
>> runtest.o -MD -MP -MF ".deps/runtest.Tpo" -c -o runtest.o runtest.c; \
>> then mv -f ".deps/runtest.Tpo" ".deps/runtest.Po"; else rm -f 
>> ".deps/runtest.Tpo"; exit 1; fi
>> /bin/bash ../libtool --tag=CC --mode=link /usr/bin/gcc-4.0 -I../include 
>> -O2 -I/opt/local/include -D_FILE_OFFSET_BITS=64 -D_REENTRANT 
>> -D_POSIX_PTHREAD_SEMANTICS -O2  -L/opt/local/lib -o runtest 
>> -L/opt/local/lib -lpthread -ldl  runtest.o ../lib/libavfs_static.la 
>> -lpthread -ldl
>> mkdir .libs
>> /usr/bin/gcc-4.0 -I../include -O2 -I/opt/local/include 
>> -D_FILE_OFFSET_BITS=64 -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -O2 -o 
>> runtest runtest.o  -L/opt/local/lib ../lib/.libs/libavfs_static.a 
>> -lpthread -ldl
>> /usr/bin/ld: Undefined symbols:
>> _crc32
>> _deflate
>> _deflateEnd
>> _deflateInit_
>> _inflate
>> _inflateEnd
>> _inflateInit2_
>> _inflateInit_
>> _inflateRestore
>> _inflateSave
>> collect2: ld returned 1 exit status
>> make[1]: *** [runtest] Error 1
>> make: *** [all-recursive] Error 1
>>
>> Error: Status 1 encountered during processing
>>
>> Any Ideas?

It seems zlib is missing at linktime, shouldn't there be a -lz on the
last gcc command line? Perhaps try adding it manually?
Also try grepping for zlib in the configure output, perhaps it isn't
found correctly... Is it readily available once OSX dev tools are
installed in  a standard location? Can't remember.
I might look into it at some point too as I am also interested in having
AVFS though FUSE on my Mac (I am using Fink though).


>> Other notes on AVFS, zip files created with The Finder's builtin Archive 
>> utility (BOMArchiveHelper) create a folder called __MACOSX that stores 
>> the resource fork of the file, (this is an hfs+ specific feature), this 
>> is for custom icons and things for files.
>>
>> This file should probably be hidden on systems that don't have resource 
>> forks, and on Macs the resource fork should be redirected there.
>> (The mac version of FUSE has a  hook to allow supplying resource forks).
>>
>> I'll look into implementing this myself.

Great idea. You have all my encouragements (and sporadic support) if
that helps! :)


>> Also have you considered automatic type detection for files like .tgz 
>> and .tbz and .tbz2, as well as miscellaneous archives with an incorrect 
>> extension?
>> The libmagic library is freely available to do magic number tests, that 
>> could make things much more intelligent.

Handling jar, ear, war, sar (Java packaging), sxw, odf, ... (all
compound office documents from Open Office, MS Word, etc.) as ZIP would
be great too, but magic would definitely be better (and might help
detecting self-extracting archives).

Happy new year everyone! :)
   Guillaume

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/