Re: [blfs-dev] gpgme
Ken Moffat wrote: On Thu, Feb 22, 2018 at 01:18:02AM +, Ken Moffat wrote: On Wed, Feb 21, 2018 at 06:04:54PM -0600, Bruce Dubbs wrote: I tried to build gpgme with gnupg and just couldn't make it work. I tried using --disable-gpg-test and several other --disable options, but it kept failing during the make phase because gnupg programs were not present. I gave up and installed gnupg and then everything was OK. I recommend making gnupg required for gpgme but will wait for feedback. -- Bruce See the thread on blfs-support. Spiky reported the problem, and eventually built gnupg. Pierre noted the test programs are always built and offered a --disable suggestion. I don't have any use for gpgme, so I've not tried to build it. And all cores of my current machine are in use, so I can't try building it at the moment. Pierre fixed it in r19805! My build completed, so I built it (without gnupg) and now confirm that it built for me using --disable-gpg-test. Hmm. I use a script that does: ./configure --prefix=/usr --disable-gpg-test make In the log is: Making all in tests ... gpgconf --kill all echo "ignore-invalid-option allow-loopback-pinentry" > /tmp/gpgme/gpgme-1.10.0/lang/qt/tests/gpg-agent.conf echo "allow-loopback-pinentry" >> gpg-agent.conf echo "ignore-invalid-option pinentry-mode" > gpg.conf echo "pinentry-mode loopback" >> gpg.conf gpg --no-permission-warning \ --import ../../../tests/gpg/pubdemo.asc Without gpg, this last line causes make to stop with an error. I tried the above with --disable-gpgconf-test --disable-gpgsm-test --disable-g13-test and it still failed for me at the same place. Investigating, it appears that the above is in lang/qt/tests/Makefile and is not disabled with any of the configure options. Note that I have Qt5 and pinentry installed. It seems that with some sets of dependencies that gpg is required. Investigating, it appears that the above is in lang/qt/tests/Makefile and is not disabled with any of the configure options. I suppose I can avoid it with: sed -i '/^SUBDIRS/s/tests//' lang/qt/Makefile.in but do we want to do that? "If no gnupg but have qt then ..." Note: Tested with the sed (and --disable-gpg-test) and there is no ^gpg in the log. -- 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] Tagging status
Bruce Dubbs wrote: Bruce Dubbs wrote: We are doing very well for the first weekend after package freeze: lfs81 tags remaining: 518 lfs82 tags : 274 Tickets targeted for 8.2: 34 === As of Tue Feb 20 05:46:29 UTC 2018 lfs81 tags remaining: 457 lfs82 tags : 335 Tickets targeted for 8.2: 20 I have a bunch of multimedia packages ready (~45) to tag, but not tonight. === As of Thu Feb 22 05:07:06 UTC 2018 lfs81 tags remaining: 272 lfs82 tags : 521 Tickets targeted for 8.2: 16 I tried to get the feh and mercurial tickets done today but am still trying to straighten out some issues. Some of these packages require a LOT of dependencies and have substantial circular dependencies if trying to build all the optional deps. -- 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] gpgme
On Thu, Feb 22, 2018 at 01:18:02AM +, Ken Moffat wrote: > On Wed, Feb 21, 2018 at 06:04:54PM -0600, Bruce Dubbs wrote: > > I tried to build gpgme with gnupg and just couldn't make it work. I tried > > using --disable-gpg-test and several other --disable options, but it kept > > failing during the make phase because gnupg programs were not present. > > > > I gave up and installed gnupg and then everything was OK. > > > > I recommend making gnupg required for gpgme but will wait for feedback. > > > > -- Bruce > See the thread on blfs-support. Spiky reported the problem, and > eventually built gnupg. Pierre noted the test programs are always > built and offered a --disable suggestion. > > I don't have any use for gpgme, so I've not tried to build it. > And all cores of my current machine are in use, so I can't try > building it at the moment. > Pierre fixed it in r19805! My build completed, so I built it (without gnupg) and now confirm that it built for me using --disable-gpg-test. ĸen -- Truth, in front of her huge walk-in wardrobe, selected black leather boots with stiletto heels for such a barefaced truth. - Unseen Academicals -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] 回复：Re: Suggestions for BLFS
>Pierre Labastie wrote:
>> On 20/02/2018 19:39, Bruce Dubbs wrote:
>>> Pierre Labastie wrote:
On 20/02/2018 12:47, Pierre Labastie wrote:
> On 31/01/2018 10:24, hykw...@sina.com wrote:
>> Version: systemd edition - Version 2018-01-30
>>[...]
>> - EXO is required if Xfwm is present. (Please note that we can build Xfwm
>> without EXO package while we can use Xfwm with lxqt)
>>
>
> Actually, there is an advice at the beginning of the Xfce Desktop chapter:
> "Build Xfce core packages in the order presented in the book for the
> easiest
> resolution of dependencies."
> And EXO is presented before xfwm in this chapter.
>
Actually, it is lightdm-gtk-greeter, which requires EXO (exactly,
"configure"
tests for exo-csource and errors out if not found). But actually,
exo-csource
is only needed in maintainer mode, which is disabled by default. So
configure
can be fooled with "HAVE_EXO_CSOURCE=yes ./configure ...". NB: CFLAGS
should
include -Wno-error=deprecated-declarations.
> Same for itstool in lightdm. It is not used during a normal build, only
> tested
by configure. configure can be fooled with "ITSTOOL=/bin/true ./configure
..."
To finish with lightdm, there is a PATH problem: if the DE is installed in
/opt, (with .desktop file in /usr), it seems the PATH is not set correctly,
and login fails. I guess "source /etc/profile" should be added somewhere...
Not found yet
>>>
>>> In /etc/lightdm/Xsession, I have:
>>>
>>>
>>> echo "Running X session wrapper"
>>>
>>> # Load profile
>>> for file in "/etc/profile" "$HOME/.bash_profile"; do
>>> if [ -f "$file" ]; then
>>> echo "Loading profile from $file";
>>> . "$file"
>>> fi
>>> done
>>>
>>> I am not sure where I figured out the Xsession. It is not installed by
>>> default. I am attaching what I have.
>>>
>>>-- Bruce
>>
>> I found that adding a line ". /etc/profile" in /usr/bin/lightdm-session is
>> enough, at least for starting LXQt.
>>
>> I suggest to propose that in the book. There are two ways to do that:
>> a sed (but it looks ugly), or a full cat. I'll commit the sed (because I've
>> tested it), but feel free to modify.
>I'll test it but I did make some minor changes. Thanks for the fixes.
> -- Bruce
Just to share my experience:
System: BLFS (Systemd version)
QT5 installed path: /opt/qt5
LXQT installed path: /opt/lxqt
1. Fix the missing file "lxqt.desktop"
In my case, I cannot execute the instruction "cp -v
{$LXQT_PREFIX,/usr}/share/xsessions/lxqt.desktop" sucessfully because the
target directory is missing. So, I have to execute the following commands (as
root):
mkdir -p /usr/share/xessions
cp -v {$LXQT_PREFIX,/usr}/share/xsessions/lxqt.desktop
I have to make usre lxqt.desktop should be located in /usr/share/xessions
because "lightdm" will use it for session creation.
2. Modify lxqt.desktop
Since the intallation path of LXQT is "/opt" rather than "/usr", I have to
modify lxqt.destop so that "lightdm" can find the command:
"Exec=startlxqt" --> "Exec=/opt/lxqt/bin/startlxqt"
3. Modify "startlxqt"
3.1 After the function "contains", add the following line in order to setup the
environment variables (I guess we can skip it if the installation path is
"/usr"):
source /etc/profile
3.2 Before the line "exec lxqt-session", add the following lines:
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
[ -x "$f" ] && . "$f"
done
unset f
fi
killall kscreen_backend_launcher
/opt/lxqt/lib/libexec/kf5/kscreen_backend_launcher &
For the fist part, please read this reference for more information.
(https://github.com/lxde/lxqt/wiki/ConfigLaunch)
For the second part, it try to fix the starting problem of
"lxqt-config-monitor".
In my case, although "kscreen_backend_launcher" is started sucessfully and I
can find the realted D-Bus setting by a Python script
(https://unix.stackexchange.com/questions/46301/a-list-of-available-dbus-services),
"lxqt-config-monitor" cannot connect to "KScreen". I have no idea about the
cause but I find that I can restart "kscreen_backend_launcher" to fix this
problem.
Then, I can start lightdm for testing: systemctl start lightdm
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: [blfs-dev] gpgme
Ken Moffat wrote: On Wed, Feb 21, 2018 at 06:04:54PM -0600, Bruce Dubbs wrote: I tried to build gpgme with gnupg and just couldn't make it work. I tried using --disable-gpg-test and several other --disable options, but it kept failing during the make phase because gnupg programs were not present. I gave up and installed gnupg and then everything was OK. I recommend making gnupg required for gpgme but will wait for feedback. See the thread on blfs-support. Spiky reported the problem, and eventually built gnupg. Pierre noted the test programs are always built and offered a --disable suggestion. Right. The --disable is now in the book. The problem is that it didn't work for me. -- 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] gpgme
On Wed, Feb 21, 2018 at 06:04:54PM -0600, Bruce Dubbs wrote: > I tried to build gpgme with gnupg and just couldn't make it work. I tried > using --disable-gpg-test and several other --disable options, but it kept > failing during the make phase because gnupg programs were not present. > > I gave up and installed gnupg and then everything was OK. > > I recommend making gnupg required for gpgme but will wait for feedback. > > -- Bruce See the thread on blfs-support. Spiky reported the problem, and eventually built gnupg. Pierre noted the test programs are always built and offered a --disable suggestion. I don't have any use for gpgme, so I've not tried to build it. And all cores of my current machine are in use, so I can't try building it at the moment. ĸen -- Truth, in front of her huge walk-in wardrobe, selected black leather boots with stiletto heels for such a barefaced truth. - Unseen Academicals -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] gpgme
I tried to build gpgme with gnupg and just couldn't make it work. I tried using --disable-gpg-test and several other --disable options, but it kept failing during the make phase because gnupg programs were not present. I gave up and installed gnupg and then everything was OK. I recommend making gnupg required for gpgme but will wait for feedback. -- 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] Suggestions for BLFS
Pierre Labastie wrote: On 20/02/2018 19:39, Bruce Dubbs wrote: Pierre Labastie wrote: On 20/02/2018 12:47, Pierre Labastie wrote: On 31/01/2018 10:24, hykw...@sina.com wrote: Version: systemd edition - Version 2018-01-30 [...] - EXO is required if Xfwm is present. (Please note that we can build Xfwm without EXO package while we can use Xfwm with lxqt) Actually, there is an advice at the beginning of the Xfce Desktop chapter: "Build Xfce core packages in the order presented in the book for the easiest resolution of dependencies." And EXO is presented before xfwm in this chapter. Actually, it is lightdm-gtk-greeter, which requires EXO (exactly, "configure" tests for exo-csource and errors out if not found). But actually, exo-csource is only needed in maintainer mode, which is disabled by default. So configure can be fooled with "HAVE_EXO_CSOURCE=yes ./configure ...". NB: CFLAGS should include -Wno-error=deprecated-declarations. Same for itstool in lightdm. It is not used during a normal build, only tested by configure. configure can be fooled with "ITSTOOL=/bin/true ./configure ..." To finish with lightdm, there is a PATH problem: if the DE is installed in /opt, (with .desktop file in /usr), it seems the PATH is not set correctly, and login fails. I guess "source /etc/profile" should be added somewhere... Not found yet In /etc/lightdm/Xsession, I have: echo "Running X session wrapper" # Load profile for file in "/etc/profile" "$HOME/.bash_profile"; do if [ -f "$file" ]; then echo "Loading profile from $file"; . "$file" fi done I am not sure where I figured out the Xsession. It is not installed by default. I am attaching what I have. -- Bruce I found that adding a line ". /etc/profile" in /usr/bin/lightdm-session is enough, at least for starting LXQt. I suggest to propose that in the book. There are two ways to do that: a sed (but it looks ugly), or a full cat. I'll commit the sed (because I've tested it), but feel free to modify. I'll test it but I did make some minor changes. Thanks for the fixes. -- 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] Suggestions for BLFS
On 20/02/2018 19:39, Bruce Dubbs wrote: > Pierre Labastie wrote: >> On 20/02/2018 12:47, Pierre Labastie wrote: >>> On 31/01/2018 10:24, hykw...@sina.com wrote: Version: systemd edition - Version 2018-01-30 [...] - EXO is required if Xfwm is present. (Please note that we can build Xfwm without EXO package while we can use Xfwm with lxqt) >>> >>> Actually, there is an advice at the beginning of the Xfce Desktop chapter: >>> "Build Xfce core packages in the order presented in the book for the easiest >>> resolution of dependencies." >>> And EXO is presented before xfwm in this chapter. >>> >> >> Actually, it is lightdm-gtk-greeter, which requires EXO (exactly, "configure" >> tests for exo-csource and errors out if not found). But actually, exo-csource >> is only needed in maintainer mode, which is disabled by default. So configure >> can be fooled with "HAVE_EXO_CSOURCE=yes ./configure ...". NB: CFLAGS should >> include -Wno-error=deprecated-declarations. >> >> Same for itstool in lightdm. It is not used during a normal build, only >> tested >> by configure. configure can be fooled with "ITSTOOL=/bin/true ./configure >> ..." >> >> To finish with lightdm, there is a PATH problem: if the DE is installed in >> /opt, (with .desktop file in /usr), it seems the PATH is not set correctly, >> and login fails. I guess "source /etc/profile" should be added somewhere... >> Not found yet > > In /etc/lightdm/Xsession, I have: > > > echo "Running X session wrapper" > > # Load profile > for file in "/etc/profile" "$HOME/.bash_profile"; do > if [ -f "$file" ]; then > echo "Loading profile from $file"; > . "$file" > fi > done > > I am not sure where I figured out the Xsession. It is not installed by > default. I am attaching what I have. > > -- Bruce I found that adding a line ". /etc/profile" in /usr/bin/lightdm-session is enough, at least for starting LXQt. I suggest to propose that in the book. There are two ways to do that: a sed (but it looks ugly), or a full cat. I'll commit the sed (because I've tested it), but feel free to modify. Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
