On Tue, Aug 29, 2017 at 06:19:42PM +0100, akhiezer wrote:
> > Date: Tue, 29 Aug 2017 17:44:13 +0100
> > From: Ken Moffat
> >
> >
> > I look forward to your fork where you show us how to automate this.
> > Bonus points for using no more than 4 cores on machines with more
>
On Tue, Aug 29, 2017 at 06:42:48PM +0200, Pierre Labastie wrote:
> Hi,
>
>
> I am trying to install new rust (for new firefox), and the command "./x.py
> dist --install" returned an error (sorry I have mucked my logs, but
> roughly, --install is not an option). I run "./x.py install" instead,
akhiezer wrote:
The matter is clearly, obviously, not about how long a single error
persists.
It is about how long folks remain addicted to donkey-tasks; the
inevitable stream, cycle, of repeated types of errors that ensue; and
the inevitable stream, cycle, of repeated types of donkey-tasks
> From: Bruce Dubbs
> Date: Tue, 29 Aug 2017 10:48:07 -0500
>
> akhiezer wrote:
> >> From: Wayne Blaszczyk
> >> Date: Tue, 29 Aug 2017 19:16:41 +1000
> >>
> >> Again, it seemed not to change from the previous version.
> >>
> >
> >
> > The central
On Tue, Aug 29, 2017 at 12:42:35PM +0100, akhiezer wrote:
> > From: Wayne Blaszczyk
> > Date: Tue, 29 Aug 2017 19:16:41 +1000
> >
> > Again, it seemed not to change from the previous version.
> >
>
>
> The central issue is that much of that 'header' info
>
Hi,
I am trying to install new rust (for new firefox), and the command
"./x.py dist --install" returned an error (sorry I have mucked my logs,
but roughly, --install is not an option). I run "./x.py install"
instead, and it seems to work. Although I am amazed it looks like it
recompiles
Ken Moffat wrote:
On Tue, Aug 29, 2017 at 07:11:30PM +1000, Wayne Blaszczyk wrote:
It seems to not have changed since 55.0.1.
Thanks for noticing, and to Bruce for fixing it. I looked at the
wrong place in my notes while I was preparing, highlighted it, then
when I edited I deleted what was
On Tue, Aug 29, 2017 at 07:11:30PM +1000, Wayne Blaszczyk wrote:
> It seems to not have changed since 55.0.1.
>
> Regards,
> Wayne.
Thanks for noticing, and to Bruce for fixing it. I looked at the
wrong place in my notes while I was preparing, highlighted it, then
when I edited I deleted what
akhiezer wrote:
From: Wayne Blaszczyk
Date: Tue, 29 Aug 2017 19:16:41 +1000
Again, it seemed not to change from the previous version.
The central issue is that much of that 'header' info
(dates/checksums/sizes/build-times/...) get input manually, instead of
done
I believe this has something to do with the generation of the signal
marshallers. I got the same vte error after building the 2.53 branch of GLib.
See this for more info:
https://git.gnome.org/browse/vte/commit/?id=fa3bc86008cfe517dbb05deb4dff0059f3749c95
Ryan
On 08/27/17 06:08 AM, Christoph
> From: Wayne Blaszczyk
> Date: Tue, 29 Aug 2017 19:16:41 +1000
>
> Again, it seemed not to change from the previous version.
>
The central issue is that much of that 'header' info
(dates/checksums/sizes/build-times/...) get input manually, instead of
done
Again, it seemed not to change from the previous version.
Regards,
Wayne.
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
12 matches
Mail list logo