On Sun, Jul 11, 2010 at 03:40:16AM +0100, Wookey wrote:
> I don't think you can re-use Debian arch names. They mean something
> and if it's been used at all widely you can't just change it later (or
> at least not for 10-20 years or so). (armeb was little-enough used
> that we probably could change
> On 12/07/10 14:34, Paul Brook wrote:
> > Anything that relies on the target triplet is going to break as soon
> > as you move outside a pure Debian system. i.e. any patches relying on
> > a particular target triplet are inherently Debian specific, and IMO
> > should never be pushed upstream.
>
>
On 12/07/10 14:34, Paul Brook wrote:
Anything that relies on the target triplet is going to break as soon
as you move outside a pure Debian system. i.e. any patches relying on
a particular target triplet are inherently Debian specific, and IMO
should never be pushed upstream.
Which is why we're
> On 09/07/10 19:16, Hector Oron wrote:
> >arm-hardfloat-linux-gnueabi
>
> This would be the path of least resistance. You can do this without
> breaking much, and without annoying anybody upstream. You might need to
> do a few hacks to various packages that want to know which ABI is in
> use
On 09/07/10 19:16, Hector Oron wrote:
>arm-hardfloat-linux-gnueabi
This would be the path of least resistance. You can do this without
breaking much, and without annoying anybody upstream. You might need to
do a few hacks to various packages that want to know which ABI is in
use, but proba
Good day Martin.
The ( only ) installer works fine, but i'm not be able to boot the system after
the installation.
This is the output:
***
Marvell Serial ATA Adapter
Integrated Sata device found
[0 1 0]: Enable DMA mode
Device 1 @ 0 1:
Mod
Hey
Just wanted to raise that it might be wise to check whether any ABI
changes or tweaks are in the pipe upstream before kicking a new port;
it's not happening that frequently after all, so worth the extra
burden.
I'm happy to take action to check that with upstream GCC folks, and
7 matches
Mail list logo
