On 31/03/2019 01:42, Brendan L via blfs-dev wrote:
> On Sat, Mar 30, 2019 at 1:27 PM Ken Moffat via blfs-dev
> wrote:
>>
>> After the discussions on meson, and cmake, I've made an attempt to
>> add details to the book. It's a bit longer than I had expected
>> (heh, I never use ywo words where fiv
On Sun, Mar 31, 2019 at 1:32 PM Ken Moffat via blfs-dev
wrote:
>
> On Sat, Mar 30, 2019 at 07:42:58PM -0500, Brendan L via blfs-dev wrote:
> > On Sat, Mar 30, 2019 at 1:27 PM Ken Moffat via blfs-dev
> > wrote:
> > >
> > > After the discussions on meson, and cmake, I've made an attempt to
> > > ad
On Sat, Mar 30, 2019 at 07:42:58PM -0500, Brendan L via blfs-dev wrote:
> On Sat, Mar 30, 2019 at 1:27 PM Ken Moffat via blfs-dev
> wrote:
> >
> > After the discussions on meson, and cmake, I've made an attempt to
> > add details to the book. It's a bit longer than I had expected
> > (heh, I neve
On Sat, Mar 30, 2019 at 1:27 PM Ken Moffat via blfs-dev
wrote:
>
> After the discussions on meson, and cmake, I've made an attempt to
> add details to the book. It's a bit longer than I had expected
> (heh, I never use ywo words where five will do ;) and I'm not sure
> if everyone will understand
On Sat, Mar 30, 2019 at 03:49:43PM -0500, Bruce Dubbs via blfs-dev wrote:
>
> I like it but I would make some minor changes. Rather than listing them,
> why don't you just commit what you have and we can collectively edit from
> there.
>
Commited at r21415.
ĸen
--
It is said that there are t
On 3/30/19 1:25 PM, Ken Moffat via blfs-dev wrote:
After the discussions on meson, and cmake, I've made an attempt to
add details to the book. It's a bit longer than I had expected
(heh, I never use ywo words where five will do ;) and I'm not sure
if everyone will understand things which seem ob
After the discussions on meson, and cmake, I've made an attempt to
add details to the book. It's a bit longer than I had expected
(heh, I never use ywo words where five will do ;) and I'm not sure
if everyone will understand things which seem obvious to me, so I've
uploaded it for comment.
A full
On 28/03/2019 16:25, Douglas R. Reno via blfs-dev wrote:
On 3/28/19 2:28 AM, Pierre Labastie via blfs-dev wrote:
On 28/03/2019 03:59, Bruce Dubbs via blfs-dev wrote:
There are just too many problems with meson-0.50.0. Therefore I
have reverted
to meson-0.49.2 in lfs-svn until it gets fixed.
On 2019-03-28 10:25 -0500, Douglas R. Reno via blfs-dev wrote:
> I stand by my opinion that this version of Meson should've been
> Meson-1.0.0...
I think they should actually rename 0.49.0 to 49.0.0, 0.50.0 to 50.0.0, etc.
It seems I could build gnome just because of my blind luck (using a custo
On 3/28/19 2:28 AM, Pierre Labastie via blfs-dev wrote:
On 28/03/2019 03:59, Bruce Dubbs via blfs-dev wrote:
There are just too many problems with meson-0.50.0. Therefore I have reverted
to meson-0.49.2 in lfs-svn until it gets fixed.
If this is a conclusion of private discussions, please ma
On 28/03/2019 03:59, Bruce Dubbs via blfs-dev wrote:
> There are just too many problems with meson-0.50.0. Therefore I have reverted
> to meson-0.49.2 in lfs-svn until it gets fixed.
>
If this is a conclusion of private discussions, please make them public, or
summarize them... If it is not, wel
On Wed, Mar 27, 2019 at 09:59:38PM -0500, Bruce Dubbs via blfs-dev wrote:
> There are just too many problems with meson-0.50.0. Therefore I have
> reverted to meson-0.49.2 in lfs-svn until it gets fixed.
>
> -- Bruce
>
LOL. My experience of looking at the detail on a *few* packages is
that it
There are just too many problems with meson-0.50.0. Therefore I have
reverted to meson-0.49.2 in lfs-svn until it gets fixed.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
On Wed, Mar 27, 2019 at 10:13:07AM +0100, Pierre Labastie via blfs-dev wrote:
>
> Note that for mesa -Db_ndebug=true can be used to disable assertions (the
> default is "if_release"). Then "-O2 -g" is still passed. You can also pass
> -Db_nebug=false with -Dbuildtype=release, of course...
To try
On Tue, Mar 26, 2019 at 10:15:50PM -0500, Bruce Dubbs via blfs-dev wrote:
>
> Are there problems with mesa without us changing the optimization?
>
In games, if not using a release build, loading levels can take
inordinate amounts of time (see the bug report). Specifying a
release build defaults
On 2019-03-27 10:51 -0500, Bruce Dubbs via blfs-dev wrote:
> On 3/27/19 4:13 AM, Pierre Labastie via blfs-dev wrote:
>
> > Note that for mesa -Db_ndebug=true can be used to disable assertions (the
> > default is "if_release"). Then "-O2 -g" is still passed. You can also pass
> > -Db_nebug=false wi
On 3/27/19 4:13 AM, Pierre Labastie via blfs-dev wrote:
Note that for mesa -Db_ndebug=true can be used to disable assertions (the
default is "if_release"). Then "-O2 -g" is still passed. You can also pass
-Db_nebug=false with -Dbuildtype=release, of course...
BTW, using gdb with "-O2 -g" does n
On 26/03/2019 20:35, Ken Moffat via blfs-dev wrote:
> I originally posted most of this to lfs-dev, thinking that since
> meson was in LFS there must be something there which used it. But
> AFAICS everything which uses meson is in BLFS, so moving this to
> here, with some updated details.
>
> I wa
On 3/26/19 8:57 PM, Ken Moffat via blfs-dev wrote:
On Tue, Mar 26, 2019 at 07:39:46PM -0500, Bruce Dubbs via blfs-dev wrote:
On 3/26/19 5:25 PM, Ken Moffat via blfs-dev wrote:
I have little experience using gdb, I'm
not entirely convinced that trying to debug a -O3 build would ever
be useful
On 3/26/19 8:57 PM, Ken Moffat via blfs-dev wrote:
(sorry for any delay in responding, been emailing MPs about the
state this country is in).
I've been meaning to ask you about that. It seems that both our
countries are being run by idiots. I submit that our problem is worse,
but less im
On Tue, Mar 26, 2019 at 07:39:46PM -0500, Bruce Dubbs via blfs-dev wrote:
> On 3/26/19 5:25 PM, Ken Moffat via blfs-dev wrote:
> > On Tue, Mar 26, 2019 at 02:55:40PM -0500, Bruce Dubbs via blfs-dev wrote:
>
> > I suppose libdrm, gdk-pixbuf, glib2, pango might be interesting
> > packages to look at
On 3/26/19 5:25 PM, Ken Moffat via blfs-dev wrote:
On Tue, Mar 26, 2019 at 02:55:40PM -0500, Bruce Dubbs via blfs-dev wrote:
I suppose libdrm, gdk-pixbuf, glib2, pango might be interesting
packages to look at.
As an initial guess, I think I should compare (with 4 cores) :
· the book's curren
On Tue, Mar 26, 2019 at 02:55:40PM -0500, Bruce Dubbs via blfs-dev wrote:
> On 3/26/19 2:35 PM, Ken Moffat via blfs-dev wrote:
> >
> > https://bugs.freedesktop.org/show_bug.cgi?id=109939#c16
> >
> > From that, the default for *mesa* is 'debugoptimized' which seems to
> > be what we are using. I
On Tue, Mar 26, 2019, 2:05 PM Bruce Dubbs via blfs-dev <
blfs-dev@lists.linuxfromscratch.org> wrote:
> On 3/26/19 2:35 PM, Ken Moffat via blfs-dev wrote:
> > I originally posted most of this to lfs-dev, thinking that since
> > meson was in LFS there must be something there which used it. But
> >
On 3/26/19 2:35 PM, Ken Moffat via blfs-dev wrote:
I originally posted most of this to lfs-dev, thinking that since
meson was in LFS there must be something there which used it. But
AFAICS everything which uses meson is in BLFS, so moving this to
here, with some updated details.
I was galancing
I originally posted most of this to lfs-dev, thinking that since
meson was in LFS there must be something there which used it. But
AFAICS everything which uses meson is in BLFS, so moving this to
here, with some updated details.
I was galancing at phoronix this afternoon (often taken over by the
On Fri, Mar 22, 2019 at 12:35:22AM +, Ken Moffat via blfs-dev wrote:
> On Thu, Mar 21, 2019 at 06:09:19PM -0500, Douglas R. Reno via blfs-dev wrote:
> >
> > On 3/21/19 5:08 PM, Ken Moffat via blfs-dev wrote:
> > > My build of recent svn is progressing *slowly* and glib seems to
> > > have move
On Thu, Mar 21, 2019 at 06:09:19PM -0500, Douglas R. Reno via blfs-dev wrote:
>
> On 3/21/19 5:08 PM, Ken Moffat via blfs-dev wrote:
> > My build of recent svn is progressing *slowly* and glib seems to
> > have moved on to 2.60 since I started (or else I forgot to update
> > the version). But eit
Hi all,
On Thu, 21 Mar 2019, Ken Moffat via blfs-dev wrote:
My build of recent svn is progressing *slowly* and glib seems to
have moved on to 2.60 since I started (or else I forgot to update
the version). But either way, with meson-0.50.0 and glib-2.58.3 I'm
getting:
meson.build:1:0: ERROR: V
On 3/21/19 5:08 PM, Ken Moffat via blfs-dev wrote:
My build of recent svn is progressing *slowly* and glib seems to
have moved on to 2.60 since I started (or else I forgot to update
the version). But either way, with meson-0.50.0 and glib-2.58.3 I'm
getting:
meson.build:1:0: ERROR: Value disab
My build of recent svn is progressing *slowly* and glib seems to
have moved on to 2.60 since I started (or else I forgot to update
the version). But either way, with meson-0.50.0 and glib-2.58.3 I'm
getting:
meson.build:1:0: ERROR: Value disabled is not boolean (true or false).
Changing to -Desl
On Wed, Jan 23, 2019 at 3:16 PM Bruce Dubbs via blfs-dev
wrote:
>
>
> That's true, but our policy has always been to use the default
> optimization of the package. Most of the packages above are a part of
> gnome.
>
Well I've noticed the buildtype is set at configuration for a few
cmake packages
On 01/23/2019 02:16 PM, Pierre Labastie via blfs-dev wrote:
On 23/01/2019 20:48, Bruce Dubbs via blfs-dev wrote:
On 01/23/2019 01:33 PM, Brendan L via blfs-dev wrote:
I noticed some of the projects that switched to meson haven't set and
default buildtype, which means a debug build is produced.
On Wed, Jan 23, 2019 at 2:17 PM Pierre Labastie via blfs-dev
wrote:
>
> On 23/01/2019 20:48, Bruce Dubbs via blfs-dev wrote:
nautilus
> >
> > Actually, that is covered at
> > http://www.linuxfromscratch.org/blfs/view/stable/introduction/notes-on-building.html#stripping
> > where all packages can
On 23/01/2019 20:48, Bruce Dubbs via blfs-dev wrote:
> On 01/23/2019 01:33 PM, Brendan L via blfs-dev wrote:
>> I noticed some of the projects that switched to meson haven't set and
>> default buildtype, which means a debug build is produced. Most of the
>> gnome projects that switched set a defau
On 01/23/2019 01:33 PM, Brendan L via blfs-dev wrote:
I noticed some of the projects that switched to meson haven't set and
default buildtype, which means a debug build is produced. Most of the
gnome projects that switched set a default buildtype to debugoptimized
which is equivalent to -O2 -g (
I noticed some of the projects that switched to meson haven't set and
default buildtype, which means a debug build is produced. Most of the
gnome projects that switched set a default buildtype to debugoptimized
which is equivalent to -O2 -g (which autotools did). The book should
probably set debu
On 29/09/2017 22:17, Bruce Dubbs wrote:
I am looking at fuse-3.2.0. This package has dropped autotools in
favor of meson/ninja. We are still in a bit of a learning mode and I
am going to present what I've found asking for comment.
sed -i '/^udev/,$ s/^/#/' util/meson.build
meson --prefix=/u
I am looking at fuse-3.2.0. This package has dropped autotools in favor
of meson/ninja. We are still in a bit of a learning mode and I am going
to present what I've found asking for comment.
sed -i '/^udev/,$ s/^/#/' util/meson.build
meson --prefix=/usr $PWD build
cd build
ninja -j1
DESTDIR
NOTE: Please trim when replying.
It looks like we will be needing to add meson and ninja to lfs pretty
soon. The initial reason is that systemd will be going to a meson only
build but we do not have a time frame.
I also understand that a lot of gnome apps will be going to meson soon also.
40 matches
Mail list logo
