Bug#575158: dpkg: Add new 'e500' architecture to triplettable and ostable

2010-04-30 Thread Sebastian Andrzej Siewior
* Guillem Jover | 2010-04-30 06:10:05 [+0200]: >Hi! Hi Guillem, >On Thu, 2010-04-29 at 21:09:20 -0500, Moffett, Kyle D wrote: >> I believe we have consensus on the port architecture name of "powerpcspe". >> Is there any chance we can get the attached patch merged soon? I'd like to >> move forwar

Bug#575158: dpkg: Add new 'e500' architecture to triplettable and ostable

2010-04-29 Thread Guillem Jover
Hi! On Thu, 2010-04-29 at 21:09:20 -0500, Moffett, Kyle D wrote: > I believe we have consensus on the port architecture name of "powerpcspe". > Is there any chance we can get the attached patch merged soon? I'd like to > move forward with getting an unofficial debian-ports.org repository created

Bug#575158: dpkg: Add new 'e500' architecture to triplettable and ostable

2010-04-29 Thread Moffett, Kyle D
Raphael, I believe we have consensus on the port architecture name of "powerpcspe". Is there any chance we can get the attached patch merged soon? I'd like to move forward with getting an unofficial debian-ports.org repository created and they won't do that until a patch has been merged to upstre

Bug#575158: dpkg: Add new 'e500' architecture to triplettable and ostable

2010-04-23 Thread Sebastian Andrzej Siewior
* Moffett, Kyle D | 2010-04-22 19:17:17 [-0500]: >Not really... If you build GCC with "--enable-e500_double" it produces code >that is not quite binary compatible with code generated without that option, >because it indicates that the GPRs have an extra shadow 32 high bits that >can be only access

Bug#575158: dpkg: Add new 'e500' architecture to triplettable and ostable

2010-04-22 Thread Moffett, Kyle D
On 2010/04/18 08:39, "Sebastian Andrzej Siewior" wrote: > * Guillem Jover | 2010-04-16 09:01:16 [+0200]: >> Do you see this as a possible workable solution, or is it completely >> unnacceptable? Did I miss something besides what I listed here? > > I don't think it is acceptable due to the points I

Bug#575158: dpkg: Add new 'e500' architecture to triplettable and ostable

2010-04-18 Thread Sebastian Andrzej Siewior
* Guillem Jover | 2010-04-16 09:01:16 [+0200]: >Hi! Hi Guillem, >On Thu, 2010-02-18 at 11:38:34 +0100, Sebastian Andrzej Siewior wrote: >> - variant two: a operation like a + b where we call in a library to >> compute the floating point operation. Here we would put the >> computation itself i

Bug#575158: dpkg: Add new 'e500' architecture to triplettable and ostable

2010-04-16 Thread Guillem Jover
Hi! [ Sorry for the delay, been moving house. ] First I wanted to comment on some things said on the bug reports and debian-devel. Yes, lpia was a mistake, I'd have preferred that the Ubuntu people would have created a new repository with a rebuilt i386 architecture tailored for Atom processors,

Bug#575158: dpkg: Add new 'e500' architecture to triplettable and ostable

2010-04-08 Thread Moffett, Kyle D
Ping? Raphael, any chance we could get more discussion or agreement from the dpkg developers regarding the "e500v2" architecture name? Both Sebastian and I are in full agreement that the name "e500v2" most accurately describes the fundamental architecture. I've included the summarized rationale

Bug#575158: dpkg: Add new 'e500' architecture to triplettable and ostable

2010-03-29 Thread Sebastian Andrzej Siewior
* Moffett, Kyle D | 2010-03-25 17:49:33 [-0500]: >We can just use --enable-e500-double when building (recent?) GCC. Yep, looks good. >Ok, so hopefully we can all agree on "e500v2"? That's the name I'm going to >go ahead and use in my newest build-cycle. Yep, I think so. However we will see what

Bug#575158: dpkg: Add new 'e500' architecture to triplettable and ostable

2010-03-25 Thread Moffett, Kyle D
On 2010/03/25 16:39, "Sebastian Andrzej Siewior" wrote: > * Moffett, Kyle D | 2010-03-24 19:28:06 [-0500]: >> The e500v1 was never very popular and all of the available parts today >> support double-precision floating point GPRS. With that said, I'm actually >> not sure if my current compiler is

Bug#575158: dpkg: Add new 'e500' architecture to triplettable and ostable

2010-03-24 Thread Sebastian Andrzej Siewior
* Moffett, Kyle D | 2010-03-23 17:52:57 [-0500]: >Ah, my apologies. I'd actually already seen that one, but wasn't paying >enough attention when submitting the bugreport. I saw in your earlier bug report that you don't have everything built (yet). At [0] I have more or less complete port of an ol

Bug#575158: dpkg: Add new 'e500' architecture to triplettable and ostable

2010-03-23 Thread Moffett, Kyle D
On 2010/03/23 18:21, "Raphael Hertzog" wrote: > On Tue, 23 Mar 2010, Kyle Moffett wrote: >> It has the unfortunate GNU arch triplet of "powerpc-linux-gnuspe", when >> it should have been "powerpcspe-linux-gnu" or "e500-linux-gnu". This >> causes much the same problem and has the same solution as

Bug#575158: dpkg: Add new 'e500' architecture to triplettable and ostable

2010-03-23 Thread Raphael Hertzog
forcemerge 568123 575158 thanks On Tue, 23 Mar 2010, Kyle Moffett wrote: > It has the unfortunate GNU arch triplet of "powerpc-linux-gnuspe", when > it should have been "powerpcspe-linux-gnu" or "e500-linux-gnu". This > causes much the same problem and has the same solution as the lpia > architec

Bug#575158: dpkg: Add new 'e500' architecture to triplettable and ostable

2010-03-23 Thread Kyle Moffett
Package: dpkg Version: 1.15.5.6 Severity: wishlist Tags: patch At this time, we have the Debian binutils, gcc, and eglibc packages building cross-compilers for e500 correctly with just a few minor patches. A few other packages (libmpfr, libgmp) needed to be crossbuilt (with minor patches only to