tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: String offset errors on evbarm 8.99 [PR 54159]

On Sun, Aug 04, 2019 at 10:22:14PM +0000, wrote:
> Please consider coming up with a test case that looks like this:
> This linker command, together with these 4 object files, fails:
> gcc one.o two.o three.o four.o
> http://yourwebsite/one.o (two.o, three.o, four.o)
> one.o was generated with the following command:
> gcc one.c -o one.o

The problem is to know how exactly the package (here it is
security/p11-kit because it has the simplest dependencies and can be
cross-compiled, but there are others) invokes the linker. It is 
embedded in the pkgsrc->automake->libtool dance, and I don't know
anything about it.

Linking directly there is no problem. So the question is to obtain _how_
the linker is invoked by the pkg building.

So I'm not able to give a test case since the command I give succeeds.
That's the way the linker is invoked that fails and I don't know how
this real labyrinth works.

Is there a way to ask pkgsrc to force every tool (gmake, libtool) to 
spit out the commands it runs?
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C

Home | Main Index | Thread Index | Old Index