Re: [blfs-dev] [blfs-book] r21178 - in trunk/BOOK: general/genutils general/graphlib lxde/desktop x/lib

[Thanos Baloukas via blfs-dev]

On 17/2/19 10:03 μ.μ., Bruce Dubbs via blfs-dev wrote:

On 2/17/19 1:38 PM, Pierre Labastie via blfs-dev wrote:

On 17/02/2019 19:56, Bruce Dubbs via blfs-dev wrote:

On 2/17/19 12:23 PM, Pierre Labastie via blfs-dev wrote:

On 17/02/2019 17:06, Bruce Dubbs via blfs-dev wrote:

On 2/17/19 7:35 AM, Pierre Labastie via blfs-dev wrote:






On 17/02/2019 00:16, bdubbs--- via blfs-book wrote:

Author: bdubbs
Date: Sat Feb 16 15:16:14 2019
New Revision: 21178

Log:
Add harfbuzz as an optional (circular) dependency of cairo.
[...]
Modified: trunk/BOOK/x/lib/cairo.xml
== 



--- trunk/BOOK/x/lib/cairo.xml Sat Feb 16 14:03:30 2019 (r21177)
+++ trunk/BOOK/x/lib/cairo.xml Sat Feb 16 15:16:14 2019 (r21178)
@@ -104,6 +104,7 @@
,
 and ,
,
+ ,
,
,
,
@@ -117,6 +118,10 @@
http://download.qt.io/archive/qt/4.8/;>Qt4.

+ There is a circular dependency between cairo and 
harfbuzz.

+ If cairo is built before harbuzz, it is necessary to rebuild cairo
+ after harfbuzz in order to build pango.
+

User Notes: 



Well, I'm not sure it has to be done this way: actually harfbuz is 
in the
"recommended" dependency chain of cairo: cairo recommends 
fontconfig, which

recommends freetype, which recommends harfbuzz...

I do not know whether you use jhalfs. If cairo got built before 
harfbuzz

using
jhalfs, this is most probably a bug in jhalfs, so please tell me.


I do not use jhalfs for BLFS (but it's critical for me in LFS).  As 
I build
for a release I try to get most of the optional dependencies as 
sell as the
required and recommended.  That does create some circular 
dependencies and it

bit me when I tried to build pango.



But that shouldn't happen, since harfbuzz is recommended (not 
directly, but it

is) for cairo. I'll do the following:
- on the harfbuzz page: note that the optional dep on cairo is 
circular, and

that it is recommended to build harfbuzz first
- on the cairo page: remove the optional dep on harfbuzz (it is 
already in the

recommended chain), which can only add confusion.


I thought we were only omitting deps in the required chain.

   -- Bruce




Not sure I understand: if a dep is in the recommended chain, what does it
bring to put it in optional? Specially in this case, harfbuzz is 
useless for
cairo without freetype and fontconfig... And freetype needs cairo. I 
think
what I have put in the book at rev 21189 allows preventing the issue 
you had.


Of course, it would not the same, for example, if a dep were required, 
and
also in the recommended dependency chain... Then it would have to be 
mentioned

as required.


package pango
   Recommended cairo (but needs harfbuzz first)

package cairo
   Required pixman and libpng only
   No mention of harfbuzz

harfbuzz X
   Optional cairo

If you build the optional cairo before harfbuzz, you can't build pango 
until cairo is rebuilt.


The following sequence

freetype
fontconfig
cairo
harfbuzz
freetype #Rebuild with Harfbuzz support
pango

works for me. Pango builds without the need to rebuild cairo
after harfbuzz.

The latest changes you made are fine, but there was not enough 
explanation before.


   -- Bruce


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

Re: [blfs-dev] rustc, and libssh2

[Thanos Baloukas via blfs-dev]

On 6/1/19 6:07 π.μ., Ken Moffat via blfs-dev wrote:

[ changing the subject for this old mail from last month, I've
   only just had time to retry the rustc build ]


I changed the subject in turn.


On Tue, Dec 25, 2018 at 09:07:57PM +0200, Thanos Baloukas via blfs-dev wrote:

Note that I've never installed libssh2. Rust downloads it, so for me
it should not be required. 1.31.0 had downloaded libssh2-sys v0.2.11
that 1.31.1 used as well, and on my previous system rustc-1.27.0 had
downloaded v0.2.6


I think I replied to that part last month - the download is a cargo
file, I suspect it links to system libssh2.




But as I said I've never installed libssh2.
On my system rustc-1.31.1 is linked to

gcc-8.2.0
glibc-2.28
llvm-7.0.1
openssl-1.1.1a
zlib-1.2.11

find /usr -iname "libssh*"
outputs nothing and there is nothing in /opt

Rust is a mystery. :)

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

Re: [blfs-dev] Libreoffice Update Policy?

[Thanos Baloukas via blfs-dev]

On 3/1/19 5:32 μ.μ., Douglas R. Reno via blfs-dev wrote:

Good morning,


What is our policy for updating Libreoffice? I have a ticket out for 
it's build problems with boost/poppler, and noticed that there is a new 
version (6.1.4.2) available.


I'm not sure if we wait until 6.2 releases or if we update to 6.1.4.x. 
It's possible that it'll fix our problems with poppler/boost, but I 
cannot be certain until I have the chance to build it (and Samba is 
sucking up my cycles).


Douglas R. Reno


I've installed 6.1.4.2 . It still needs the poppler and boost fixes.
I used three patches for poppler from Arch Linux and
sed 's/return loaded;/return bool{loaded};/' -i 
sfx2/source/appl/shutdownicon.cxx

for boost. I build libreoffice without cups and java.

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

Re: [blfs-dev] On updating old systems

[Thanos Baloukas via blfs-dev]

On 25/12/18 7:55 π.μ., Ken Moffat via blfs-dev wrote:

So, for my attempts to keep old systems viable, things are looking
better, at least until firefox-65 appears (that will need a newer
version of rustc, but for me 1.31.1 fails to build from source).


Well, rust really hates you! ):

Just finished 1.31.1 build with llvm-7.0.1. I had 1.31.0 built with
llvm-7.0.0 installed and used

cargo = "/usr/bin/cargo"
rustc = "/usr/bin/rustc"

