On Mon, 19 Apr 2010, Thorsten Glaser wrote:
> Wouter Verhelst dixit:
>
> >could we look into re-bootstrapping the port and starting to build
>
> I?m currently building gcc-4.4 and other up-to-date packages. Once I get
> gcc-4.4 to work ... we can ask doko to put the patches into 4.4.
>
> Then
Wouter Verhelst dixit:
>could we look into re-bootstrapping the port and starting to build
I’m currently building gcc-4.4 and other up-to-date packages. Once
I get gcc-4.4 to work (got multiarch/multilib working, but libfortran
can't be built for -mfidoa due to incompatible inline assembly in a
s
On Mon, Apr 19, 2010 at 09:33:54PM +1000, fth...@telegraphics.com.au wrote:
>
> On Mon, 19 Apr 2010, Wouter Verhelst wrote:
>
> > Does anyone know what the status of this support is in libc?
>
> This was the situation a month ago--
> http://lists.debian.org/debian-68k/2010/03/msg00014.html
Righ
On Mon, Apr 19, 2010 at 01:01:38PM +0200, Wouter Verhelst wrote:
> > Well, motivation is somewhat lower after not being an official part of
> > Debian anymore, but I still like m68k and would keep my machines running.
> I could revive some hosts, too, though it would involve some work.
> But the p
On Mon, 19 Apr 2010, Wouter Verhelst wrote:
> Does anyone know what the status of this support is in libc?
This was the situation a month ago--
http://lists.debian.org/debian-68k/2010/03/msg00014.html
It appears that the eglibc repo has the patches in HEAD now.
Finn
--
To UNSUBSCRIBE, email
On Mon, Apr 19, 2010 at 12:05:39PM +0200, Ingo Jürgensmann wrote:
> On Mon, Apr 19, 2010 at 11:43:29AM +0200, Wouter Verhelst wrote:
>
> > Or have we collectively lost interest and should we just let it die?
>
> Well, motivation is somewhat lower after not being an official part of
> Debian anymo
On Mon, Apr 19, 2010 at 11:43:29AM +0200, Wouter Verhelst wrote:
> Or have we collectively lost interest and should we just let it die?
Well, motivation is somewhat lower after not being an official part of
Debian anymore, but I still like m68k and would keep my machines running.
So, when there's
Hi all,
GCC 4.5 was released not so long ago, and one of the new features listed
on its changes page[1] is TLS support for m68k/ColdFire.
Does anyone know what the status of this support is in libc? If so,
could we look into re-bootstrapping the port and starting to build
up-to-date packages agai
8 matches
Mail list logo