Le 20 sept. 2013 23:06, "Russ Allbery" <rra@debian.org> a écrit :
>
> Michael Biebl <biebl@debian.org> writes:
>
> > The multiarch -L path is coming from `gpgme-config --libs`.
> > The maintainer took the advice and tried to move the .pc file to a
> > multiarch location (even though the library itself was not
> > multiarchified). This resulted in [1].
>
> Yes, at the least the message should make clear that you have to multiarch
> the whole package to fix this.
>
> > 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.
>
> > It seems reasonable to therefore downgrade this message to a warning.
>
> Warning does seem like the right level regardless, since most of the
> circumstances under which this can actually break something are fairly
> obscure.
I personnaly break by multiarching ImageMagick and forgetting to move the PC file. And it lead to ftbs in other package in arch other than amd64.
> --
> Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
>