* Bob Proulx <[EMAIL PROTECTED]> [030708 18:19]:
> > It's almost the same as your version, but we using the same
> > code as the others might be nice anyway. As a bonus, you
> > can run it as 'linux64'.
>
> Just as a general comment I dislike programs which change their
> behavior based upon their
Arnd Bergmann wrote:
> Right. I now found the 'official site' for the tool at
> ftp://ftp.x86-64.org/pub/linux-x86_64/tools/linux32/
>
> It's almost the same as your version, but we using the same
> code as the others might be nice anyway. As a bonus, you
> can run it as 'linux64'.
Just as a gene
* Arnd Bergmann <[EMAIL PROTECTED]> [030707 15:22]:
> On Monday 07 July 2003 21:07, Bart Trojanowski wrote:
>
> > If I understand what linux32 does the program is quite trivial.
>
> Right. I now found the 'official site' for the tool at
> ftp://ftp.x86-64.org/pub/linux-x86_64/tools/linux32/
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 07 July 2003 21:07, Bart Trojanowski wrote:
> If I understand what linux32 does the program is quite trivial.
Right. I now found the 'official site' for the tool at
ftp://ftp.x86-64.org/pub/linux-x86_64/tools/linux32/
It's almost the same
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [030707 14:41]:
> Since other ISVs are adopting the use of linux32, I recommend
> consistency here. AFAIK, the basic functions of linux32 are (1) to
> change the architecture reported by uname, and (2) to adjust the
> available address space for that process
, July 07, 2003 11:07 AM
To: Miller, Marc; debian-x86-64@lists.debian.org
Cc: [EMAIL PROTECTED]; debian-dpkg@lists.debian.org;
debian-devel@lists.debian.org
Subject: Re: gcc on a biarch system
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [030707 13:44]:
> I've seen such an animal (tha
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [030707 13:44]:
> I've seen such an animal (that switches the personality and the
> architecture reported by uname) in some distributions; it's called
> linux32.
After Arnd's proposal, I wrote one for my own use, but now I am
curious...
Would there be a u
ebian-dpkg@lists.debian.org; debian-devel@lists.debian.org
Subject: Re: gcc on a biarch system
On Saturday 05 July 2003 19:44, Bart Trojanowski wrote:
> On amd64, we currently have a biarch-gcc that builds 32bit binaries by
> default, and 64bit ones with a -m64 option. Coding debian/rules for
* Arnd Bergmann <[EMAIL PROTECTED]> [030705 17:14]:
> No, that's exactly the wrong way around. dpkg-libinfo (at least the
> current proposal) uses dpkg-architecture to find the target
> architecture and dpkg-architecture in turn calls gcc to get that.
> It makes sense this way, although dpkg-libinf
On Saturday 05 July 2003 19:44, Bart Trojanowski wrote:
> On amd64, we currently have a biarch-gcc that builds 32bit binaries by
> default, and 64bit ones with a -m64 option. Coding debian/rules for this
> is pretty trivial but still requires some ugly architecture specific
> hacks in each debian/
On Sat, Jul 05, 2003 at 01:44:31PM -0400, Bart Trojanowski wrote:
> On amd64, we currently have a biarch-gcc that builds 32bit binaries by
> default, and 64bit ones with a -m64 option. Coding debian/rules for this
> is pretty trivial but still requires some ugly architecture specific
> hacks in ea
On Sat, Jul 05, 2003 at 01:44:31PM -0400, Bart Trojanowski wrote:
> I propose obtaining the gcc specific options from a dpkg-libinfo
> (introduced by Gerhard Tonn's lib64 patches) or dpkg-architecture.
> debian/rules can query for said options, and use them in order to build
> for a given host arch
On amd64, we currently have a biarch-gcc that builds 32bit binaries by
default, and 64bit ones with a -m64 option. Coding debian/rules for this
is pretty trivial but still requires some ugly architecture specific
hacks in each debian/rules.
These hacks can be troublesome if the default compile ta
13 matches
Mail list logo