in config.toml. It took 28 min with very few downloads.
1.31.0 was the first rust installation on this system and took 44 min
with the downloads. These are without -j passed, with AMD Ryzen 7 2700X,
which by the way has no problem at all (until I'll try to run the rust
tests, I'm afraid).

Note that I've never installed libssh2. Rust downloads it, so for me
it should not be required. 1.31.0 had downloaded libssh2-sys v0.2.11
that 1.31.1 used as well, and on my previous system rustc-1.27.0 had
downloaded v0.2.6

On my llvm builds I add the -DLLVM_ENABLE_RTTI=ON option because mesa
with meson needs it IIRC.

I don't use python3. I do

./x.py build
DESTDIR=${fakeroot} ./x.py install

x.py has #!/usr/bin/env python

These are my related to rust deviations from the book that I can
remember.

Merry Xmas!

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

Re: [blfs-dev] NetworkManager-1.14.2

[Thanos Baloukas via blfs-dev]

On 20/12/18 5:54 μ.μ., Roger Koehler via blfs-dev wrote:

On 20/12/18 5:42 μ.μ., Thanos Baloukas via blfs-dev wrote:
 > On 20/12/18 4:29 μ.μ., Roger Koehler via blfs-dev wrote:
 >> It still doesn't build for me. It wants the gtkdoc-scan
directory for
 >> some reason.
 >>
 >
 > Install gtk-doc or remove the -Ddocs=true option.
 >
I thought you were installing NetworkManager-1.14.4, sorry.


It appears that I am. I guess the book has been updated since I began 
this thread. That option should be removed unless gtk-doc is added to 
the required dependencies.




I think that gtk-doc has to be in the optional deps
and the -Ddocs=true has to go to Command Explanations.

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

Re: [blfs-dev] NetworkManager-1.14.2

[Thanos Baloukas via blfs-dev]

On 20/12/18 5:42 μ.μ., Thanos Baloukas via blfs-dev wrote:

On 20/12/18 4:29 μ.μ., Roger Koehler via blfs-dev wrote:
On Sun, Dec 16, 2018, 12:30 PM Brendan L via blfs-dev 
<mailto:blfs-dev@lists.linuxfromscratch.org> wrote:


    On Sat, Dec 15, 2018 at 6:47 PM Roger Koehler via blfs-dev
    mailto:blfs-dev@lists.linuxfromscratch.org>> wrote:
 >
 > It looks like NetworkManager requires ModemManager now. I can't
    find a
 > way to remove the dependency on mm-glib. -Dlibmm-glib=false didn't
 > work.

    I used -Dmodem_manager=false and it works for me.


Thanks! I also had to use -Djson_validarion=false and -Dovs=false 
without jansson installed which is listed as an optional dependency. I 
also had to install libpsl, so I guess it needs to be added as a 
required dependency.


It still doesn't build for me. It wants the gtkdoc-scan directory for 
some reason.




Install gtk-doc or remove the -Ddocs=true option.


I thought you were installing NetworkManager-1.14.4, sorry.

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

Re: [blfs-dev] NetworkManager-1.14.2

[Thanos Baloukas via blfs-dev]

On 20/12/18 4:29 μ.μ., Roger Koehler via blfs-dev wrote:
On Sun, Dec 16, 2018, 12:30 PM Brendan L via blfs-dev 
 wrote:


On Sat, Dec 15, 2018 at 6:47 PM Roger Koehler via blfs-dev
mailto:blfs-dev@lists.linuxfromscratch.org>> wrote:
 >
 > It looks like NetworkManager requires ModemManager now. I can't
find a
 > way to remove the dependency on mm-glib. -Dlibmm-glib=false didn't
 > work.

I used -Dmodem_manager=false and it works for me.


Thanks! I also had to use -Djson_validarion=false and -Dovs=false 
without jansson installed which is listed as an optional dependency. I 
also had to install libpsl, so I guess it needs to be added as a 
required dependency.


It still doesn't build for me. It wants the gtkdoc-scan directory for 
some reason.




Install gtk-doc or remove the -Ddocs=true option.

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

[blfs-dev] xfce4-power-manager-1.6.1 remove UDisks-1.0.5 dependency

[Thanos Baloukas]

See

https://github.com/xfce-mirror/xfce4-power-manager/commit/3ad75fad293fb66e6316aa5820ee064f264eafa4

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

Re: [blfs-dev] fluxbox - hard to move windows

[Thanos Baloukas]

On 18/05/2018 11:44 μμ, Ken Moffat wrote:

Dunno which theme ('style') I had been using (just basically grey
title bars), but changing to Blueflux via the fluxbox menu lets me
move the windows around - but the three icons for min/max/close are
just dark grey globs on light grey backgrounds.  Hmm some of the
styles in the list give hard-to-read menus and one of them worked
once for moving but then rolled up.  Currently I'm using Makro.


I've seen many times on fluxbox styles bad background - foreground -
highlight combinations in the menus, that made them unreadable. Not
strange, since they are not maintained for a long time. It reminds me
the days I was using fluxbox and was altering the styles to suit my
taste.



Ahh - double-clicking on the title bar DOES rollup the window, some
of my problem is because this mouse is a bit "variable" at sending
clicks.  And when it is rolled up, double clicking will then unroll
it.

Sorted! (apart from changing the mouse ;-)

ĸen



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

Re: [blfs-dev] fluxbox - hard to move windows

[Thanos Baloukas]

On 18/05/2018 04:22 πμ, Ken Moffat wrote:

On a new build I always use fluxbox as my first windowmanager.  With
the current build this has become "unpleasant" - I thought that the
icon in the top left corner used to bring up a menu for things like
moving a window to another desktop (or 'workspace' in fluxbox
terms), but it now seems to do nothing (although I've managed to get
my initial urxvt term on all 4 desktops).  But the real problem is
that it has suddenly become painful to move windows (so far, only
attempted with glxgears and urxvt):

Some themes I've used in the past have had four icons at top right
of the titlebar, with the first rolling up the window so that only
the titlebar is visible.  But I'm using a "regular" theme with just
iconify / maximize / close.  If I try to drag the titlebar, the
window rolls up and the only way to get it back is to click on
maximize twice (first to maximize, second click to restore to
unmaximized i.e. normal).

This is with the radeon driver, I'm hoping that out of my own build
only fluxbox is affected.

I assume this is fallout from xorg-server-1.20 rather than from
gcc-8.1.



On an up to date svn installation, mesa built with meson and some
open ticket updates, e.g. libdmx-1.1.4

Radeon here too. lspci reports Caicos PRO Radeon HD 7450

The windows on fluxbox move fine dragging them by the titlebar.
Resizing works fine too. All the rest windows' functions perform well
with left clicking on the title bar's icons or via the title bar right
click menu. I tried the above on several themes and apps. I did not test
fluxbox extensively though, since I build it for early xorg testing
only.

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

Re: [blfs-dev] systemd-238

[Thanos Baloukas]

On 15/05/2018 09:08 μμ, Cyrillo Baggins wrote:
I don't see the five sed command in the current BLFS book, I guess 
that's explain the error


http://www.linuxfromscratch.org/blfs/view/systemd/general/systemd.html




On Tue, May 15, 2018 at 10:45 PM, Bruce Dubbs > wrote:


On 05/15/2018 07:36 AM, Cyrillo Baggins wrote:

Hello,

today I did a fresh build of the latest lfs systemd dev book and
blfs systemd dev book.

systemd-238 fails to build even with the upstream patch, the
error I get references to the following bug:

https://github.com/systemd/systemd/issues/8507



When building with systemd-master.zip as source it works.


There are five sed commands for the systemd package in the book. 
Did you apply all of them?


   -- Bruce


Bruce,

The first patch I sent in

http://lists.linuxfromscratch.org/pipermail/blfs-dev/2018-March/034320.html

included only the libgpg-error-1.28 fixes. As I wrote in the above mail,
I had applied the sed commands by the lfs-systemd book for the headers' 
fix before the patch. When you put that patch in the book without the

sed commands, I sent a new patch that included the headers' fix

http://lists.linuxfromscratch.org/pipermail/blfs-dev/2018-April/034328.html

and you replied that you committed that

http://lists.linuxfromscratch.org/pipermail/blfs-dev/2018-April/034329.html

but that second patch did not find its way in the book.

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

Re: [blfs-dev] xfce and gcc8

[Thanos Baloukas]

On 14/05/2018 09:45 πμ, Bruce Dubbs wrote:
Has anyone else built xfce using gcc8 yet?  I've built it, but it makes 
xorg segfault at startup.  I've built twm, lxde, openbox, sawfish, 
icewm, and fluxbox and they all run OK.


It's possible that I may have missed some dependencies and I can try 
rebuilding xfce, but I thought I'd ask here.  I'll note that I start 
xfce with startx and .xinitrc uses:


exec startxfce4 --with-ck-launch

but I get the same thing with just startxfce4 at the command line.


It's running fine here on current blfs-systemd svn, started with
dbus-launch --exit-with-session startxfce4
in ~/.xinitrc and running
exec startx "$@" 2>$HOME/xsession.errors
from a script. It creates ~/.xfce4-session.verbose-log. Do you have
that? On my previous installations I had some early notify-send
core dumps in /var/lib/systemd/coredump which I don't have now. It seems
to me also that text scrolling and windows exchange with a keyboard
shortcut is slightly faster than my previous svn installation with
gcc-7.3.0 xorg-server-1.19.6 and mesa-18.0.2.

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

[blfs-dev] Firefox-60.0 missing patch command

[Thanos Baloukas]

The command to apply the required ffmpeg-4.0 patch is missing
from the instructions.

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

Re: [blfs-dev] xf86-video-fbdev-0.4.4 fails with gcc-8.1.0

[Thanos Baloukas]

On 12/05/2018 09:01 μμ, Bruce Dubbs wrote:

On 05/12/2018 01:52 AM, Thanos Baloukas wrote:

fbdev.c:898:7: error: #if with no expression
  #if XV
    ^

sed 's/if XV/ifdef XV/' -i src/fbdev.c


I did a test build of fbdev and cannot duplicate the error.  I do have 7 
warnings on that page, but no errors.


I do see in configure:

#include "xorg-server.h"
#if !defined XV
#error XV not defined
#endif

xorg-server.h should have:

#define XV 1

I wonder if the issue you are seeing has to do with dependencies in 
either xorg-server or mesa.



Maybe it's due to my mesa build with meson.

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

[blfs-dev] xf86-video-fbdev-0.4.4 fails with gcc-8.1.0

[Thanos Baloukas]

fbdev.c:898:7: error: #if with no expression
 #if XV
   ^

sed 's/if XV/ifdef XV/' -i src/fbdev.c

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

[blfs-dev] nasm-2.13.03 failed on blfs-svn

[Thanos Baloukas]

gcc -c -g -O3 -fwrapv -U__STRICT_ANSI__ -fno-common -Werror=attributes 
-W -Wall -pedantic -Wc90-c99-compat -Wno-long-long -Werror=implicit 
-Werror=missing-
braces -Werror=return-type -Werror=trigraphs -Werror=pointer-arith 
-Werror=missing-prototypes -Werror=missing-declarations -Werror=comment 
-Werror=vla -DHA
VE_CONFIG_H -I. -I. -I./include -I./include -I./x86 -I./x86 -I./asm 
-I./asm -I./disasm -I./disasm -I./output -I./output -o stdlib/snprintf.o 
stdlib/snprintf.c

In file included from stdlib/snprintf.c:13:
./include/nasmlib.h:194:1: error: ...pure... attribute on function 
returning ...void... [-Werror=attributes]

 void pure_func seg_init(void);
 ^~~~

Two solutions:

sed 's/-Werror=attributes //' -i Makefile

or by a fedora patch

sed -e 's/pure_func seg_init/seg_init/' \
-e 's/pure_func seg_alloc/seg_alloc/' -i include/nasmlib.h

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

Re: [blfs-dev] Systemd-238 in BLFS-dev doesn't compile

[Thanos Baloukas]

On 04/05/2018 05:26 μμ, John Burrell wrote:
Using the commands for systemd-238 in the sysutils section of the 
systemd version of the Book gives the following error:


[316/1488] Compiling C object 'src/core/core@sta/dbus-mount.c.o'.
FAILED: src/core/core@sta/dbus-mount.c.o
ccache cc  -Isrc/core/core@sta -Isrc/core -I../src/core -I. -I../ 
-Isrc/libsystemd-network -I../src/libsy
stemd-network -I../src/libsystemd/sd-network 
-I../src/libsystemd/sd-netlink -I../src/libsystemd/sd-id128
-I../src/libsystemd/sd-hwdb -I../src/libsystemd/sd-device 
-I../src/libsystemd/sd-bus -Isrc/libudev -I../s
rc/libudev -Isrc/udev -I../src/udev -Isrc/login -I../src/login 
-Isrc/timesync -I../src/timesync -Isrc/res
olve -I../src/resolve -Isrc/journal -I../src/journal -Isrc/systemd 
-I../src/systemd -Isrc/shared -I../src
/shared -Isrc/basic -I../src/basic -I/usr/include/libmount 
-I/usr/include/blkid -I/usr/include/uuid -fdia
gnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch 
-std=gnu99 -O0 -g -Wextra -Werror=
undef -Wlogical-op -Wmissing-include-dirs -Wold-style-definition 
-Wpointer-arith -Winit-self -Wdeclaratio
n-after-statement -Wfloat-equal -Wsuggest-attribute=noreturn 
-Werror=missing-prototypes -Werror=implicit-
function-declaration -Werror=missing-declarations -Werror=return-type 
-Werror=incompatible-pointer-types
-Werror=format=2 -Wstrict-prototypes -Wredundant-decls 
-Wmissing-noreturn -Wimplicit-fallthrough=5 -Wshad
ow -Wendif-labels -Wstrict-aliasing=2 -Wwrite-strings -Werror=overflow 
-Wdate-time -Wnested-externs -ffas
t-math -fno-common -fdiagnostics-show-option -fno-strict-aliasing 
-fvisibility=hidden -fstack-protector -
fstack-protector-strong --param=ssp-buffer-size=4 -fPIE 
-Wno-unused-parameter -Wno-missing-field-initiali
zers -Wno-unused-result -Wno-format-signedness -Wno-error=nonnull 
-Werror=shadow -include config.h -fPIC
-pthread -MD -MQ 'src/core/core@sta/dbus-mount.c.o' -MF 
'src/core/core@sta/dbus-mount.c.o.d' -o 'src/core

/core@sta/dbus-mount.c.o' -c ../src/core/dbus-mount.c
In file included from ../src/basic/util.h:47:0,
                  from ../src/basic/hashmap.h:30,
                  from ../src/shared/bus-util.h:31,
                  from ../src/core/dbus-mount.c:21:
../src/basic/missing.h:528:17: error: expected identifier before numeric 
constant

  #define MS_MOVE 8192

This appears to be the same error identified in the LFS version of 
systemd-238.


Should the commands that are in the LFS version:

sed -i '527,565 d'  src/basic/missing.h
sed -i '24 d'   src/core/load-fragment.c
sed -i '53 a#include ' src/shared/bus-unit-util.c


also be in the BLFS version?

jb.


It's been reported in the following thread too:

http://lists.linuxfromscratch.org/pipermail/blfs-support/2018-April/080065.html

Either the patch in the book must be replaced by the revised one or
the sed commands by the LFS book must be used.

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

Re: [blfs-dev] [PATCH] Subversion-1.10.0 has new optional dependencies

[Thanos Baloukas]

On 16/04/2018 06:52 μμ, Bruce Dubbs wrote:

On 04/16/2018 08:19 AM, Thanos Baloukas wrote:

Configure options --with-lz4=internal and --with-utf8proc=internal
are now required, if the optional dependencies are not installed.


Thanks for the patch.  Applied perfectly.


Glad I could help.

That's what I get for waiting to update the book after I actually build 
the package.  I did have those options in my build script.  I just 
forgot when I updated to book.


   -- Bruce


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

[blfs-dev] [PATCH] Subversion-1.10.0 has new optional dependencies

[Thanos Baloukas]

Configure options --with-lz4=internal and --with-utf8proc=internal
are now required, if the optional dependencies are not installed.

--
Thanos
Index: general/prog/subversion.xml
===
--- general/prog/subversion.xml	(revision 20087)
+++ general/prog/subversion.xml	(working copy)
@@ -111,10 +111,13 @@
 -->
   ,
   ,
+  ,
 
(with sqlite support for the tests),
-  , and
-   (for building Perl, Python and Ruby bindings)
+  ,
+   (for building Perl, Python and Ruby bindings),
+  https://github.com/lz4/lz4/releases;>LZ4, and
+  http://git.netsurf-browser.org/libutf8proc.git/;>UTF8proc
 
 
 Optional (for the Java Bindings)
@@ -148,9 +151,11 @@
   commands:
 
 
-./configure --prefix=/usr\
---disable-static \
---with-apache-libexecdir 
+./configure --prefix=/usr \
+--disable-static  \
+--with-apache-libexecdir  \
+--with-lz4=internal   \
+--with-utf8proc=internal 
 make
 
 
@@ -258,6 +263,11 @@
 
 
 
+  --with-lz4=internal, --with-utf8proc=internal:
+  Remove them if you have installed the optional dependencies.
+
+
+
   --enable-javahl: enables compilation of Java high level
   bindings. Running make javahl is necessary to do
   the compilation.
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] [PATCH] Xfburn-0.5.5 dependencies

