On Fri, Sep 22, 2006 at 11:38:30PM -0700, Brian Morris wrote:
> it says 21.4 there. that is the mass build a guy made in
> april for mac68k. it is not necessarily tested, but it did build.
ok, that would mean the old problem that I encountered was
fixed or maybe xemacs reintroduced the old lisp en
well if our kernels work and i am able
to get through this lisp book i am reading
then maybe i can help, at least test it out.
brian
(meanwhile i may as well install the sarge
version, i guess)
On 9/23/06, Richard Zidlicky <[EMAIL PROTECTED]> wrote:
On Fri, Sep 22, 2006 at 11:38:30PM -0700, Br
On Thu, Sep 21, 2006 at 09:55:18PM -0700, Brian Morris wrote:
> netbsd has emacs21 and xemacs21 running under
> mac68k (its on their download page as of Now).
iirc the change that broke xemacs for m68k-linux was somewhere
between 21.1.10 and 21.1.14, what versions run on netbsd?
Regards
Richard
it says 21.4 there. that is the mass build a guy made in
april for mac68k. it is not necessarily tested, but it did build.
ftp://ftp.netbsd.org/pub/NetBSD/packages/packages-2006Q1/NetBSD-3.0/m68k/editors/
On 9/22/06, Richard Zidlicky <[EMAIL PROTECTED]> wrote:
On Thu, Sep 21, 2006 at 09:55:18PM
netbsd has emacs21 and xemacs21 running under
mac68k (its on their download page as of Now).
in their general packages section they also
list emacs20 and a lisp-emacs package which
appears to be from 12/20/20002.
they claim on their download page their packages
run under any port, ie kernel inde
On Tue, Aug 22, 2006 at 08:56:51PM +0200, Roman Zippel wrote:
> Hi,
>
> On Tue, 22 Aug 2006, Stephen R Marenka wrote:
>
> > Any interest in tackling emacs21 or gcj-4.1? ;)
>
> I looked shortly into exmacs21 and that's a bit more complicated. It could
> be a cache issue, so if someone tried to b
On Mon, Sep 18, 2006 at 02:23:47AM +0200, Roman Zippel wrote:
> Hi,
>
> On Fri, 8 Sep 2006, Wouter Verhelst wrote:
>
> > grmbl, build failed with corrupt files, and dmesg shows bad blocks on
> > the disk. I'll need to either replace it, or start doing some fsck; both
> > will take some time.
> >
Hi,
On Fri, 8 Sep 2006, Wouter Verhelst wrote:
> grmbl, build failed with corrupt files, and dmesg shows bad blocks on
> the disk. I'll need to either replace it, or start doing some fsck; both
> will take some time.
>
> If anyone else feels like taking this on, be my guest
I just submitted a p
On Tue, Sep 05, 2006 at 06:39:32PM +0200, Wouter Verhelst wrote:
> On Tue, Sep 05, 2006 at 11:42:05AM +0200, Roman Zippel wrote:
> > It might also be worth to retry subversion, I checked it, but I didn't see
> > that failure, so if that persists, I'll have to recheck.
>
> I'm doing so manually ri
On Tue, Sep 05, 2006 at 11:42:05AM +0200, Roman Zippel wrote:
> It might also be worth to retry subversion, I checked it, but I didn't see
> that failure, so if that persists, I'll have to recheck.
I'm doing so manually right now, with knowledge of the maintainer (had
discussed it with him on IRC
Hi,
On Tue, 5 Sep 2006, Stephen R Marenka wrote:
> > gcc-4.1.12 is now in the archive, that means kdelibs should compile now. :)
>
> I'll get on that. 4.1.1ds1-13 should be done real soon now. I'm
> surprised -12 got built since -13 came out 30 minutes later.
I think Matthias started the build
On Tue, Sep 05, 2006 at 11:42:05AM +0200, Roman Zippel wrote:
> Hi,
>
> gcc-4.1.12 is now in the archive, that means kdelibs should compile now. :)
I'll get on that. 4.1.1ds1-13 should be done real soon now. I'm
surprised -12 got built since -13 came out 30 minutes later.
> I looked at the gnust
Hi,
gcc-4.1.12 is now in the archive, that means kdelibs should compile now. :)
I looked at the gnustep problems, but they seem to be gone with a new
gnustep-base, so recompiling this one should help.
It might also be worth to retry subversion, I checked it, but I didn't see
that failure, so if
On Wed, Aug 23, 2006 at 12:10:50PM +0200, Roman Zippel wrote:
> Hi,
>
> On Tue, 22 Aug 2006, Stephen R Marenka wrote:
>
> > It looks like libgc needs the patch in 383817. libffi is part of gcc,
> > which is preparing for a -12. After that we should rebuilt gcj and see
> > if it works?
>
> That's
Hi,
On Tue, 22 Aug 2006, Stephen R Marenka wrote:
> It looks like libgc needs the patch in 383817. libffi is part of gcc,
> which is preparing for a -12. After that we should rebuilt gcj and see
> if it works?
That's the plan. :) gcc has it its own copy of libgc, so luckily it
doesn't need to w
On Tue, Aug 22, 2006 at 08:56:51PM +0200, Roman Zippel wrote:
> Hi,
>
> On Tue, 22 Aug 2006, Stephen R Marenka wrote:
>
> > Any interest in tackling emacs21 or gcj-4.1? ;)
>
> I looked shortly into exmacs21 and that's a bit more complicated. It could
> be a cache issue, so if someone tried to b
Hi,
On Tue, 22 Aug 2006, Stephen R Marenka wrote:
> Any interest in tackling emacs21 or gcj-4.1? ;)
I looked shortly into exmacs21 and that's a bit more complicated. It could
be a cache issue, so if someone tried to build it on 030 machine, it might
help to confirm the suspicion.
I haven't rea
On Tue, Aug 22, 2006 at 06:56:42PM +0200, Roman Zippel wrote:
> Hi,
>
> On Tue, 22 Aug 2006, Stephen R Marenka wrote:
>
> > Your fixes have allowed a bunch of packages to build!
>
> Wait for the next update. :)
> It should take care of most the issues on the DebianM68kGcc page with the
> most i
Hi,
On Tue, 22 Aug 2006, Stephen R Marenka wrote:
> Your fixes have allowed a bunch of packages to build!
Wait for the next update. :)
It should take care of most the issues on the DebianM68kGcc page with the
most important one probably the kdelibs problem.
> log4cxx seems a puzzle though.
>
On Tue, Aug 22, 2006 at 11:43:18AM +0200, Roman Zippel wrote:
> cppunit and grace as well. I have to check mpfr, but everything else
> shouldn't need this anymore.
> BTW over the weekend I checked the failed nano build and it builds fine
> here, so I guess it can just be requeued.
thanks, done.
Hi,
On Mon, 21 Aug 2006, Stephen R Marenka wrote:
> > BTW does anyone have a list of packages, which are currently compiled with
> > -O0 or -O1? It would be nice to get rid of it again.
> > I'm just seeing a failed erlang compiled because it timed out in the test
> > suite, but it's also compil
On Sun, Aug 20, 2006 at 07:35:29PM +0200, Roman Zippel wrote:
> Hi,
>
> BTW does anyone have a list of packages, which are currently compiled with
> -O0 or -O1? It would be nice to get rid of it again.
> I'm just seeing a failed erlang compiled because it timed out in the test
> suite, but it's
Hi,
BTW does anyone have a list of packages, which are currently compiled with
-O0 or -O1? It would be nice to get rid of it again.
I'm just seeing a failed erlang compiled because it timed out in the test
suite, but it's also compiled with -O0...
bye, Roman
--
To UNSUBSCRIBE, email to [EMAI
On Tue, Aug 15, 2006 at 03:54:21PM +0200, Roman Zippel wrote:
> Hi,
>
> Matthias is working on a new gcc upload, which should appear later this
> week and which will contain a number of m68k related bug fixes, so it
> would be quite important to get it as soon as possible to the buildd.
>
> It f
On Tue, Aug 15, 2006 at 03:54:21PM +0200, Roman Zippel wrote:
> Hi,
>
> Matthias is working on a new gcc upload, which should appear later this
> week and which will contain a number of m68k related bug fixes, so it
> would be quite important to get it as soon as possible to the buildd.
-11 mayb
Hi,
Matthias is working on a new gcc upload, which should appear later this
week and which will contain a number of m68k related bug fixes, so it
would be quite important to get it as soon as possible to the buildd.
It fixes a bug which caused to break binutils and thus linker problems
and binu
26 matches
Mail list logo
