On Mon, Apr 19, 2021 at 02:21:14PM -0500, Bruce Dubbs via blfs-dev wrote:
> On 4/19/21 1:09 PM, Ken Moffat via blfs-dev wrote:
> > On Sun, Apr 18, 2021 at 09:44:19PM -0500, Bruce Dubbs via blfs-dev wrote:
> > > On 4/18/21 5:36 PM, Ken Moffat via blfs-dev wrote:
> > > >
On Sun, Apr 18, 2021 at 09:44:19PM -0500, Bruce Dubbs via blfs-dev wrote:
> On 4/18/21 5:36 PM, Ken Moffat via blfs-dev wrote:
> > - Forwarded message from Ken Moffat via blfs-book
> > -
> >
> > Arghh - I sent this to -book.
> >
> > Date: Sun, 1
- Forwarded message from Ken Moffat via blfs-book
-
Arghh - I sent this to -book.
Date: Sun, 18 Apr 2021 23:03:22 +0100
From: Ken Moffat via blfs-book
To: blfs-b...@lists.linuxfromscratch.org
Cc: Ken Moffat
Subject: [blfs-book] RFC: Adding advisories chapter to the editor's guide
On Thu, Apr 15, 2021 at 01:24:13AM +0200, Tim Tassonis via blfs-dev wrote:
> Hi all
>
> When trying to push my changes to git, I got following error:
>
> timtas@dalglish:~/src/blfs-git$ git commit -a
> [trunk 8355679be] Upgrade to curl-7.76.1.
> 4 files changed, 15 insertions(+), 4 deletions(-)
I saw on phoronix that kde have set up repos for their patches.
There was a suggestion that these are patches kde devs have sent
upstream.
Top level is at https://invent.kde.org/qt although navigating is
slightly strange - somehow I managed to get to
https://invent.kde.org/qt/qt?page=1 which is
On Thu, Apr 01, 2021 at 12:54:26PM -0500, Bruce Dubbs via blfs-dev wrote:
> On 4/1/21 3:52 AM, Tim Tassonis via blfs-dev wrote:
> > Hi all
> >
> > I just discovered that curl apparently now also optionally supports
> > cmake as build system. Per official documentation however, ./configure
> >
On Thu, Apr 01, 2021 at 12:09:48PM +0200, Tim Tassonis via blfs-dev wrote:
>
> >
> > > However, there might be a lfs/blfs policy regarding preference for cmake
> > > that I am not aware of?
> >
> > If the upstream has a recommendation, just follow the upstream. Otherwise,
> > for
> >
On Sun, Mar 28, 2021 at 09:36:16PM +0200, Pierre Labastie via blfs-dev wrote:
> On Sun, 2021-03-28 at 18:42 +0100, Ken Moffat via blfs-dev wrote:
> > On Sun, Mar 28, 2021 at 04:16:33PM +0100, Ken Moffat via blfs-dev wrote:
> >
> > > In theory plugins should hav
On Sun, Mar 28, 2021 at 04:16:33PM +0100, Ken Moffat via blfs-dev wrote:
> In theory plugins should have been working for years, and nothing in
> that area has changed, but exceot for icewm I don't use lto because
> packages that should benefit from the longer build (mozilla
> p
On Sun, Mar 28, 2021 at 11:33:45AM +0200, Pierre Labastie via blfs-dev wrote:
> On Sun, 2021-03-28 at 00:31 +0000, Ken Moffat via blfs-dev wrote:
> > On Sun, Mar 28, 2021 at 12:16:18AM +0000, Ken Moffat wrote:
> > > Trying to bring up a new system (packages current as of a day
On Sun, Mar 28, 2021 at 12:16:18AM +, Ken Moffat wrote:
> Trying to bring up a new system (packages current as of a day
> ago), I got as far as icewm.
>
> My previous build used icewm-2.1.2, this attempt was using 2.2.1.
> I also note that cmake is now 3.20.0, and that
Trying to bring up a new system (packages current as of a day ago),
I got as far as icewm.
My previous build used icewm-2.1.2, this attempt was using 2.2.1.
I also note that cmake is now 3.20.0, and that I was initially
adding more options:
-DCONFIG_LIBRSVG=on \
The link in the book gives a 404.
If I go to https://github.com/rhboot/efibootmgr/releases I can
use firefox to download 17 as efibootmgr-17.tar.gz from
https://github.com/rhboot/efibootmgr/archive/refs/tags/17.tar.gz,
but if I use wget for that the tarball is downloaded as 17.tar.gz.
At various
On Sat, Mar 20, 2021 at 06:35:12PM -0500, Marty Jack via blfs-dev wrote:
>
>
> On Sat, 20 Mar 2021 18:11:58 -0500 Ken Moffat via blfs-dev wrote:
> > I'm getting ready for next week's release of firefox-78.9.0 by
> > measuring the build using the current candi
I'm getting ready for next week's release of firefox-78.9.0 by
measuring the build using the current candidate. Looking at our
instructions, since 'time immemorial' (ok, more exactly for 3 years,
but in our terms that is eons ago) we've had:
mkdir -pv /usr/lib/mozilla/plugins
On Sun, Mar 14, 2021 at 10:03:10PM +, Ken Moffat via blfs-dev wrote:
> On Sun, Mar 14, 2021 at 07:25:36PM +0000, Ken Moffat via blfs-dev wrote:
> >
> > Currently running a manual build to make sure it does now complete,
> > and hoping that I'm not again fille
On Sun, Mar 14, 2021 at 07:25:36PM +, Ken Moffat via blfs-dev wrote:
>
> Currently running a manual build to make sure it does now complete,
> and hoping that I'm not again filled with false optimism.
>
Turns out I *was* filled with false optimism, failed (as before)-
On Wed, Mar 10, 2021 at 03:09:30AM +, Ken Moffat via blfs-dev wrote:
> On Tue, Mar 09, 2021 at 09:58:23PM +0000, Ken Moffat via blfs-dev wrote:
> > On Tue, Mar 09, 2021 at 04:50:34PM +0000, Ken Moffat via blfs-dev wrote:
> > > On Tue, Mar 09, 2021 at 12:25:51AM -0500, Marty
On Tue, Mar 09, 2021 at 09:58:23PM +, Ken Moffat via blfs-dev wrote:
> On Tue, Mar 09, 2021 at 04:50:34PM +0000, Ken Moffat via blfs-dev wrote:
> > On Tue, Mar 09, 2021 at 12:25:51AM -0500, Marty Jack via blfs-dev wrote:
> > >
> > >
> > > On Mon, 08 Ma
On Tue, Mar 09, 2021 at 04:50:34PM +, Ken Moffat via blfs-dev wrote:
> On Tue, Mar 09, 2021 at 12:25:51AM -0500, Marty Jack via blfs-dev wrote:
> >
> >
> > On Mon, 08 Mar 2021 22:16:51 -0500 Ken Moffat via blfs-dev wrote:
> > >
> > > Output for
On Tue, Mar 09, 2021 at 12:25:51AM -0500, Marty Jack via blfs-dev wrote:
>
>
> On Mon, 08 Mar 2021 22:16:51 -0500 Ken Moffat via blfs-dev wrote:
> >
> > Output for the failing target follows (some lines are very long),
> > any clues, please ?
> >
> > TIA.
People who read -book will have seen that I'm trying to build the
git version of qtwebengine, because the non-commercial release of
5.15.3 is probably a month or more away but webengine has the usaul
crop of backported chromium fixes.
When I started, my build failed fairly quickly and I suspected
On Sun, Feb 14, 2021 at 02:07:57AM +, Ken Moffat via blfs-support wrote:
[ originally to -support, now copying -dev, looks like glibc-2.33
with qtwebengine is the problem ]
> This has got me flummoxed.
>
> I use falkon as my secondary browser for (amongst other things)
> lwn.n
The new pages for Security Advisories are now live.
To see the BLFS advisories, go to
http://www.linuxfromscratch.org/blfs/read.html and follow the links
in the Current Stable paragraphs (svn, systemd).
For editors, the advisories are common to svn and systemd and are in
the www repo, at
On Sun, Jan 31, 2021 at 09:16:36PM +, Ken Moffat via blfs-dev wrote:
> On Sun, Jan 31, 2021 at 09:07:34PM +0000, Ken Moffat via blfs-dev wrote:
> > On Sun, Jan 31, 2021 at 10:39:05AM -0600, Bruce Dubbs via blfs-dev wrote:
> > > On 1/31/21 7:57 AM, Ken Moffat
On Sun, Jan 31, 2021 at 09:07:34PM +, Ken Moffat via blfs-dev wrote:
> On Sun, Jan 31, 2021 at 10:39:05AM -0600, Bruce Dubbs via blfs-dev wrote:
> > On 1/31/21 7:57 AM, Ken Moffat via blfs-dev wrote:
> >
>
> Perhaps add Date: Severity: Critical/High/Unce
On Sun, Jan 31, 2021 at 10:39:05AM -0600, Bruce Dubbs via blfs-dev wrote:
> On 1/31/21 7:57 AM, Ken Moffat via blfs-dev wrote:
>
> > Current links:
>
> > 2. The revised details for 10.0 are at
> > http://www.linuxfromscratch.org/blfs/advisories/10.0.html with short
On Sun, Jan 31, 2021 at 01:57:35PM +, Ken Moffat via blfs-dev wrote:
> REvised links at end of this post.
>
Sorry, duplicate post.
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
REvised links at end of this post.
On Sun, Jan 31, 2021 at 03:16:53AM +, Ken Moffat via blfs-dev wrote:
> On Sun, Jan 31, 2021 at 09:55:10AM +0800, Kevin Buckley via blfs-dev wrote:
> > On Fri, 29 Jan 2021 at 11:37, Ken Moffat via blfs-dev
> > wrote:
> > >
> >
On Sun, Jan 31, 2021 at 09:55:10AM +0800, Kevin Buckley via blfs-dev wrote:
> On Fri, 29 Jan 2021 at 11:37, Ken Moffat via blfs-dev
> wrote:
> >
> > I'm thinking the format will be something like the following (not
> > necessarily what I originally suggested).
>
A few days ago I read in a link somewhere that perl.com had been
stolen and appeared to be parked for sale, as squatters do. This
sounded merely annoying, and I can't find the original link.
Today I looked at the latest URI release and saw that it changed
perl.com to example.com in tests and
On Sat, Jan 30, 2021 at 02:18:19AM +, Ken Moffat via blfs-dev wrote:
> On Fri, Jan 29, 2021 at 07:14:37PM +0000, Ken Moffat via blfs-dev
> wrote:
>
> So at last it is up for review at
> http://www.linuxfromscratch.org/blfs/advisories/ - unfortunately, I
> thought I'd fixed
On Fri, Jan 29, 2021 at 07:14:37PM +, Ken Moffat via blfs-dev
wrote:
>
> I've minimally started to hack on a page covering the 60+ items
> since 10.0 was released (14 in January up to last night by my
> current counting) to see how it looks. Still feeling my way.
> What I can'
On Fri, Jan 29, 2021 at 10:59:19AM -0600, Douglas R. Reno via blfs-dev wrote:
>
> On 1/28/21 9:37 PM, Ken Moffat via blfs-dev wrote:
> > A little while ago I proposed separating out our Security
> > Advisories. What I would now like to do is create an *extra* page
> >
A little while ago I proposed separating out our Security
Advisories. What I would now like to do is create an *extra* page
in the www/ repo listing (and in a couple of mutt cases creating[1])
advisories from 1st September when BLFS-10.0 was released.
For changes to the books I would create a
When firefox started to require the use of mach to build it, the
help it provided when failing to use the old comands said to run
'mach build', so I've been using that. This week, when looking at
thunderbird in AUR I noticed that now uses './mach configure'
followed by './mach build'.
The
On Tue, Jan 12, 2021 at 09:11:47AM +0100, Pierre Labastie via blfs-dev wrote:
> On Tue, 2021-01-12 at 08:50 +0100, Tim Tassonis via blfs-dev wrote:
> > Hi all
> >
> > Since a couple of days, I'm experiencing connect issues to
> > wiki.linuxfromscratch.org. Is this a known issue, or is the
We are getting better at noticing packages which have been updated
for vulnerabilities, but I find out current layout (Security
Vulnerabilities listed under Errata for our latest release) awkward:
as I understand it, we add to the end of the list unless there is an
earlier update for this package
On Wed, Jan 06, 2021 at 05:56:51PM +0100, Tim Tassonis via blfs-dev wrote:
>
>
> On 1/6/21 5:38 PM, Bruce Dubbs via blfs-dev wrote:
> > On 1/6/21 10:27 AM, Tim Tassonis via blfs-dev wrote:
> > >
> > >
> > > On 1/6/21 5:14 PM, Bruce Dubbs via blfs-dev wrote:
> > > > On 1/6/21 9:58 AM, Tim
On Tue, Jan 05, 2021 at 10:20:51PM +, Ken Moffat via blfs-dev wrote:
> On Tue, Jan 05, 2021 at 07:50:14PM +0000, Ken Moffat via blfs-dev wrote:
> > On Tue, Jan 05, 2021 at 11:33:30AM -0600, Bruce Dubbs via blfs-dev wrote:
> > > On 1/5/21 9:34 AM, Ken Moffat via blfs-dev wro
On Tue, Jan 05, 2021 at 05:29:53PM -0600, Douglas R. Reno via blfs-dev wrote:
>
> On 1/5/21 4:20 PM, Ken Moffat via blfs-dev wrote:
> > On Tue, Jan 05, 2021 at 07:50:14PM +, Ken Moffat via blfs-dev wrote:
> > > On Tue, Jan 05, 2021 at 11:33:30AM -0600, Bruce Dub
On Tue, Jan 05, 2021 at 07:50:14PM +, Ken Moffat via blfs-dev wrote:
> On Tue, Jan 05, 2021 at 11:33:30AM -0600, Bruce Dubbs via blfs-dev wrote:
> > On 1/5/21 9:34 AM, Ken Moffat via blfs-dev wrote:
> > > On Tue, Jan 05, 2021 at 02:33:35PM +0100, Pierre Labastie via blf
On Tue, Jan 05, 2021 at 11:33:30AM -0600, Bruce Dubbs via blfs-dev wrote:
> On 1/5/21 9:34 AM, Ken Moffat via blfs-dev wrote:
> > On Tue, Jan 05, 2021 at 02:33:35PM +0100, Pierre Labastie via blfs-dev
> > wrote:
> > > On Wed, 2020-12-30 at 18:21 +, Ken Moffat via bl
On Tue, Jan 05, 2021 at 02:33:35PM +0100, Pierre Labastie via blfs-dev wrote:
> On Wed, 2020-12-30 at 18:21 +0000, Ken Moffat via blfs-dev wrote:
> > Hi Guys,
> >
> > some of you may have noticed that I have an aversion to gtk-doc (I'm
> > getting over it). This was t
On Sat, Jan 02, 2021 at 07:57:01PM +0800, Kevin Buckley via blfs-dev wrote:
> Been working against the BLFS Version 2020-09-03, so Pango 1.46.0
> but BLFS Version 2021-01-01 with Pango 1.48.0 has the same text.
>
> I read,
>
> Pango Dependencies
>
> Required
>
> Fontconfig-2.13.1 (must be
I've got as far as checking cogl in the packages needing autoreconf
(might as well do them all whilst on a system where gtkdocize is
made unavailable) - not surprisingly, gtkdocize gets needed more in
gnome packages.
Among these is cogl, but in this case autoreconf is a legacy from
when we used
On Wed, Dec 30, 2020 at 03:46:58PM -0600, Bruce Dubbs via blfs-dev wrote:
> On 12/30/20 1:18 PM, Pierre Labastie via blfs-dev wrote:
>
> > I think you can start gnome without a dm, by putting "exec gnome-
> > session" in .xinitrc. Now how to only start gnome-shell, I am not sure.
>
> This is
On Wed, Dec 30, 2020 at 08:18:16PM +0100, Pierre Labastie via blfs-dev wrote:
> On Wed, 2020-12-30 at 18:21 +0000, Ken Moffat via blfs-dev wrote:
> > Hi Guys,
> >
> > some of you may have noticed that I have an aversion to gtk-doc (I'm
> > getting over it). This was t
Hi Guys,
some of you may have noticed that I have an aversion to gtk-doc (I'm
getting over it). This was triggered by occasional uses of
autoreconf now needing gtkdocize. That first hit me in polkit with
the patch for elogind, but my memory suggested that the patch has in
the past been added or
On Mon, Dec 28, 2020 at 09:33:22PM -0600, Bruce Dubbs via blfs-dev
wrote:
> On 12/28/20 9:04 PM, Ken Moffat via blfs-dev wrote:
> > First, comment on gtkmm3 - the book does not have '..' in the
> > meson command. Seems unusual, Im using e conventional '..'.
> >
> &
First, comment on gtkmm3 - the book does not have '..' in the meson
command. Seems unusual, Im using e conventional '..'.
Second, a question: why are the docs for this package so important ?
The book passes -Dbuild-documentation=true and later installs the
docs. But that requires doxygen which
On Sun, Dec 27, 2020 at 07:05:29AM -0600, Bruce Dubbs via blfs-dev wrote:
> On 12/26/20 11:30 PM, Ken Moffat via blfs-dev wrote:
> > Using polkit-0.118 and our
> > polkit-0.118-fix_elogind_detection-1.patch, autoreconf fails with
> > current versions of everything.
&
Using polkit-0.118 and our
polkit-0.118-fix_elogind_detection-1.patch, autoreconf fails with
current versions of everything. In my script I use autoreconf -fiv
instead of just autoreconf -fi, so this maybe shows a little more
detail than the book's version:
(the first part looks ok)
autoreconf:
On Fri, Dec 25, 2020 at 05:05:43PM +0100, Tim Tassonis via blfs-dev wrote:
>
>
> On 12/25/20 4:04 AM, Ken Moffat via blfs-dev wrote:
> > On Thu, Dec 24, 2020 at 11:56:59PM +0100, Tim Tassonis via blfs-dev wrote:
> > > Hi all
> > >
> > > As a new
On Thu, Dec 24, 2020 at 11:56:59PM +0100, Tim Tassonis via blfs-dev wrote:
> Hi all
>
> As a new release of my favorite DE is out and it's christmas, I thought I
> give it a go.
>
> In short: An upgrade from 4.14 as in blfs svn works seamlessly, in the exact
> order as already in the book.
>
>
On Sat, Dec 12, 2020 at 10:07:29AM +0100, Pierre Labastie via blfs-dev wrote:
> Presently, in the book, we have two pages for the Qt library: one for
> full Qt, except we do not build qtwebengine, and another one for
> qtwebengine. This has a couple of drawbacks:
> - If a package needs only Qt
On Fri, Dec 11, 2020 at 12:39:36PM -0600, Bruce Dubbs via blfs-dev wrote:
> On 12/11/20 12:04 PM, Ken Moffat via blfs-dev wrote:
> >
> > More generally, our releases are frozen at a point in time, and
> > subject to errata. If a url becomes unusable, do we not fix that
&
On Fri, Dec 11, 2020 at 11:03:05AM -0600, Bruce Dubbs via blfs-dev wrote:
> On 12/11/20 12:40 AM, Pierre Labastie via blfs-dev wrote:
> > On Fri, 2020-12-11 at 02:43 +0000, Ken Moffat via blfs-dev wrote:
> >
> > Yes I've been bitten by that when trying to build LXQt. Note th
I must have been evil in a previous existence, because I'm not
trying to use jhalfs to build kde.
In kf5 I stopped the build after a bit over an hour because nothing
was happening. The log said:
URL transformed to HTTPS due to an HSTS policy
--2020-12-11 02:14:37--
For those who don't read -support:
I've just hit a problem, initially reported earlier this month by
Christopher Gregory, where libsoup built with meson-0.56.0 fails to
link to static sysprof. That was supposedly fixed in meson by
https://github.com/mesonbuild/meson/pull/7930 but rebuilding
On Tue, Nov 10, 2020 at 05:43:00PM +, Ken Moffat via blfs-dev wrote:
> On Tue, Nov 10, 2020 at 10:43:49AM -0600, Bruce Dubbs via blfs-dev wrote:
> > On 11/10/20 6:43 AM, Tim Tassonis via blfs-dev wrote:
>
> Not directly related to this, but I've had various problems trying
>
On Tue, Nov 10, 2020 at 10:43:49AM -0600, Bruce Dubbs via blfs-dev wrote:
> On 11/10/20 6:43 AM, Tim Tassonis via blfs-dev wrote:
> > Hi all
> >
> > I'm just about to build llvm 11 as in current blfs, and wondered if it
> > would be better to install it in /opt/llvm11, instead of /usr.
> >
> >
On Wed, Oct 21, 2020 at 10:48:39PM -0500, Bruce Dubbs via blfs-dev wrote:
>
> In LFS, we can make the symlink to p3. For p2 in BLFS, we will use 'make
> altinstall'. Everything else would be for non-python packages that either
> use p2 or create a p2 module.
>
I've now completed my build
On Fri, Oct 30, 2020 at 07:10:40PM -0500, Marty Jack via blfs-dev wrote:
>
>
> The fix is simple: replace TRUE by true and FALSE by false wherever it is
> needed.
> The requirement is pervasive. I have 3 packages that needed changes. The
> qtwebengine touches a lot of files.
> The one I had
On Sat, Oct 31, 2020 at 12:47:54AM +, Ken Moffat via blfs-dev wrote:
> On Fri, Oct 30, 2020 at 06:56:19PM -0500, Douglas R. Reno via blfs-dev wrote:
> >
> > On 10/30/20 6:15 PM, Ken Moffat via blfs-dev wrote:
> > >
> > > This comes from encoding.c
>
On Fri, Oct 30, 2020 at 07:10:40PM -0500, Marty Jack via blfs-dev wrote:
>
>
> The fix is simple: replace TRUE by true and FALSE by false wherever it is
> needed.
> The requirement is pervasive. I have 3 packages that needed changes. The
> qtwebengine touches a lot of files.
> The one I had
On Fri, Oct 30, 2020 at 06:56:19PM -0500, Douglas R. Reno via blfs-dev wrote:
>
> On 10/30/20 6:15 PM, Ken Moffat via blfs-dev wrote:
> > I see we've already had one set of fixes for changes in icu68, I
> > hope it is not going to trash a lot of things.
> >
> &
I see we've already had one set of fixes for changes in icu68, I
hope it is not going to trash a lot of things.
I've been building libxml2 --with-icu for some time, that breaks:
/bin/sh ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
-I./include -I./include -pedantic -Wall
On Wed, Oct 28, 2020 at 06:21:11PM -0500, Marty Jack via blfs-dev wrote:
>
>
> On Wed, 28 Oct 2020 16:02:02 -0500 Ken Moffat via blfs-dev wrote:
> > On Wed, Oct 28, 2020 at 02:36:06AM -0500, Marty Jack via blfs-dev wrote:
> > >
> > >
> > > On Tue, 27 O
On Wed, Oct 28, 2020 at 02:36:06AM -0500, Marty Jack via blfs-dev wrote:
>
>
> On Tue, 27 Oct 2020 17:00:15 -0500 Ken Moffat via blfs-dev wrote:
> > (Cc: to support if I remember, in case anyone else hits this)
> >
> > Starting to upgrade my systems for whatever has c
(Cc: to support if I remember, in case anyone else hits this)
Starting to upgrade my systems for whatever has caused today's
gstreamer releases. Most are still running 9.1 with 1.16.2.
Normally I build gstreamer well before qt, but trying to upgrade has
changed that.
In gst-plugins-base it
On Fri, Oct 23, 2020 at 04:15:09PM +0100, Ken Moffat via blfs-dev wrote:
> On Fri, Oct 23, 2020 at 09:04:53AM +0200, Pierre Labastie via blfs-dev wrote:
> >
> > When we find something like that, couldn't we use:
> > grep -rl '#!.*python' | xargs sed -i
> > '1{s/p
On Fri, Oct 23, 2020 at 11:22:06AM -0500, Bruce Dubbs via blfs-dev wrote:
> > Is there an official python recommendation for that, to quote at
> > them, please ?
>
> That's a good question, but I would also like to see if there is a survey of
> the major distros on the subject. I know arch has
On Fri, Oct 23, 2020 at 09:04:53AM +0200, Pierre Labastie via blfs-dev wrote:
> > Reluctantly, I have to go with a python symlink. Out of the more
> > than 48000 tests in clang-11.0, one uses /usr/bin/env/python.
> >
>
> When we find something like that, couldn't we use:
> grep -rl '#!.*python'
On Fri, Oct 23, 2020 at 10:27:51AM -0500, DJ Lucas via blfs-dev wrote:
> On October 23, 2020 10:15:09 AM CDT, Ken Moffat via blfs-dev
> wrote:
> >On Fri, Oct 23, 2020 at 09:04:53AM +0200, Pierre Labastie via blfs-dev
> >wrote:
> >> > Reluctantly, I have to
On Fri, Oct 23, 2020 at 09:04:53AM +0200, Pierre Labastie via blfs-dev wrote:
> On Fri, 2020-10-23 at 07:00 +0100, Ken Moffat via blfs-dev wrote:
> > On Thu, Oct 22, 2020 at 04:44:19PM +0100, Ken Moffat via blfs-dev
> > wrote:
> > > On Thu, Oct 22, 2020 at 11:24:52PM +0800
On Thu, Oct 22, 2020 at 04:44:19PM +0100, Ken Moffat via blfs-dev wrote:
> On Thu, Oct 22, 2020 at 11:24:52PM +0800, Xi Ruoyao via blfs-dev wrote:
> > On 2020-10-22 16:14 +0100, Ken Moffat via blfs-dev wrote:
> > > On Thu, Oct 22, 2020 at 06:25:59AM -0500, Bruce Dubbs
On Thu, Oct 22, 2020 at 03:32:07PM -0500, Douglas R. Reno via blfs-dev wrote:
>
> On 10/22/20 3:23 PM, Ken Moffat via blfs-dev wrote:
> > I saw that sysprof was now recommended for libsoup, and I thought
> > I'd seen a post about that, but I can't spot it in my mail or by
>
Sorry, posted to lfs-dev, lemme try again.
- Forwarded message from Ken Moffat via lfs-dev
-
Date: Thu, 22 Oct 2020 21:01:16 +0100
From: Ken Moffat via lfs-dev
To: lfs-...@lists.linuxfromscratch.org
Cc: Ken Moffat
Subject: [lfs-dev] Problems with scour
Reply-To: LFS Developers
I saw that sysprof was now recommended for libsoup, and I thought
I'd seen a post about that, but I can't spot it in my mail or by
searching on google ?
Anyway,for the current build I went along with the recommendation
and added it, plus libdazzle. But building libsoup did not go
smoothly:
On Thu, Oct 22, 2020 at 11:24:52PM +0800, Xi Ruoyao via blfs-dev wrote:
> On 2020-10-22 16:14 +0100, Ken Moffat via blfs-dev wrote:
> > On Thu, Oct 22, 2020 at 06:25:59AM -0500, Bruce Dubbs via blfs-dev wrote:
> > > On 10/22/20 12:56 AM, DJ Lucas via blfs-dev wrote:
> > &g
On Thu, Oct 22, 2020 at 02:46:43PM +0200, Pierre Labastie via blfs-dev wrote:
> Actually, apart from cairomm, the C++ GTK stack has not been updated,
> so gtkmm3 and pangomm require cairomm-1.0 (whose last release is
> cairomm-1.14).
>
> I got an error while building gnome-system-monitor because
On Thu, Oct 22, 2020 at 06:25:59AM -0500, Bruce Dubbs via blfs-dev wrote:
> On 10/22/20 12:56 AM, DJ Lucas via blfs-dev wrote:
> > On October 21, 2020 10:48:39 PM CDT, Bruce Dubbs via blfs-dev
> > wrote:
> > > On 10/21/20 10:06 PM, DJ Lucas via blfs-dev wrote:
> > > >
> >
> > >
> > > In LFS,
On Wed, Oct 21, 2020 at 10:06:45PM -0500, DJ Lucas via blfs-dev wrote:
> >
> > As to the convenience link in /usr/bin, I'd look to remove it and tell
> > people that they can alias the bare "python" if they really, really need
> > to, but that they have to make the choice to do so: the system
On Thu, Oct 22, 2020 at 08:12:18AM +0800, Kevin Buckley via blfs-dev wrote:
> On Thu, 22 Oct 2020 at 00:26, Bruce Dubbs via blfs-dev
> wrote:
> >
> > Currently we have /usr/bin/python -> python2. Is it time to change that
> > to python3?
>
> Probably a bit too drastic a view, but should we even
On Wed, Oct 21, 2020 at 12:53:27PM -0500, Bruce Dubbs via blfs-dev wrote:
> On 10/21/20 12:06 PM, DJ Lucas via blfs-dev wrote:
> > On October 21, 2020 11:25:42 AM CDT, Bruce Dubbs via blfs-dev
> > wrote:
> > > Currently we have /usr/bin/python -> python2. Is it time to change
> > > that
> > >
On Thu, Oct 15, 2020 at 05:03:54PM -0500, Bruce Dubbs via blfs-dev wrote:
> On 10/15/20 4:51 PM, Ken Moffat via blfs-dev wrote:
> > On Wed, Oct 14, 2020 at 03:59:32PM +0100, Ken Moffat via blfs-dev wrote:
> > > On Wed, Oct 14, 2020 at 02:14:56PM +0100, Ken Moffat via blfs-dev wro
On Wed, Oct 14, 2020 at 03:59:32PM +0100, Ken Moffat via blfs-dev wrote:
> On Wed, Oct 14, 2020 at 02:14:56PM +0100, Ken Moffat via blfs-dev wrote:
> > On Wed, Oct 14, 2020 at 04:17:50PM +0800, Xi Ruoyao via blfs-dev wrote:
> > > On 2020-10-14 02:45 +0100, Ken Moffat
On Wed, Oct 14, 2020 at 10:21:13PM +0200, Pierre Labastie via blfs-dev wrote:
> On Wed, 2020-10-14 at 11:52 -0500, Bruce Dubbs via blfs-dev wrote:
> > On 10/14/20 11:43 AM, Ken Moffat via blfs-dev wrote:
> > > On Tue, Oct 13, 2020 at 11:11:13AM -0500, Bruce Dubbs via bl
On Tue, Oct 13, 2020 at 11:11:13AM -0500, Bruce Dubbs via blfs-dev wrote:
> On 10/12/20 10:15 PM, Ken Moffat via blfs-dev wrote:
> > On Mon, Oct 12, 2020 at 09:41:37PM -0500, Bruce Dubbs via blfs-dev
> > wrote:
>
> They seem to be using system JBIG2DEC, JPEGXR, and GUMBO w
On Wed, Oct 14, 2020 at 02:14:56PM +0100, Ken Moffat via blfs-dev wrote:
> On Wed, Oct 14, 2020 at 04:17:50PM +0800, Xi Ruoyao via blfs-dev wrote:
> > On 2020-10-14 02:45 +0100, Ken Moffat via blfs-dev wrote:
> > > On Wed, Oct 14, 2020 at 02:21:39AM +0100, Ken Moffat
On Wed, Oct 14, 2020 at 04:17:50PM +0800, Xi Ruoyao via blfs-dev wrote:
> On 2020-10-14 02:45 +0100, Ken Moffat via blfs-dev wrote:
> > On Wed, Oct 14, 2020 at 02:21:39AM +0100, Ken Moffat via blfs-dev wrote:
> > > On Mon, Oct 12, 2020 at 09:15:30PM +0100, Ken Moffat
On Wed, Oct 14, 2020 at 02:21:39AM +0100, Ken Moffat via blfs-dev wrote:
> On Mon, Oct 12, 2020 at 09:15:30PM +0100, Ken Moffat via blfs-dev wrote:
> > People might remember that I looked at llvm-11-rc1 in early August,
> > and discovered that rustc-1.42.0 could not use it. I se
On Mon, Oct 12, 2020 at 09:15:30PM +0100, Ken Moffat via blfs-dev wrote:
> People might remember that I looked at llvm-11-rc1 in early August,
> and discovered that rustc-1.42.0 could not use it. I see that
> llvm-11.0.0 is now out, and the release notes for rust-1.47.0 say
> t
On Mon, Oct 12, 2020 at 09:41:37PM -0500, Bruce Dubbs via blfs-dev
wrote:
> I have been struggling today to get a satisfactory build of
> mupdf-1.18.0. I can get it to build, but it also builds its own
> copies of curl, freeglut, freetype, harfbuzz, lcms2, ligjpeg,
> openjpeg, and zlib and links
People might remember that I looked at llvm-11-rc1 in early August,
and discovered that rustc-1.42.0 could not use it. I see that
llvm-11.0.0 is now out, and the release notes for rust-1.47.0 say
that it ships with llvm-11 (although it 'should' build with older
llvm).
I've just started a fresh
On Wed, Oct 07, 2020 at 11:17:49AM -0500, Bruce Dubbs via blfs-dev wrote:
> On 10/7/20 10:38 AM, Douglas R. Reno via blfs-dev wrote:
> >
> > On 10/7/20 2:38 AM, Pierre Labastie via blfs-dev wrote:
> > > Usually, the first thing I do after building a new lfs VM, and the
> > > necessary tools to
On Tue, Sep 22, 2020 at 01:48:27AM +0800, Xi Ruoyao via blfs-dev wrote:
> On 2020-09-21 17:59 +0100, Ken Moffat via blfs-dev wrote:
> > On Mon, Sep 21, 2020 at 10:07:18AM -0500, Douglas R. Reno via blfs-dev
> > wrote:
> > >
> > > On 9/21/20 9:36 AM, Ken Moffat vi
On Mon, Sep 21, 2020 at 10:07:18AM -0500, Douglas R. Reno via blfs-dev wrote:
>
> On 9/21/20 9:36 AM, Ken Moffat via blfs-dev wrote:
> > I'm now looking at js78 because firefox-78.3.0 is out. For the
> > moment I'm still using js68, but I can at least compare the js build
I'm now looking at js78 because firefox-78.3.0 is out. For the
moment I'm still using js68, but I can at least compare the js build
against 78.2.0.
Looking at that, we have '--disable-jemalloc' with the explanation:
This switch disables the internal memory allocator used in JS78.
jemalloc causes
1 - 100 of 1697 matches
Mail list logo
