Re: bigloo compile error

[email protected]
Newsgroups gmane.lisp.scheme.bigloo
Organization Inria
Message-ID <[email protected]>
Hi Mojca,

> I tested again with the default clang on 10.7 and it seems to break
> with the same error. Then I tried to compile with clang-3.3 which
> failed with (known):
> 
> make[9]: Entering directory `/path/to/bigloo4.1a/api/flac/src'
> /opt/local/bin/clang-mp-3.3  -o libbiglooflac_s-4.1a.dylib 
>                  -install_name
> @executable_path/../Frameworks/bigloo/4.1a/libbiglooflac_s-4.1a.dylib
> 
>                  objs/bglflac.o objs/flac.o objs/flac_alsadec.o 
>                   
>                  -dynamiclib -single_module -Wl,-read_only_relocs,suppress 
>                  -lFLAC  -lbigloo_s-4.1a -lbigloogc_fth-4.1a 
>                  -lc -L/path/to/bigloo4.1a/lib/4.1a -L/opt/local/lib   && 
>          if [ "libbiglooflac_s-4.1a.dylib" !=
> "/path/to/bigloo4.1a/lib/4.1a/libbiglooflac_s-4.1a.dylib" ]; then 
>            mv libbiglooflac_s-4.1a.dylib
> /path/to/bigloo4.1a/lib/4.1a/libbiglooflac_s-4.1a.dylib; 
>          fi
> ld: warning: -read_only_relocs cannot be used with x86_64
> Undefined symbols for architecture x86_64:
>   "_bgl_flac_checksum_debug", referenced from:
>       _bgl_read_callback in bglflac.o
>   "_bgl_flac_debug", referenced from:
>       _bgl_read_callback in bglflac.o
>       _bgl_seek_callback in bglflac.o
>       _bgl_tell_callback in bglflac.o
> ld: symbol(s) not found for architecture x86_64
> clang: error: linker command failed with exit code 1 (use -v to see invocation)
> make[9]: *** [shared-install-name] Error 1
> make[9]: Leaving directory `/path/to/bigloo4.1a/api/flac/src'
> make[8]: *** [shared] Error 1
> make[8]: Leaving directory `/path/to/bigloo4.
Fixed. Fairly easy as this was just dead code!

I will prepare a new tarball and check it against my local clang. I will upload
it when it will pass the whole test suite successfully.

-- 
Manuel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.