[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] Extra linked objects in qemu-system-aarch64
From: |
Sean Bruno |
Subject: |
Re: [Qemu-devel] Extra linked objects in qemu-system-aarch64 |
Date: |
Mon, 26 Dec 2016 13:36:42 -0700 |
User-agent: |
Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 |
On 12/26/16 12:55, Peter Maydell wrote:
> On 26 December 2016 at 15:01, Sean Bruno <address@hidden> wrote:
>> FreeBSD detects undeclared dependencies when building "ports" and I've
>> been ignoring a bunch of warnings from qemu-system-aarch64 that I'm a
>> bit puzzled by. It appears that we're linking qemu-system-aarch64
>> differently than the other system emulator targets:
>>
>> https://gist.github.com/seanbruno/dd992cc1e425d708e53dc0fd0f958b92
>>
>> I would have expected that all the system targets have the same non-qemu
>> objects linked against it. Is this something specific to the aarc64
>> emulator that needs to be there?
>
> You don't give the other system targets for comparison so it's
> hard to tell. I would expect for instance that the system
> emulators would pull in various things like X11 for the GUI.
> The link lines ought not to be any different, though -- often
> aarch64 appears in warnings just because it happens to be
> lexicographically the first target architecture. Is the
> ports setup just suppressing later identical warnings about
> the same libraries on other binaries?
>
> In any case, it looks like a packaging problem to me.
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209813
> might or might not be relevant to whether this should be
> fixed in the QEMU packaging or in the handling of the
> things like Gnome we might be linking against (just a
> random related-looking google hit).
>
> thanks
> -- PMM
>
Agreed. I'll follow up with freebsd portmgr folks.
sean
signature.asc
Description: OpenPGP digital signature