Re: Compiling true amd64 binaries on woody?
Turbo Fredriksson <[EMAIL PROTECTED]> writes: > I'm still stuck on/in woody on all my systems. Can't change just > yet (I'm working on it), but in the meantime I'm trying to > create packages that's true amd64. > > The kernel is from sarge (true amd64 kernel), but the rest > of the system is pure woody. > > I was hoping that all I had to do was to get dpkg recompiled, > and that worked somewhat. That's quite impossible. It is hard enough to build 64bit software manualy on i386. What you need is a 64bit chroot. Use cdebootstrap -aamd64 to make one and then work in there. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiling true amd64 binaries on woody?
Turbo Fredriksson wrote: > I'm still stuck on/in woody on all my systems. Can't change just > yet (I'm working on it), but in the meantime I'm trying to > create packages that's true amd64. But there is no woody amd64. So your statement is confusing. If you are talking about woody do you mean x86 woody? You want to cross compile to produce an amd64 binary on woody? If that is your question then I think that is too difficult. Better to create a sid chroot and cross compile from there. If that is not what you are asking then please explain further. > The kernel is from sarge (true amd64 kernel), but the rest > of the system is pure woody. Again, there is no woody for amd64. The earliest possible would be an early sarge release candidate. So your statement confuses me. Bob signature.asc Description: Digital signature
Compiling true amd64 binaries on woody?
I'm still stuck on/in woody on all my systems. Can't change just
yet (I'm working on it), but in the meantime I'm trying to
create packages that's true amd64.
The kernel is from sarge (true amd64 kernel), but the rest
of the system is pure woody.
I was hoping that all I had to do was to get dpkg recompiled,
and that worked somewhat.
Looking at what's happening when 'debuild' is building a package,
I found 'dpkg-architecture -qDEB_HOST_ARCH' (which is run by
'dpkg-gencontrol'). Running 'dpkg-architecture' without params
will give me:
- s n i p -
DEB_BUILD_ARCH=amd64
DEB_BUILD_GNU_CPU=x86_64
DEB_BUILD_GNU_SYSTEM=linux
DEB_BUILD_GNU_TYPE=x86_64-linux
DEB_HOST_ARCH=i386
DEB_HOST_GNU_CPU=i386
DEB_HOST_GNU_SYSTEM=linux
DEB_HOST_GNU_TYPE=i386-linux
- s n i p -
So, is there a trick to fool 'dpkg-architecture' ('debuild' or
'dpkg-gencontrol' etc) that it should use the 'DEB_BUILD_ARCH'
instead?
I guess I _could_ hack '/usr/lib/dpkg/controllib.pl:findarch()'
to retreive the 'DEB_BUILD_ARCH' value instead of the current
'DEB_HOST_ARCH' but I was hoping for something smarter...
--
AK-47 Panama 747 Ortega Noriega Albanian critical nuclear security
toluene counter-intelligence Serbian ammunition cracking BATF
[See http://www.aclu.org/echelonwatch/index.html for more about this]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