[Thanos Baloukas]

On 12/04/2018 08:32 μμ, William Harrington wrote:

On Thu, 12 Apr 2018 11:09:10 -0500
Bruce Dubbs <bruce.du...@gmail.com> wrote:


On 04/12/2018 03:52 AM, Thanos Baloukas wrote:

On 12/04/2018 01:25 πμ, Bruce Dubbs wrote:

On 04/11/2018 02:42 PM, Thanos Baloukas wrote:

I remembered that when I was installing 8.2 I had seen some
dependencies' inconsistencies on this package. No linkage with
libisoburn, grepping  the headers and the binaries returns nothing, and
finally it works fine on my laptop built without libisoburn.

It links with libxfce4ui and libxfce4util and the dep chain is
libxfce4ui -> Xfconf -> libxfce4util, so I changed that too.



Isn't the above a good reason for the libxfce4util dependency to be
replaced by libxfce4ui as I have in the patch?


OK.  I'll do that.


I think that no other blfs package needs libisoburn. It is referenced in

http://www.linuxfromscratch.org/lfs/view/development/chapter08/grub.html

but there must be other tools in blfs for that, so maybe it can be
archived.


brasero references libisoburn




Xorriso from libisoburn uses it.

  readelf -d /usr/bin/xorriso | grep NEEDED
