Re: [blfs-dev] RFC: remove '..' in our meson commands

2019-12-31 Thread Ken Moffat via blfs-dev
On Wed, Jan 01, 2020 at 03:20:33AM +0800, Xi Ruoyao via blfs-dev wrote:
> Hi:
> 
> Now most of our meson commands contains a '..' but a few does not.  Maybe we
> should remove all '..' in meson commands.  Reasons:
> 
> (1)  '..' is unnecessary in meson command, with "mkdir build; cd build".
> (2)  Sometimes we forgot to "mkdir build; cd build" and type the meson command
> in the source code directory, mistakenly.  With a '..' meson will believe '..'
> is the building directory and produce build.ninja and many other files in 
> '..'. 
> It's hard to clean them because BLFS source code directory (/usr/src or
> $HOME/src) contains lots of tarballs.  However, without '..' if we forgot to
> type "mkdir build; cd build" meson would complain and exit, instead of 
> producing
> the files.
> 
> Any thoughts?

While I'm still maybe sober - I've seen both.  The scattering of
files around .. is certainly painful to clear up, and the exit if
not in a build directory is useful.

But I see Bruce prefers to be explicit.  Dunno about that, in
./configure scripts we usually ignore options which are the defaults
(compare various builds in AUR and gentoo).

ĸen
-- 
And there's a hand, my trusty fiere!
and gie's a hand o' thine!
And we'll tak' a right gude-willie waught,
for auld lang syne.
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-dev] RFC: remove '..' in our meson commands

2019-12-31 Thread Bruce Dubbs via blfs-dev

On 12/31/19 1:20 PM, Xi Ruoyao via blfs-dev wrote:

Hi:

Now most of our meson commands contains a '..' but a few does not.  Maybe we
should remove all '..' in meson commands.  Reasons:

(1)  '..' is unnecessary in meson command, with "mkdir build; cd build".
(2)  Sometimes we forgot to "mkdir build; cd build" and type the meson command
in the source code directory, mistakenly.  With a '..' meson will believe '..'
is the building directory and produce build.ninja and many other files in '..'.
It's hard to clean them because BLFS source code directory (/usr/src or
$HOME/src) contains lots of tarballs.  However, without '..' if we forgot to
type "mkdir build; cd build" meson would complain and exit, instead of producing
the files.

Any thoughts?


My usual preference it to be explicit.  Removing the .. directory relies 
on implicit behavior.  I prefer using the current instructions.


  -- Bruce

--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-dev] Theme parsing error

2019-12-31 Thread Bruce Dubbs via blfs-dev

On 12/31/19 3:40 PM, Pierre Labastie via blfs-dev wrote:

Le 31/12/2019 à 17:50, Bruce Dubbs via blfs-dev a écrit :

On 12/31/19 9:06 AM, Pierre Labastie via blfs-dev wrote:

Le 31/12/2019 à 12:00, Bruce Dubbs via blfs-dev a écrit :

I'm getting a lot of warnings lately like:

Gtk-WARNING **: 04:36:49.304: Theme parsing error: gtk-contained.css:388:37:
Missing closing bracket for :not()

Has anyone else seen these?

I find gtk-contained.css in gtk+-3.24.13:

    gtk/theme/Adwaita/gtk-contained.css
    gtk/theme/HighContrast/gtk-contained.css

but they generate:

    build-gtk3/gtk/theme/Adwaita/gtk-contained.css
    build-gtk3/gtk/theme/HighContrast/gtk-contained.css

which have the problematic constructs.

The problem is not critical, but it is irritating.  The only thing I could
find on google was

https://github.com/B00merang-Project/macOS/issues/73

which is not very helpful and probably not relevant.



I've not seen this, but I usually launch graphical apps using a menu, so that
warning and error messages don't show up.

Which desktop? which app?


Actually most gtk3 apps.  Try for instance firefox.  I do test most graphical
apps over ssh so for FF I use 'firefox --no-remote'.  Other, simpler, apps to
try are gnome-calculator, evince, gparted, or gedit.

I get the same warnings if I go to my development system and run directly, so
it's not unique to running over ssh.

I'm using xfce, but that shouldn't make any difference.  I get the same thing
when using twm and xterm.



Sorry for delay in answering. I've tried to run gnome-calculator, epiphany,
and gnome-tweaks from gnome-terminal (I do not have firefox on this VM), and
seen no warning... I've tried under gnome and under openbox (not gnome-tweaks
under openbox).


Hmm.  Do you have a ~/.config/gtk-3.0/settings.ini file that uses a 
non-adwaita theme?


  -- Bruce

--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-dev] RFC: remove '..' in our meson commands

2019-12-31 Thread Xi Ruoyao via blfs-dev
Hi:

Now most of our meson commands contains a '..' but a few does not.  Maybe we
should remove all '..' in meson commands.  Reasons:

(1)  '..' is unnecessary in meson command, with "mkdir build; cd build".
(2)  Sometimes we forgot to "mkdir build; cd build" and type the meson command
in the source code directory, mistakenly.  With a '..' meson will believe '..'
is the building directory and produce build.ninja and many other files in '..'. 
It's hard to clean them because BLFS source code directory (/usr/src or
$HOME/src) contains lots of tarballs.  However, without '..' if we forgot to
type "mkdir build; cd build" meson would complain and exit, instead of producing
the files.

Any thoughts?
-- 
Xi Ruoyao 
School of Aerospace Science and Technology, Xidian University

