Le 20 sept. 2013 23:21, "Michael Biebl" <biebl@debian.org> a écrit :
>
> Am 20.09.2013 23:03, schrieb Russ Allbery:
> >> As we found out, pkg-config actually strips such library system search paths:
> >> > $ pkg-config --static --libs gmime-2.6 -pthread -lgmime-2.6 -lnsl -lgpgme-pthread -lassuan -lgpg-error -lpthread -lgio-2.0 -lz -lresolv -lgmodule-2.0 -ldl -lgobject-2.0 -lffi -lglib-2.0 -lpcre
> > Is that true if you run that command on the "wrong" architecture? In
> > other words, I would expect it to strip out the multiarch path that
> > matches your local system, but if you run the same command on (say) arm
> > with the same file, for it to *not* strip out the path. Which potentially
> > causes problems.
>
> You are right: I hand-edited gmime-2.6.pc for testing purposes, assuming
> the package was built on i386. My primary architecture is amd64. This
> results in
>
> # pkg-config --static --libs gmime-2.6
> -pthread -L/usr/lib/i386-linux-gnu -lgmime-2.6 -lnsl -lgpgme-pthread
> -lassuan -lgpg-error -lpthread -lgio-2.0 -lz -lresolv -lgmodule-2.0 -ldl
> -lgobject-2.0 -lffi -lglib-2.0 -lpcre
>
Yes it is the problem and instead of having it for -L flag I get it for -I on a include path.
In this case maybe it is safe because linker will not choose foreign arch for linking but for -I it change padding of structure and api/abi
Bastien
>
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>