As a follow up, I tried to compile it in a different Mac, with same MacOS X
10.5.5 (Darwin 9.5.0) and gcc 4.0.1.

But in this new machine everything compiled fine, so I checked ld version:

Not working:
$ ld -v
@(#)PROGRAM:ld  PROJECT:ld64-82.5

Working:
$ ld -v
@(#)PROGRAM:ld  PROJECT:ld64-85

I could also find in google that other people had the very same problem with
other projects and some could get it solved running:

./configure --with-ld=/usr/bin/ld_classic

But as far as I could check gprolog's configure ignores this option and I
could not find any way to force ld_classic to be used.

ld_classic version is also older in the machine that is not working:

Not working:
$ ld_classic -v
Apple Computer, Inc. version cctools-667.3~112

Working:
$ ld_classic -v
Apple Computer, Inc. version cctools-668~13

I'll try to update the not-working machine, hope that will solve the
problem.

-- 
Marcello Azambuja

On Tue, Oct 7, 2008 at 2:05 PM, Marcello Azambuja <[EMAIL PROTECTED]>wrote:

> Hi,
>
> I'm trying to compile gprolog on my MacBook Pro running Mac OS X 10.5.5
> (Darwin 9.5.0) with gcc 4.0.1.
>
> I tried downloading gprolog-1.3.0.tar.gz but could not compile it
> (configure && make):
>
> ...
> gplc -o pl2wam --no-fd-lib --min-bips pl2wam.o read_file.o bip_list.o
> syn_sugar.o internal.o code_gen.o reg_alloc.o inst_codif.o first_arg.o
> indexing.o wam_emit.o
> collect2: ld terminated with signal 10 [Bus error]
> Undefined symbol: predicate($pl_query_recover_alt/0)
> Undefined symbol: predicate($pl_query_recover_alt/0)
> compilation failed
> make[1]: *** [pl2wam] Error 1
> make: *** [all] Error 1
>
> I also tried 'port install gprolog' but got the same error (it basically
> does the same that I did).
>
> I searched the list archives but could only find a message from two years
> ago suggesting to use gcc 3.x.
>
> Any help is appreciated.
>
> Regards,
>
> Marcello Azambuja
>
_______________________________________________
Users-prolog mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/users-prolog

Reply via email to