Re: Depends: libfoo:foreign ???
On 05/14/2013 09:40 AM, Goswin von Brederlow wrote:
Could you build a 32bit only, a 64bit only and a 32+64bit wine, run
make install for each case and generate a file list for each?
Including "file" output so it shows what is 32bit and what 64bit in
the mixed case.
I have these file lists now, along with several other lists based on the
same data; they aren't attached because the combination of all 5 "file"
lists alone would be close to 1.5MB, and I'm not sure what's acceptable
on-list here. I can provide them, here or elsewhere, on request.
I've spent some time considering them, but I'm not sure what conclusions
to draw.
Also what happens if you take the list for 32+64bit and then manually
pick the respective files from the 32bit only and 64bit only tree
according to bitness of the files? Does that produce something
functional? Equal to the 32+64bit build?
As there are over 3000 files involved, this is a fairly big task to
handle manually, and I haven't yet found the time to either do it by
hand or devise a way to automate it. This is therefore still pending.
I can already say that it won't be binary identical to the 64+32 build,
because even the 64-bit standalone build isn't binary identical to the
64-bit side of a combined build (even though they're configured the
exact same way). I'm not sure what the differences are, though vbindiff
confirms that (in at least one file selected at random) it's not just a
few random bytes.
I'm coming to lean towards the conclusion that further work on this
would probably be better done in the context of the Debian Wine
packaging team, if not (for some parts of it) Wine upstream...
--
The Wanderer
Warning: Simply because I argue an issue does not mean I agree with any
side of it.
Every time you let somebody set a limit they start moving it.
- LiveJournal user antonia_tiger
Reply to: