* Andrew M.A. Cater <[EMAIL PROTECTED]> [030728 18:06]:
>
> I was actually asked directly at work today what I thought was
> going to happen to Red Hat and whether Debian supported the AMD64.
>
> I've seen a couple of posts on this topic since about March.
>
> Anybody care to sum up in words sui
* 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-
* [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
* [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
For those that will be attending OLS later this month...
http://www.linuxsymposium.org/2003/view_abstract.php?talk=192
I have scheduled a BoF session for Thursday July 24 at 20:00 to meet
people interested in the Debian port to AMD64.
Hope to see you there.
Regards,
Bart.
--
* 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 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
Hello,
I was curious to know if anyone would be any interest among the Debian
developers attending OLS (www.linuxsymposium.org) this summer to discuss
the future of the Debian port to AMD64. I will be securing us a space
with the organizers, but if there is only a low volume of interested
bodie
* Mark Shuttleworth <[EMAIL PROTECTED]> [030427 16:59]:
> I've configured and built the kernel, using gcc-2.95, make bzImage and
> modules, installed modules under /lib/modules/2.5.68. Everything goes
> fine except for a bunch of depmod errors during the 'make
> modules_install' which I'm guessi
* Gunnar Wolf <[EMAIL PROTECTED]> [030426 22:29]:
> > > >>> 1a. create a stripped down version for i386, i.e. required/important
> > > >>> and go for i486.
> > > >> Is there much performance improvement in dropping i386 in favour of
> > > >> i486+?
> > >
> > > > - Integrated math coprocessor
* Mark Brown <[EMAIL PROTECTED]> [030426 12:21]:
> On Sat, Apr 26, 2003 at 10:08:12AM -0400, Bart Trojanowski wrote:
>
> > For openssl there is a huge improvement. I was doing benchmarks on
> > openssl (they were done for internally at a company I no longer work
>
* Darren Salt <[EMAIL PROTECTED]> [030426 10:26]:
> I demand that José Luis Tallón may or may not have written...
>
> > At 19:55 26/04/2003 +1000, you wrote:
> >> On Sat, Apr 26, 2003 at 09:41:14AM +0200, Andreas Metzler wrote:
> >>> 1a. create a stripped down version for i386, i.e. required/impor
* Hamish Moffatt <[EMAIL PROTECTED]> [030426 05:57]:
> On Sat, Apr 26, 2003 at 09:41:14AM +0200, Andreas Metzler wrote:
> > 1a. create a stripped down version for i386, i.e. required/important
> > and go for i486.
>
> Is there much performance improvement in dropping i386 in favour of
> i486+?
* Grzegorz B. Prokopski <[EMAIL PROTECTED]> [030426 04:45]:
> Anyway - I am not using any true 386 systems since years,
> so maybe first solution would be to just make i386 mean
> "i486 and higher". If there's *real* need for i386, then
> it should be possible to create i386true sub-distro in the f
Here is an email from an AMD rep posted on the x86-64 developer mailing list.
B.
---
Date: Fri, 25 Apr 2003 11:56:56 -0700
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [discuss] From AMD -- RE: [discuss] x86_64 -> amd64 renaming?
All,
You're correct, AMD is trying to minimize use of
* Michael Banck <[EMAIL PROTECTED]> [030424 19:26]:
> On Thu, Apr 24, 2003 at 06:27:34PM -0400, Bart Trojanowski wrote:
> > A bug on the lack of a debian-x86-64 mailing list has been opened (162668).
> >
> > All that can be done has been done -- it's out
* Andreas Tille <[EMAIL PROTECTED]> [030424 17:18]:
> On Thu, 24 Apr 2003, Jose Carlos Garcia Sogo wrote:
>
> > I meant "in the meantime". I think that the list in lists.d.o must be
> > created, but as this will take some time and seems that there are some
> > people interested in this, I th
* Gunnar Wolf <[EMAIL PROTECTED]> [030424 16:36]:
> ...But IA64 is the name for the platform, as opposed to a specific
> implementation. We also refer to the Pentiums, Athlons and their smaller
> cousins as x86 or i386 chips[1]. The right naming should follow the
> architecture's name, not a specif
* Andreas Tille <[EMAIL PROTECTED]> [030424 14:17]:
> On Thu, 24 Apr 2003, Bart Trojanowski wrote:
>
> > I thought this was a good idea. And since there was no such list yet I
> > requested the creation of 'debian-x86-64'. It will take 72 hours to
> > setu
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [030424 13:55]:
> On Thu, 24 Apr 2003, Bart Trojanowski wrote:
>
> > * Rich Payne <[EMAIL PROTECTED]> [030424 13:43]:
> > > > On a side note, it would seem that the 'x86-64' branding may be dropped
> > &
* Rich Payne <[EMAIL PROTECTED]> [030424 13:43]:
> > On a side note, it would seem that the 'x86-64' branding may be dropped
> > in favor of 'AMD64'.
> >
> > http://www.theinquirer.net/?article=9133
> > (7th paragraph)
> >
> > The Inquirer is not always right, so I am not sure if I should t
* Jose Carlos Garcia Sogo <[EMAIL PROTECTED]> [030424 03:56]:
> Though I think that a debian-x86-64 list is worth you can open a
> project in alioth in the interim. You could use it also to have a CVS
> repo for patches or packages you need to build.
I thought this was a good idea. And since th
22 matches
Mail list logo
