[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Linking errors from gplc with ld 2.28
From: |
Daniel Diaz |
Subject: |
Re: Linking errors from gplc with ld 2.28 |
Date: |
Thu, 27 Jul 2017 12:02:53 +0200 |
Hi Jasper,
this is due to the last gcc. The bug has been fixed on the sourceforge
repository.
But you can also easily fix it since there is one file to change:
file src/Ma2Asm/x86_64_any.c:213
replace
#if defined(M_x86_64_darwin) || defined(M_x86_64_bsd)
by
#if defined(M_x86_64_darwin) || defined(M_x86_64_bsd) || defined(M_x86_64_linux)
Then (in src):
make clean
make
make check
Hope this helps
Daniel
> Le 21 juil. 2017 à 12:25, Jasper Taylor <address@hidden> a écrit :
>
> I just upgraded my Debian box from Jessie to Stretch and I find I can no
> longer use gplc to convert Prolog code into executables. I get a lot of error
> messages starting as follows...
>
> /usr/bin/ld: /tmp/gplcMP1nIg.o: relocation R_X86_64_32S against `.text' can
> not be used when making a shared object; recompile with -fPIC
> /usr/bin/ld: /usr/local/gprolog-1.4.4/lib/all_pl_bips.o: relocation
> R_X86_64_32S against `.text' can not be used when making a shared object;
> recompile with -fPIC
> /usr/bin/ld: /usr/local/gprolog-1.4.4/lib/all_fd_bips.o: relocation
> R_X86_64_32S against `.text' can not be used when making a shared object;
> recompile with -fPIC
> .
>
> .
>
> /usr/bin/ld: final link failed: Nonrepresentable section on output
> collect2: error: ld returned 1 exit status
> compilation failed
>
> The first line refers to the object file generated from the Prolog code,
> subsequent lines to objects included in the gprolog installation. Debian
> Stretch includes ld version 2.28, while systems on which gplc works properly
> include ld version 2.25.
>
> Adding -C '-fPIC' makes no difference, presumably because the c compiler is
> not used when converting Prolog code to executable. Adding -A -'fPIC'
> produces an error message from the assembler, presumably because
> position-independence is determined in the assembly language code and cannot
> be added by the assembler.
>
> I get similar errors attempting to recompile gprolog on the new system. Does
> anyone know what is going on?
>
> --Jasper
>
>
>
> _______________________________________________
> Bug-prolog mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/bug-prolog