=
0x0001 (NEEDED) Shared library: [libisoburn.so.1]
=
^


We were discussing about **packages** that need libisoburn **package**
That readelf says that xorriso by libisoburn package links to
libisoburn.so.1 by its own package.

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

Re: [blfs-dev] [PATCH] Xfburn-0.5.5 dependencies

[Thanos Baloukas]

On 12/04/2018 01:25 πμ, Bruce Dubbs wrote:

On 04/11/2018 02:42 PM, Thanos Baloukas wrote:

I remembered that when I was installing 8.2 I had seen some
dependencies' inconsistencies on this package. No linkage with
libisoburn, grepping  the headers and the binaries returns nothing, and
finally it works fine on my laptop built without libisoburn.

It links with libxfce4ui and libxfce4util and the dep chain is
libxfce4ui -> Xfconf -> libxfce4util, so I changed that too.



Isn't the above a good reason for the libxfce4util dependency to be
replaced by libxfce4ui as I have in the patch?


I think that no other blfs package needs libisoburn. It is referenced in

http://www.linuxfromscratch.org/lfs/view/development/chapter08/grub.html

but there must be other tools in blfs for that, so maybe it can be 
archived.


brasero references libisoburn


Not really. Brasero references libburn and libisofs. Rethinking that,
libisoburn has not only libs, so no need to be archived, even if
it's not used by another package.

I don't use brasero, but occasioned by your reference I downloaded the
tarball to take a look. By the README:

Brasero default backend is provided by cdrtools/cdrkit but libburn can
be used as an alternative

The book has recommended libburn and optional runtime cdrtools.

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

[blfs-dev] [PATCH] Xfburn-0.5.5 dependencies

[Thanos Baloukas]

I remembered that when I was installing 8.2 I had seen some
dependencies' inconsistencies on this package. No linkage with
libisoburn, grepping  the headers and the binaries returns nothing, and
finally it works fine on my laptop built without libisoburn.

It links with libxfce4ui and libxfce4util and the dep chain is
libxfce4ui -> Xfconf -> libxfce4util, so I changed that too.

I think that no other blfs package needs libisoburn. It is referenced in

http://www.linuxfromscratch.org/lfs/view/development/chapter08/grub.html

but there must be other tools in blfs for that, so maybe it can be archived.

--
Thanos
Index: xfce/apps/xfburn.xml
===
--- xfce/apps/xfburn.xml	(revision 20075)
+++ xfce/apps/xfburn.xml	(working copy)
@@ -78,8 +78,9 @@
 Required
 
   ,
-  , and
-  
+  ,
+  , and
+  
 
 
 Optional
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] Anyone building rustc on a ryzen ?

[Thanos Baloukas]

On 09/04/2018 06:36 μμ, Ken Moffat wrote:

Yes, I understood.  But in the absence of any other strategy I
decided to try it just in case (primarily because this was the first
time I'd seen 3.7GHz during this run and the load was fairly low.

I took a look at the bios options after I wrote that - but this is
the low-end A320 with no overclocking options for the CPU.  And the
RAM seemed fine in memtest86.  Will have another look later, there
was one BIOS option I need to research (soemthing like 'use AsRock
profile or AMD profile - I left it on the AsRock default), and maybe
RAM voltage can be adjusted.

ĸen



I can't predict what ryzen 2 will be, the first generation however was a
lottery, so I thought that if I'll be unlucky and have to do battle with
some buggy cpu, I better have a full-featured motherboard in my arsenal.
AsRock here too, but X370 Taichi.

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

Re: [blfs-dev] Anyone building rustc on a ryzen ?

[Thanos Baloukas]

On 09/04/2018 03:07 πμ, Ken Moffat wrote:

On Sun, Apr 08, 2018 at 12:11:39PM +0300, Thanos Baloukas wrote:

On 08/04/2018 06:30 πμ, Ken Moffat wrote:

On Sun, Apr 08, 2018 at 04:01:11AM +0300, Thanos Baloukas wrote:

On 07/04/2018 11:57 μμ, Ken Moffat wrote:




The only problem the machine had was freezing on idle. In the beginning
I disabled the cool 'n quiet in the bios and that solved the problem.
Then I found this bug report,

https://bugzilla.kernel.org/show_bug.cgi?id=196683



I've been running cool 'n quiet without any problems (apart from
this) and using lm_sensors I can see CPU frequencies at 3592 MHz on
all cores, or a bit above 3600 on only one core - for a nominal max
frequency of 3500 - and much lower frequencies when less-busy)

To be clear, you turned off C6 if that is available as a bios
option, OR added CONFIG_RCU_NO_CB_CPU and added a boot argument of
rcu_nocbs=0-3 ?


Didn't play with C6 at all. Using a kernel with

# RCU Subsystem
CONFIG_TREE_RCU=y
# CONFIG_RCU_EXPERT is not set
CONFIG_SRCU=y
CONFIG_TREE_SRCU=y
CONFIG_TASKS_RCU=y
CONFIG_RCU_STALL_COMMON=y
CONFIG_RCU_NEED_SEGCBLIST=y
CONFIG_RCU_NOCB_CPU=y
CONFIG_HAVE_RCU_TABLE_FREE=y
# RCU Debugging
# CONFIG_PROVE_RCU is not set
# CONFIG_RCU_PERF_TEST is not set
CONFIG_RCU_TORTURE_TEST=m
CONFIG_RCU_CPU_STALL_TIMEOUT=60
# CONFIG_RCU_TRACE is not set
# CONFIG_RCU_EQS_DEBUG is not set

and rcu_nocbs=0-3 on kernel command line was enough.



Thanks.  Tried that, but it did not help.  I also tried logging
output from top and sensors every 5 seconds (that took two goes,
first time I fubar'd and emptied the log on every pass through the
loop).  I noticed that 5 seconds before the crash, one core was
running at just over 3.7 GHz (boosted) and the others were slowing
down.


What I did is just a workaround for the freezing on idle problem and I
wrote it just to answer to your question. It was no way a suggestion
to solve your problem. As I wrote in my previous reply, I would suspect
not enough voltage fed to the cpu and/or to ram, causing the reboots.


So I decided to try turning of c6 states anyway, using zenstates.py
(it's on github with some other zen stuff) - bad mistake : the Xorg
display went blank while I was watching, but the box did not reboot
and neither of the front-panel switches (reboot, on/off) worked.

For the moment I'm going to step away from this (I've got something
else to install and test here).

ĸen



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

Re: [blfs-dev] Anyone building rustc on a ryzen ?

[Thanos Baloukas]

On 08/04/2018 06:30 πμ, Ken Moffat wrote:

On Sun, Apr 08, 2018 at 04:01:11AM +0300, Thanos Baloukas wrote:

On 07/04/2018 11:57 μμ, Ken Moffat wrote:




The only problem the machine had was freezing on idle. In the beginning
I disabled the cool 'n quiet in the bios and that solved the problem.
Then I found this bug report,

https://bugzilla.kernel.org/show_bug.cgi?id=196683



