On 05/13/2013 10:31 AM, The Wanderer wrote:
On 05/13/2013 10:22 AM, The Wanderer wrote:
On 05/13/2013 09:46 AM, Wookey wrote:
Hmm. Do the parts of the 64-bit tree that the 32-bit side
compiles against end up installed in a final installation (as
libraries?) or are they really just intermediate 'during build'
items?
They do end up getting installed, though whether as libraries or
not I don't recall offhand.
I think I may have misunderstood this question.
Some of the 64-bit components which would ordinarily get installed in
a 64-bit-only build get omitted from the final install (and possibly
from compilation) in a combined build, because the 32-bit components
replace them.
Argh. I think I got this wrong again. If I'm not mistaken, it's actually
closer to the other way around.
Post-install-time, the 32-bit build tree contains symlinks pointing to
the 64-bit build tree for three directories: fonts/, server/, and tools/.
Post-install-time, the 64-bit build tree contains symlinks pointing to
the 32-bit build tree for two executables: loader/wine and
loader/wine-preloader.
Everything else appears to be separate for the two build trees. As far
as I'm aware, the installs for both of them run completely separately.
However, since the directions call for installing the 32-bit version
first and the 64-bit version second, some files installed by the 32-bit
version may get overwritten. If that happens, I have no idea which ones.
I would have to investigate the build process more closely in order
to say much more with any certainty.
This remains true.
--
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
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51910019.5030...@fastmail.fm
