Andreas wrote:
> Unfortunately, when I run it I get a few warnings about type
> declarations. But what is more important are the following errors:
> /usr/bin/ld: poplink_3.o: relocation R_X86_64_32S against `.text'
> can not be used when making a PIE object; recompile with -fPIE
> amd there are lots like that.
> In the end poplog doesn't build.
>
> Does anyone know what to correct in the build process?
>
> I'm running on Arch Linux: Linux iona 5.4.6-arch3-1 #1 SMP PREEMPT
> Tue, 24 Dec 2019 04:36:53 +0000 x86_64 GNU/Linux
I suspect this has something to do with this part of poplog
$usepop/pop/src/syscomp/poplink_main.p
$usepop/pop/src/syscomp/make_poplink.p
An old redhat bug report found by google makes it look as if that '-fPIE'
error message is not peculiar to Arch since it can also occur in Redhat
systems, e.g.:
------
https://bugzilla.redhat.com/show_bug.cgi?id=785399
/usr/bin/ld: dynamic STT_GNU_IFUNC symbol `strcmp' with pointer equality in
`/usr/lib/gcc/x86_64-redhat-linux/4.4.4/../../../../lib64/libc.a(strcmp.o)'
can not be used when making an executable; recompile with -fPIE and relink with
-pie
collect2: ld returned 1 exit status
...
Reproduced both with Fedora 13 x86 and Fedora 13 x86_64. Reproduced when
using gcc and gcc34 compilers.
-----
So perhaps it is not inherently due to use of Arch, but something about
Arch defaults, or the type of file system in use? I've tested Poplog
installation only on ext4 file systems.
A proper diagnosis may require the complete trace output from the Poplog
install process, if you don't mind re-running the install script and saving
the output to post to this list or to a web site from which it can be
downloaded. If that's inconvenient for you post it as an attachment to a
message.
Sorry I can't be more helpful.
Aaron