I've been running cool 'n quiet without any problems (apart from
this) and using lm_sensors I can see CPU frequencies at 3592 MHz on
all cores, or a bit above 3600 on only one core - for a nominal max
frequency of 3500 - and much lower frequencies when less-busy)

To be clear, you turned off C6 if that is available as a bios
option, OR added CONFIG_RCU_NO_CB_CPU and added a boot argument of
rcu_nocbs=0-3 ?


Didn't play with C6 at all. Using a kernel with

# RCU Subsystem
CONFIG_TREE_RCU=y
# CONFIG_RCU_EXPERT is not set
CONFIG_SRCU=y
CONFIG_TREE_SRCU=y
CONFIG_TASKS_RCU=y
CONFIG_RCU_STALL_COMMON=y
CONFIG_RCU_NEED_SEGCBLIST=y
CONFIG_RCU_NOCB_CPU=y
CONFIG_HAVE_RCU_TABLE_FREE=y
# RCU Debugging
# CONFIG_PROVE_RCU is not set
# CONFIG_RCU_PERF_TEST is not set
CONFIG_RCU_TORTURE_TEST=m
CONFIG_RCU_CPU_STALL_TIMEOUT=60
# CONFIG_RCU_TRACE is not set
# CONFIG_RCU_EQS_DEBUG is not set

and rcu_nocbs=0-3 on kernel command line was enough.


Mine has a recent motherboard, the bios seems to be a few versions
on from what was initially used.



There is a new bios version for ryzen 2 for my motherboard, but I
thought it would be better to not update now, since the system is in a
good state and the update could make things worst. Ryzen 2 comes out in
a few weeks and I'll do the update (if and) when I'll get the new cpu.



Yes, RAM variations seem to have caused problems (although recent
bios updates are supposed to help).  Mine is 2666 but only 2x4GB.



With 2x16, while compiling with all cores I can do everything with no
lug at all.



For that, *many* thanks - it confirms the problem is only when
running the tests (or rather, there is no problem with building
or running firefox ;)



Yes, firefox-59.0.2 built with rust-1.25 runs fine.


I suppose that the segfaults, and reboots, might be down to a more
machine-specific issue.



Possibly related to not enough voltage fed to the cpu, which can be
addressed with bios updates. There are reports that overclocking the cpu
or increasing the voltages slightly, improves things, but as I said I'm
intending to upgrade soon, so I did not test anything for the moment.



Maths seems to still not be a strong point for the overall total :)


I noticed that too, but did not search further.


I'll also look at C6.  And I might have to leave it running even if
there are traps, to see if it reboots.

Thanks.


Thank you for your valuable contribution to LFS.

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

Re: [blfs-dev] Anyone building rustc on a ryzen ?

[Thanos Baloukas]

On 07/04/2018 11:57 μμ, Ken Moffat wrote:

Does anyone here use a ryzen ?  I got a 1300X recently, and building
current rustc - and using that to build firefox - seems to work
fine.  BUT - I had not bothered to run the rustc testsuite because
it takes so long.

But those initial builds of rustc were to install it in /opt -
seemed good enough, so I decided to install it in /usr and to see
how the test results looked.  Disaster.

Every time I run the tests, within a couple of minutes I get two
traps for invalid opcodes, followed a few minutes later by two
segfaults (noted by reading syslog, the tests seem to continue as
normal).  But if I leave the tests running, about 20 to 30 minutes
later (before the end of the tests, according to what got written
to the log) the machine reboots.  These are all that got logged the
first time, nothingrelated to the reboot.

Apr  6 06:37:48 origin kernel: [ 3695.201558] traps: backtrace.stage[17714] 
trap invalid opcode ip:7f1e76696498 sp:7ffc6848af80 error:0 in 
libstd-23815cc482a70678.so[7f1e7663c000+155000]
Apr  6 06:37:48 origin kernel: [ 3695.231521] traps: backtrace.stage[17720] 
trap invalid opcode ip:7f76e0ff0498 sp:7ffc2bf46850 error:0 in 
libstd-23815cc482a70678.so[7f76e0f96000+155000]
Apr  6 06:41:17 origin kernel: [ 3903.999612] segfault-no-out[31250]: segfault 
at 0 ip 555aa6cd0b69 sp 7ffeb0d96fa0 error 6 in 
segfault-no-out-of-stack.stage2-x86_64-unknown-linux-gnu[555aa6ccd000+5000]
Apr  6 06:41:23 origin kernel: [ 3910.633482] signal-exit-sta[32055]: segfault 
at 1 ip 55afe3b44efc sp 7fffc985f660 error 6 in 
signal-exit-status.stage2-x86_64-unknown-linux-gnu[55afe3b42000+4000]
Apr  6 06:41:26 origin kernel: [ 3913.231883] traps: simd-target-fea[32330] 
trap invalid opcode ip:55b72481e89c sp:7fff97757750 error:0 in 
simd-target-feature-mixup.stage2-x86_64-unknown-linux-gnu[55b72481b000+7000]

Now that I know it will reboot, I've spend some hours trying to work
around this (I'm assuming it uses opcodes not valid on Ryzen, but
for somiething which is only exercised by the testsuite) - failed
completely - and eventually raised an issue.

However, I've now looked at rustc-1.22.1 and that too gets the same
two traps.  so, I'm thinking that I should put a big warning in the
book to not run the tests on a Ryzen.

But confirmation that the tests segfault on somebody else's ryzen
would be conclusive, which is why I'm asking: has anyone already run
the rustc tests on a ryzen ?  If not, is anybody willing to give it
a go on a ryzen ?  Waiting for it to reboot is not required, just
keep an eye on the system log or journal and stop the tests if the
segfaults occur.