-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-dev] clang-9.0.1, thunderbird-68.3.0 and optimized ryzen builds

2019-12-31 Thread Ken Moffat via blfs-dev
First, since the book has moved forward to January, a Happy New Year
to everyone.

Now that Doug has come up with a patch to let rustc-1.37.0 build
with system llvm-9.0.1 (thanks!), most people should have no
problems with clang.  However, my normal builds are optimized for
the machine I'm using, and on my more powerful machines they use
higher optimizations or extra security options.

I was testing the patch on a Ryzen 5 3400G using -O3 -march=native
-D_FORTIFY_SOURCE=2 -fstack-protector-strong in CFLAGS, CXXFLAGS and
also -D_GLIBCXX_ASSERTIONS in the CXXFLAGS.

Those have not given me any recent problems (some odd minor packages
were noted back in mid-year in my 'tuning' notes), but building
thunderbird died with a segmentation fault in llvm.

By a process of trial and error I established that without my
CFLAGS, CXXFLAGS it was fine.  Then, picking at the details, I
established that llvm thought (correctly) that it was built on
znver1 (Ryzen1), and that both -march=native and -march=znver1
showed the problem, but that the less-specific -march=amdfam10 was
ok.

Then I dropped back to -j1 for the C and C++ parts and saw that it
was failing to build a file in the elfhack code.  We've had problems
with elfhack on firefox over the years, it seems to be very prone to
breakage.  Disabling it allowed by build to complete, so I've now
added it to the book's mozconfig, but commented because I'm sure not
many people will need to disable it.

If I was actively _using_ thunderbird, I'm sure that I would build
it with gcc and g++, use the patch for system graphite and system
harfbuzz, and probably not need to disable the elf hack.  But that's
just a matter of preferences.

Regards,

ĸen
-- 
  We've all got both light and dark inside of us.
  What matters is the part we choose to act on.
  -- Sirius Black
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-dev] Theme parsing error

2019-12-31 Thread Bruce Dubbs via blfs-dev

On 12/31/19 9:06 AM, Pierre Labastie via blfs-dev wrote:

Le 31/12/2019 à 12:00, Bruce Dubbs via blfs-dev a écrit :

I'm getting a lot of warnings lately like:

Gtk-WARNING **: 04:36:49.304: Theme parsing error: gtk-contained.css:388:37:
Missing closing bracket for :not()

Has anyone else seen these?

I find gtk-contained.css in gtk+-3.24.13:

   gtk/theme/Adwaita/gtk-contained.css
   gtk/theme/HighContrast/gtk-contained.css

but they generate:

   build-gtk3/gtk/theme/Adwaita/gtk-contained.css
   build-gtk3/gtk/theme/HighContrast/gtk-contained.css

which have the problematic constructs.

The problem is not critical, but it is irritating.  The only thing I could
find on google was

https://github.com/B00merang-Project/macOS/issues/73

which is not very helpful and probably not relevant.



I've not seen this, but I usually launch graphical apps using a menu, so that
warning and error messages don't show up.

Which desktop? which app?


Actually most gtk3 apps.  Try for instance firefox.  I do test most 
graphical apps over ssh so for FF I use 'firefox --no-remote'.  Other, 
simpler, apps to try are gnome-calculator, evince, gparted, or gedit.


I get the same warnings if I go to my development system and run 
directly, so it's not unique to running over ssh.


I'm using xfce, but that shouldn't make any difference.  I get the same 
thing when using twm and xterm.


  -- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-dev] Theme parsing error

2019-12-31 Thread Pierre Labastie via blfs-dev
Le 31/12/2019 à 12:00, Bruce Dubbs via blfs-dev a écrit :
> I'm getting a lot of warnings lately like:
> 
> Gtk-WARNING **: 04:36:49.304: Theme parsing error: gtk-contained.css:388:37:
> Missing closing bracket for :not()
> 
> Has anyone else seen these?
> 
> I find gtk-contained.css in gtk+-3.24.13:
> 
>   gtk/theme/Adwaita/gtk-contained.css
>   gtk/theme/HighContrast/gtk-contained.css
> 
> but they generate:
> 
>   build-gtk3/gtk/theme/Adwaita/gtk-contained.css
>   build-gtk3/gtk/theme/HighContrast/gtk-contained.css
> 
> which have the problematic constructs.
> 
> The problem is not critical, but it is irritating.  The only thing I could
> find on google was
> 
> https://github.com/B00merang-Project/macOS/issues/73
> 
> which is not very helpful and probably not relevant.
> 

I've not seen this, but I usually launch graphical apps using a menu, so that
warning and error messages don't show up.

Which desktop? which app?

Pierre
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[blfs-dev] Theme parsing error

2019-12-31 Thread Bruce Dubbs via blfs-dev

I'm getting a lot of warnings lately like:

Gtk-WARNING **: 04:36:49.304: Theme parsing error: 
gtk-contained.css:388:37: Missing closing bracket for :not()


Has anyone else seen these?

I find gtk-contained.css in gtk+-3.24.13:

  gtk/theme/Adwaita/gtk-contained.css
  gtk/theme/HighContrast/gtk-contained.css

but they generate:

  build-gtk3/gtk/theme/Adwaita/gtk-contained.css
  build-gtk3/gtk/theme/HighContrast/gtk-contained.css

which have the problematic constructs.

The problem is not critical, but it is irritating.  The only thing I 
could find on google was


https://github.com/B00merang-Project/macOS/issues/73

which is not very helpful and probably not relevant.

  -- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page