Hi Jussi,
On Sun, Dec 02, 2018 at 06:48:17PM +0200, Jussi Pakkanen wrote:
> I did try it and it worked without problems, which was very confusing.
That wasn't clear from your previous mail.
> However I ran some more tests and it seems that (at least on my tests
> with amd64 + armhf) this thing i
On Sun, Dec 2, 2018 at 8:12 AM Helmut Grohne wrote:
> Furthermore, I think that it is very inefficient if you ask me to try
> various things. I put up with the cost of providing a minimized test
> case. Effectively, I already did the work you are now requesting me to
> do. Did you even attempt to
Hi Jussi,
On Sun, Dec 02, 2018 at 12:02:53AM +0200, Jussi Pakkanen wrote:
> It could be that the system picks the wrong pkg-config by accident.
What kind of accident are you envisioning here? It works in the very
same setting if I remove the unused "glib = dependency('glib-2.0')"
line. And why sh
On Thu, Nov 8, 2018 at 9:51 PM Helmut Grohne wrote:
> You notice that the native compiler invocation is asked to link the host
> architecture libglib-2.0.so. That's wrong.
>
> To see that this is actually the first depenency() call leaking into the
> next call, we can simply remove the first (unn
Package: meson
Version: 0.48.1-1
User: helm...@debian.org
Usertags: rebootstrap
Meson wrongly caches the result of a dependency() call. If you need a
dependency for both the build architecture and host architecture, meson
caches uses the results from the first invocation for the other
invocation.
5 matches
Mail list logo