My machine otherwise seems stable (I replaced the nvidia graphics
card with a low-nd radeon because nouveau frequently locked up X,
since then it has seemed fine apart from this.  And no, I'm not
overclocking, the CPU seems to run cool (maximum I've seen was low
50s degrees).


I was going to get an 8 core 16 thread Ryzen, but after the problems
they exhibited I decided to get a 4 core 4 thread 3 1200 for now,
and upgrade when Ryzen 2 comes out, be tested and proved to be stable.

I knew that I needed a host with latest gcc to build LFS, so I used 
Fedora 27 with gcc-7.3. Everything went smoothly, except some core

dumps during the gcc tests. I ran the tests only for the recommended
by the book packages.

The only problem the machine had was freezing on idle. In the beginning
I disabled the cool 'n quiet in the bios and that solved the problem.
Then I found this bug report,

https://bugzilla.kernel.org/show_bug.cgi?id=196683

enabled cool 'n quiet, tried the proposed RCU solution and it worked.
Since then the system is rock stable. Cpu at stock speed, 32GB ram at
rated 3200MHz. Ram speed is not that important for our use, but I
favored that ram kit because it is one of the most compatible with
Ryzen according many testers' and users' reports.

On my svn installation I have rust-1.25.0 and used that to build
firefox-59.0.2. When I read your mail I installed gdb and rebuilt
to run the tests. No reboots. About 15 tests dumped core. Iindicatively:

systemd-coredump[2185]: Process 2172 (issue-24313.sta) of user 1001 
dumped core.


Stack trace of thread 2183:
#0  0x7f7f8e582e5b __GI_raise (libc.so.6)
#1  0x7f7f8e584211 __GI_abort (libc.so.6)
#2  0x7f7f8edb2339 
_ZN3std3sys4unix14abort_internal17he99af7afd6098d88E 
(libstd-23815cc482a70678.so)
#3  0x7f7f8edc6a8b 
_ZN3std10sys_common4util5abort17h240ecd99fa33591bE 
(libstd-23815cc482a70678.so)

#4  0x7f7f8ed976a2 rust_panic (libstd-23815cc482a70678.so)
#5  0x7f7f8ed975c2 
_ZN3std9panicking20rust_panic_with_hook17hfcd2a02d3b761d28E 
(libstd-23815cc482a70678.so)
#6  0x5602b2dc24c4 n/a 
(/build/tmp/rustc-1.25.0-src/build/x86_64-unknown-linux-gnu/test/run-pass/issue-24313.stage2-x86_64-unknown-linux-gnu)


3 traps:

Απρ 08 02:17:50 kernel: traps: backtrace.stage[11039] trap invalid 
opcode ip:7fd12c93a488 sp:7ffc99eb6230 

Re: [blfs-dev] [lfs-dev] systemd-238

[Thanos Baloukas]

On 30/03/2018 04:04 μμ, Thanos Baloukas wrote:

On 30/03/2018 12:09 πμ, Thanos Baloukas wrote:

On 29/03/2018 07:56 μμ, Bruce Dubbs wrote:

On 03/29/2018 01:02 AM, William Harrington wrote:

On Sat, 24 Mar 2018 10:52:18 -0500
Bruce Dubbs <bruce.du...@gmail.com> wrote:
...



I'm  on it, I'll start a jhalfs automated build soon and made 
the necessary

changes to packages.ent

in LFS-svn sources to use systemd 238 instead of 237.

Base Linux in front of the chroot is debian 9.4 at the moment 
(I've been

itchy to replace it with

LFS+BLFS for a long time already).

Alain


Looks like there's a bit of a mess with the headers; there's an 
issue open. A
commit was made yesterday to "make it more robust," but in the 
meantime,

there's a patch available in the issue that is reported to work:

https://github.com/systemd/systemd/issues/8507


I just had an issue where I was going to upgrade from 236 to 237 
and I had upgraded libgpg-error from 1.27 to 1.28  I had to go 
back to 1.27 for 236 and 237 to build. I'm going to test 238 and 
see what happens.


with libgpg-error 1.27 both Systemd 236, 237 and 238 build fine. 
It's libgpg-error 1.28 when the issue surfaces.


https://hastebin.com/irotixezin.cs


Thanks for the report.  It's not an issue in LFS since we don't have
libgpg-error error there, but we will need to address it for BLFS.

Will this sed fix it?

sed -i '422,423d' src/basic/macro.h

    -- Bruce


Hello Bruce,

No, it does not.

Can any one confirm when building Systemd with gcrypt and libgcrypt 
1.28 that they need to revert to 1.27?


I've had to revert to libgcrypt 1.27 in all instances of testing. I 
suspect in the Systemd BLFS book when people use Gcrypt with Systemd 
and libgcrypt 1.28 they will need to revert to libgcrypt 1.27. It's 
always successful with libgcrypt 1.27 and no 1.28.



libgcrypt or libgpg-error?  I note that libgcrypt-1.8.2 does 
currently require libgpg-error-1.28.



On current blfs-svn with libgpg-error-1.28 and libgcrypt-1.8.2
systemd-238 failed and I had to add -Dgcrypt=false to meson options
to build, install and test. I confirm that reverting to
libgpg-error-1.27 it builds. I did not install this build though.


Following up reinstalled libgpg-error-1.28, made a diff on
systemd-238 and commit c58ab03f64890e7db88745a843bd4520e307099b
which Arch Linux is currently using, rebuilt with the patch in chroot
and booted. So far so good. Nothing strange in the logs.
If someone wants to test, commands used:

sed '171,$ d' -i src/resolve/meson.build
sed -i '527,565 d'  src/basic/missing.h
sed -i '24 d'   src/core/load-fragment.c
sed -i '53 a#include ' src/shared/bus-unit-util.c
patch -Np1 -i ${SRC_DIR}/systemd-238-upstream_fixes.patch
sed -i 's/GROUP="render", //' rules/50-udev-default.rules.in

meson --prefix=/usr   \
   --sysconfdir=/etc   \
   --localstatedir=/var    \
   -Dblkid=true    \
   -Dbuildtype=release \
   -Ddefault-dnssec=no \
   -Dfirstboot=false   \
   -Dinstall-tests=false   \
   -Dldconfig=false    \
   -Drootprefix=   \
   -Drootlibdir=/lib   \
   -Dsplit-usr=true    \
   -Dsysusers=false    \
   -Db_lto=false   \
   $PWD build

cd build
ninja -v
DESTDIR=${fakeroot} ninja install
rm -rf ${fakeroot}/usr/lib/rpm

Pam config the same as in the blfs-svn book for systemd-237
Patch attached.


I did not include the headers' fix in the patch. I made another
witch includes the LFS book's fix. See attachment.

And a small typo:
patch -Np1 -i ../systemd-238-upstream_fixes.patch-1
patch -Np1 -i ../systemd-238-upstream_fixes-1.patch

Thank you for all your hard work.

--
Thanos
diff -Naur systemd-a/hwdb/60-evdev.hwdb systemd-b/hwdb/60-evdev.hwdb
--- systemd-a/hwdb/60-evdev.hwdb	2018-03-06 00:16:37.0 +0200
+++ systemd-b/hwdb/60-evdev.hwdb	2018-04-02 02:13:54.239434763 +0300
@@ -114,8 +114,10 @@
  EVDEV_ABS_35=::18
  EVDEV_ABS_36=::16
 
-# Asus X550CC and S550CB
-evdev:name:ETPS/2 Elantech Touchpad:dmi:*:svnASUSTeKCOMPUTERINC.:pn?550C?:*
+# Asus X550CC, S550CB and N550JV
+evdev:name:ETPS/2 Elantech Touchpad:dmi:*:svnASUSTeKCOMPUTERINC.:pnX550CC:*
+evdev:name:ETPS/2 Elantech Touchpad:dmi:*:svnASUSTeKCOMPUTERINC.:pnS550CB:*
+evdev:name:ETPS/2 Elantech Touchpad:dmi:*:svnASUSTeKCOMPUTERINC.:pnN550JV:*
  EVDEV_ABS_00=::31
  EVDEV_ABS_01=::30
  EVDEV_ABS_35=::31
@@ -144,6 +146,20 @@
  EVDEV_ABS_00=::14
  EVDEV_ABS_01=::18
 
+# Dell Inspiron 3537 - PS/2
+evdev:name:SynPS/2 Synaptics TouchPad:dmi:*svnDellInc.:pnInspiron3537*
+ EVDEV_ABS_00=1268:5675:41
+ EVDEV_ABS_01=1101:4792:61
+ EVDEV_ABS_35=1268:5675:41
+ EVDEV_ABS_36=1101:4792:61
+
+# Dell Inspiron 3537 - RMI4
+evdev:name:Synaptics TM2382-001:dmi:*svnDellInc.:pnInspiron3537*
+ EVDEV_ABS_00=::24
+ EVDEV_ABS_01=::34
+ EVDEV_

Re: [blfs-dev] [lfs-dev] systemd-238

[Thanos Baloukas]

On 30/03/2018 12:09 πμ, Thanos Baloukas wrote:

On 29/03/2018 07:56 μμ, Bruce Dubbs wrote:

On 03/29/2018 01:02 AM, William Harrington wrote:

On Sat, 24 Mar 2018 10:52:18 -0500
Bruce Dubbs <bruce.du...@gmail.com> wrote:
...



I'm  on it, I'll start a jhalfs automated build soon and made the 
necessary

changes to packages.ent

in LFS-svn sources to use systemd 238 instead of 237.

Base Linux in front of the chroot is debian 9.4 at the moment 
(I've been

itchy to replace it with

LFS+BLFS for a long time already).

Alain


Looks like there's a bit of a mess with the headers; there's an 
issue open. A
commit was made yesterday to "make it more robust," but in the 
meantime,

there's a patch available in the issue that is reported to work:

https://github.com/systemd/systemd/issues/8507


I just had an issue where I was going to upgrade from 236 to 237 
and I had upgraded libgpg-error from 1.27 to 1.28  I had to go back 
to 1.27 for 236 and 237 to build. I'm going to test 238 and see 
what happens.


with libgpg-error 1.27 both Systemd 236, 237 and 238 build fine. 
It's libgpg-error 1.28 when the issue surfaces.


https://hastebin.com/irotixezin.cs


Thanks for the report.  It's not an issue in LFS since we don't have
libgpg-error error there, but we will need to address it for BLFS.

Will this sed fix it?

sed -i '422,423d' src/basic/macro.h

    -- Bruce


Hello Bruce,

No, it does not.

Can any one confirm when building Systemd with gcrypt and libgcrypt 
1.28 that they need to revert to 1.27?


I've had to revert to libgcrypt 1.27 in all instances of testing. I 
suspect in the Systemd BLFS book when people use Gcrypt with Systemd 
and libgcrypt 1.28 they will need to revert to libgcrypt 1.27. It's 
always successful with libgcrypt 1.27 and no 1.28.



libgcrypt or libgpg-error?  I note that libgcrypt-1.8.2 does currently 
require libgpg-error-1.28.



On current blfs-svn with libgpg-error-1.28 and libgcrypt-1.8.2
systemd-238 failed and I had to add -Dgcrypt=false to meson options
to build, install and test. I confirm that reverting to
libgpg-error-1.27 it builds. I did not install this build though.


Following up reinstalled libgpg-error-1.28, made a diff on
systemd-238 and commit c58ab03f64890e7db88745a843bd4520e307099b
which Arch Linux is currently using, rebuilt with the patch in chroot
and booted. So far so good. Nothing strange in the logs.
If someone wants to test, commands used:

sed '171,$ d' -i src/resolve/meson.build
sed -i '527,565 d'  src/basic/missing.h
sed -i '24 d'   src/core/load-fragment.c
sed -i '53 a#include ' src/shared/bus-unit-util.c
patch -Np1 -i ${SRC_DIR}/systemd-238-upstream_fixes.patch
sed -i 's/GROUP="render", //' rules/50-udev-default.rules.in

meson --prefix=/usr   \
  --sysconfdir=/etc   \
  --localstatedir=/var\
  -Dblkid=true\
  -Dbuildtype=release \
  -Ddefault-dnssec=no \
  -Dfirstboot=false   \
  -Dinstall-tests=false   \
  -Dldconfig=false\
  -Drootprefix=   \
  -Drootlibdir=/lib   \
  -Dsplit-usr=true\
  -Dsysusers=false\
  -Db_lto=false   \
  $PWD build

cd build
ninja -v
DESTDIR=${fakeroot} ninja install
rm -rf ${fakeroot}/usr/lib/rpm

Pam config the same as in the blfs-svn book for systemd-237
Patch attached.

--
Thanos
diff -Naur systemd-238/hwdb/60-evdev.hwdb systemd-stable-c58ab03f64890e7db88745a843bd4520e307099b/hwdb/60-evdev.hwdb
--- systemd-238/hwdb/60-evdev.hwdb	2018-03-06 00:16:37.0 +0200
+++ systemd-stable-c58ab03f64890e7db88745a843bd4520e307099b/hwdb/60-evdev.hwdb	2018-03-22 12:50:37.0 +0200
@@ -114,8 +114,10 @@
  EVDEV_ABS_35=::18
  EVDEV_ABS_36=::16
 
-# Asus X550CC and S550CB
-evdev:name:ETPS/2 Elantech Touchpad:dmi:*:svnASUSTeKCOMPUTERINC.:pn?550C?:*
+# Asus X550CC, S550CB and N550JV
+evdev:name:ETPS/2 Elantech Touchpad:dmi:*:svnASUSTeKCOMPUTERINC.:pnX550CC:*
+evdev:name:ETPS/2 Elantech Touchpad:dmi:*:svnASUSTeKCOMPUTERINC.:pnS550CB:*
+evdev:name:ETPS/2 Elantech Touchpad:dmi:*:svnASUSTeKCOMPUTERINC.:pnN550JV:*
  EVDEV_ABS_00=::31
  EVDEV_ABS_01=::30
  EVDEV_ABS_35=::31
@@ -144,6 +146,20 @@
  EVDEV_ABS_00=::14
  EVDEV_ABS_01=::18
 
+# Dell Inspiron 3537 - PS/2
+evdev:name:SynPS/2 Synaptics TouchPad:dmi:*svnDellInc.:pnInspiron3537*
+ EVDEV_ABS_00=1268:5675:41
+ EVDEV_ABS_01=1101:4792:61
+ EVDEV_ABS_35=1268:5675:41
+ EVDEV_ABS_36=1101:4792:61
+
+# Dell Inspiron 3537 - RMI4
+evdev:name:Synaptics TM2382-001:dmi:*svnDellInc.:pnInspiron3537*
+ EVDEV_ABS_00=::24
+ EVDEV_ABS_01=::34
+ EVDEV_ABS_35=::24
+ EVDEV_ABS_36=::34
+
 # Dell Inspiron N5040
 evdev:name:AlpsPS/2 ALPS DualPoint TouchPad:dmi:bvn*:bvr*:bd*:svnDellInc.:pnInspironN5040*
  EVDEV_ABS_00=25:2000:22
@@ -241,6 +257,13 @@
  EVDEV_ABS_35=1068:5805:44
  EVDEV_ABS_36=1197:4

Re: [blfs-dev] [lfs-dev] systemd-238

[Thanos Baloukas]

On 29/03/2018 07:56 μμ, Bruce Dubbs wrote:

On 03/29/2018 01:02 AM, William Harrington wrote:

On Sat, 24 Mar 2018 10:52:18 -0500
Bruce Dubbs  wrote:
...



I'm  on it, I'll start a jhalfs automated build soon and made the 
necessary

changes to packages.ent

in LFS-svn sources to use systemd 238 instead of 237.

Base Linux in front of the chroot is debian 9.4 at the moment 
(I've been

itchy to replace it with

LFS+BLFS for a long time already).

Alain


Looks like there's a bit of a mess with the headers; there's an 
issue open. A
commit was made yesterday to "make it more robust," but in the 
meantime,

there's a patch available in the issue that is reported to work:

https://github.com/systemd/systemd/issues/8507


I just had an issue where I was going to upgrade from 236 to 237 and 
I had upgraded libgpg-error from 1.27 to 1.28  I had to go back to 
1.27 for 236 and 237 to build. I'm going to test 238 and see what 
happens.


with libgpg-error 1.27 both Systemd 236, 237 and 238 build fine. 
It's libgpg-error 1.28 when the issue surfaces.


https://hastebin.com/irotixezin.cs


Thanks for the report.  It's not an issue in LFS since we don't have
libgpg-error error there, but we will need to address it for BLFS.

Will this sed fix it?

sed -i '422,423d' src/basic/macro.h

    -- Bruce


Hello Bruce,

No, it does not.

Can any one confirm when building Systemd with gcrypt and libgcrypt 
1.28 that they need to revert to 1.27?


I've had to revert to libgcrypt 1.27 in all instances of testing. I 
suspect in the Systemd BLFS book when people use Gcrypt with Systemd 
and libgcrypt 1.28 they will need to revert to libgcrypt 1.27. It's 
always successful with libgcrypt 1.27 and no 1.28.



libgcrypt or libgpg-error?  I note that libgcrypt-1.8.2 does currently 
require libgpg-error-1.28.



On current blfs-svn with libgpg-error-1.28 and libgcrypt-1.8.2
systemd-238 failed and I had to add -Dgcrypt=false to meson options
to build, install and test. I confirm that reverting to
libgpg-error-1.27 it builds. I did not install this build though.

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

[blfs-dev] autofs-5.1.4 required dep rpcsvc-proto-1.3.1 missing

[Thanos Baloukas]

Missing from the stable and dev books.
You can go there through the dep-chain
autofs -> optional nfs-utils -> optional libnsl -> required rpcsvc-proto
but I think that this is not in compliance with the books policy.

With the book's options configure fails with

checking for rpcgen... no
configure: error: required program RPCGEN not found

Also it installed a broken symlink
$DESTDIR/usr/lib/autofs/lookup_nis.so --> lookup_yp.so

I started the service, plugged a usb stick and it worked.

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

[blfs-dev] ntfs-3g-2017.3.23 optional dependency on fuse2

[Thanos Baloukas]

On
http://www.linuxfromscratch.org/blfs/view/systemd/postlfs/ntfs-3g.html
the 'fuse 2.x' link is external, while fuse2 is in the book.

sed -i '/fuse 2.x/c\  '   \
postlfs/filesystems/ntfs-3g.xml

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

Re: [blfs-dev] Pango-1.40.14 fails on pango-view.1 generation

[Thanos Baloukas]

On 02/22/2018 10:05 PM, Bruce Dubbs wrote:

Thanos Baloukas wrote:

If the help2man perl script by lsb_release-1.4 is installed in /usr/bin
according the book instructions, the build fails with

[125/127] Generating pango-view.1 with a custom command.
FAILED: pango-view/pango-view.1
/usr/bin/help2man --no-info --section=1 '--help-option="--help-all"' 
'--name="Pango text viewer"' --output=pango-view/pango-view.1 
/tmp/pango-1.40.14/build/pango-view/pango-view

Unknown option: help-option
`help2man' generates a man page out of `--help' and `--version' output.

Usage: help2man [OPTION]... EXECUTABLE

  -n, --name=STRING use `STRING' as the description for the 
NAME paragraph

  -s, --section=SECTION use `SECTION' as the section for the man page
  -i, --include=FILE    include material from `FILE'
  -I, --opt-include=FILE    include material from `FILE' if it exists
  -o, --output=FILE send output to `FILE'
  -N, --no-info suppress pointer to Texinfo manual
  --alt_version_key=KEY use specified flag instead of --version
  --help    print this help, then exit
  --version print version number, then exit

EXECUTABLE should accept `--help' and `--version' options.

The lsb_release-1.4 help2man does not accept the --help-option. With
sed '/--help-option=/d' -i pango-view/meson.build
it builds ok.


help2man is a perl script.  The one in lsb-release is quite old.  I 
don't think it is worth adding a whole page for installing it, but we 
could add an additional download to lsb-release with a newer version.


http://anduin.linuxfromscratch.org/BLFS/help2man


Having a new help2man version in the book sounds good. I'm not sure
if the lsb-release page is the most appropriate place to place the
download link.

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

[blfs-dev] Pango-1.40.14 fails on pango-view.1 generation

[Thanos Baloukas]

If the help2man perl script by lsb_release-1.4 is installed in /usr/bin
according the book instructions, the build fails with

[125/127] Generating pango-view.1 with a custom command.
FAILED: pango-view/pango-view.1
/usr/bin/help2man --no-info --section=1 '--help-option="--help-all"' 
'--name="Pango text viewer"' --output=pango-view/pango-view.1 
/tmp/pango-1.40.14/build/pango-view/pango-view

Unknown option: help-option
`help2man' generates a man page out of `--help' and `--version' output.

Usage: help2man [OPTION]... EXECUTABLE

 -n, --name=STRING use `STRING' as the description for the NAME 
paragraph

 -s, --section=SECTION use `SECTION' as the section for the man page
 -i, --include=FILEinclude material from `FILE'
 -I, --opt-include=FILEinclude material from `FILE' if it exists
 -o, --output=FILE send output to `FILE'
 -N, --no-info suppress pointer to Texinfo manual
 --alt_version_key=KEY use specified flag instead of --version
 --helpprint this help, then exit
 --version print version number, then exit

EXECUTABLE should accept `--help' and `--version' options.

The lsb_release-1.4 help2man does not accept the --help-option. With
sed '/--help-option=/d' -i pango-view/meson.build
it builds ok.

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

[blfs-dev] systemd-237-dependencies.patch

[Thanos Baloukas]

Also on LLVM-5.0.1 Command Explanations has
-DLLVM_ENABLE_FFI=ON: This switch enables LLVM to use libffi. Remove if 
you did not install libffi.


The 'Remove if you did not install libffi.' has to go or become
'Remove if this is not desired.'

--
Thanos
Index: general/sysutils/systemd.xml
===
--- general/sysutils/systemd.xml	(revision 19801)
+++ general/sysutils/systemd.xml	(working copy)
@@ -84,9 +84,11 @@
   ,
   ,
   ,
-  ,
+   or 
+  (If both are installed, defaults to using libidn),
   ,
   ,
+  ,
   ,
   ,
(for the zsh completions),
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-dev] JS-38.2.1 alternative headers' installation fix

[Thanos Baloukas]

The fix can be done with
sed -i '/dist_include.*add_symlink/s/add_symlink/add_copy/'  \
python/mozbuild/mozbuild/backend/recursivemake.py

https://git.archlinux.org/svntogit/packages.git/tree/trunk/mozjs38-copy-headers.patch?h=packages/js38

Tested in chroot with destdir. The chown -Rv root.root was not needed
with the sed. On both installations (with the book's instructions and
the sed) $DESTDIR/usr/include/mozjs-38/js-config.h had mode 755
so a chmod 644 is needed.

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

Re: [blfs-dev] network manager applet question

[Thanos Baloukas]

On 21/08/2015 08:41 πμ, hykw...@sina.com wrote:

After the Network manager applet is built successfully, I find that some images 
are missing for some buttons.
So, what icon theme should I install to fix it?
Thanks.

H.Y. Kwok

P.S. Please update the BLFS (Systemd edition) version for the Network manager 
and Network manager applet to 1.0.4


Wrong list. This should be sent to blfs-support.
Which desktop are you using? On xfce the Network manager applet icon
is in the panel's notification area. Do you have notification area
enabled on your panel?

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

Re: [blfs-dev] Multimedia cdrom/dvd woes

[Thanos Baloukas]

On 10/03/2015 06:43 μμ, Bruce Dubbs wrote:

Thanos Baloukas wrote:

On 10/03/2015 06:18 μμ, Armin K. wrote:


Use this patch:

https://projects.archlinux.org/svntogit/packages.git/tree/trunk/cdio-includes.patch?h=packages/mplayer




Or a sed (untested)

sed -i 's:/paranoia.h:/paranoia:g;s:/cdda.h:/paranoia:g' configure
stream/stream_cdda.c



I used this patch to build MPlayer-2014-12-19
http://www.linuxfromscratch.org/blfs/view/systemd/multimedia/mplayer.html
with libcdio-0.93 libcdio-paranoia-10.2-0.93-1
It pauses when it plays music CDs. Does it work for you?


Yes, it did work for me.

ldd `which mplayer`|grep libcd
 libcdio_cdda.so.2 = /usr/lib64/libcdio_cdda.so.2
(0x7f7d93bbe000)
 libcdio.so.16 = /usr/lib64/libcdio.so.16 (0x7f7d93996000)
 libcdio_paranoia.so.2 = /usr/lib64/libcdio_paranoia.so.2


   -- Bruce



You mean that except that it linked as it should, it also
stopped pausing when playing CDs?
I guess your mplayer is 2015-02-20, is that right?

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

Re: [blfs-dev] Multimedia cdrom/dvd woes

[Thanos Baloukas]

On 10/03/2015 06:18 μμ, Armin K. wrote:


Use this patch:

https://projects.archlinux.org/svntogit/packages.git/tree/trunk/cdio-includes.patch?h=packages/mplayer


Or a sed (untested)

sed -i 's:/paranoia.h:/paranoia:g;s:/cdda.h:/paranoia:g' configure
stream/stream_cdda.c



I used this patch to build MPlayer-2014-12-19
http://www.linuxfromscratch.org/blfs/view/systemd/multimedia/mplayer.html
with libcdio-0.93 libcdio-paranoia-10.2-0.93-1
It pauses when it plays music CDs. Does it work for you?

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

Re: [blfs-dev] Multimedia cdrom/dvd woes

[Thanos Baloukas]

On 10/03/2015 11:25 μμ, Bruce Dubbs wrote:

Thanos Baloukas wrote:


You mean that except that it linked as it should, it also
stopped pausing when playing CDs?
I guess your mplayer is 2015-02-20, is that right?


Yes, I used mplayer 2015-02-20 and yes, it is not pausing any more.  It
is working properly.

   -- Bruce


Thanks, I'll install that version too, on my current lfs-7.7 build.

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