[blfs-dev] wacom
I rebuilt my whole system using the latest SVN of LFS and BLFS, and xsetwacom still doesn't see my devices (ever since LFS 9.0). In my pre-9.0 system with all packages upgraded to the latest versions: roger [ ~ ]$ xsetwacom --list devices Serial Wacom Tablet WACf004 stylus id: 12 type: STYLUS Serial Wacom Tablet WACf004 eraser id: 13 type: ERASER After 9.0, there is no output from this command. So, I can't move on past 9.0 the way things currently are, and I don't have a lot of time to debug. Hopefully, one of your more Linux-savvy list members will be able to identify the problem. LFS/BLFS/ALFS is still my favorite way of creating a Linux desktop to order. Thanks, Roger -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] epiphany
I just tried epiphany for the first time today. It looks like it can't play html5 videos. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] gnome-calculator
meson.build:28:0: ERROR: Dependency "gee-0.8" not found, tried pkgconfig and cmake -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Curl
On Fri, Sep 13, 2019 at 5:01 PM Roger Koehler wrote: > > The latest Firefox browser doesn't seem to like the latest Curl update. It > keeps telling me to restart my tab. Must have been something else. Not seeing the problem this morning. Sorry for the noise. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] Curl
The latest Firefox browser doesn't seem to like the latest Curl update. It keeps telling me to restart my tab. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] graphviz fails to build
swig -c++ -ocaml -o gv_ocaml.cpp ./gv.i
SWIG:1: Warning 524: Experimental target language. Target language OCaml
specified by -ocaml is an experimental language. Please read about SWIG
experimental languages,
http://swig.org/Doc4.0/Introduction.html#Introduction_experimental_status.
mv gv_ocaml.cpp gv_ocaml.cpp.orig
sed '/int caml_array_length/d' gv_ocaml.cpp.orig > gv_ocaml.cpp
rm gv_ocaml.cpp.orig
CXX libgv_ocaml_la-gv_ocaml.lo
gv_ocaml.cpp: In function 'long int caml_long_val_full(caml_value_t, const
char*)':
gv_ocaml.cpp:1362:48: error: invalid conversion from 'const caml_value_t*'
{aka 'const long int*'} to 'caml_value_t*' {aka 'long int*'} [-fpermissive]
1362 | CAML_VALUE *enum_to_int = caml_named_value(SWIG_MODULE
"_enum_to_int");
|
^~~~
||
|const caml_value_t*
{aka const long int*}
gv_ocaml.cpp: In function 'int caml_ptr_val_internal(caml_value_t, void**,
swig_type_info*)':
gv_ocaml.cpp:1416:37: error: invalid conversion from 'const caml_value_t*'
{aka 'const long int*'} to 'caml_value_t*' {aka 'long int*'} [-fpermissive]
1416 | func_val = caml_named_value("caml_obj_ptr");
| ^~~~
| |
| const caml_value_t* {aka const
long int*}
gv_ocaml.cpp: In function 'caml_value_t SWIG_Ocaml_ptr_to_val(const char*,
void*, swig_type_info*)':
gv_ocaml.cpp:1529:47: error: invalid conversion from 'const caml_value_t*'
{aka 'const long int*'} to 'caml_value_t*' {aka 'long int*'} [-fpermissive]
1529 | CAML_VALUE *fromval = caml_named_value(name);
| ^~
| |
| const caml_value_t*
{aka const long int*}
make[4]: *** [Makefile:2227: libgv_ocaml_la-gv_ocaml.lo] Error 1
make[4]: Leaving directory
'/var/lib/sources/graphviz/graphviz-2.42.1/tclpkg/gv'
make[3]: *** [Makefile:2758: all-recursive] Error 1
make[3]: Leaving directory
'/var/lib/sources/graphviz/graphviz-2.42.1/tclpkg/gv'
make[2]: *** [Makefile:646: all-recursive] Error 1
make[2]: Leaving directory
'/var/lib/sources/graphviz/graphviz-2.42.1/tclpkg'
make[1]: *** [Makefile:825: all-recursive] Error 1
make[1]: Leaving directory '/var/lib/sources/graphviz/graphviz-2.42.1'
make: *** [Makefile:633: all] Error 2
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
[blfs-dev] cups-filters fails to build
See attached log file. CC bannertopdf-bannertopdf.o filter/bannertopdf.c: In function ‘get_pagesize’: filter/bannertopdf.c:89:5: warning: ‘ppdPageSize’ is deprecated: Use cupsCopyDestInfo and friends instead. [-Wdeprecated-declarations] 89 | if (!ppd || !(pagesize = ppdPageSize(ppd, NULL))) | ^~ In file included from filter/bannertopdf.c:32: /usr/include/cups/ppd.h:392:20: note: declared here 392 | extern ppd_size_t *ppdPageSize(ppd_file_t *ppd, const char *name) |^~~ filter/bannertopdf.c: In function ‘duplex_marked’: filter/bannertopdf.c:157:8: warning: ‘ppdIsMarked’ is deprecated: Use cupsCopyDestInfo and friends instead. [-Wdeprecated-declarations] 157 |(ppdIsMarked(ppd, "Duplex", "DuplexNoTumble") || |^ In file included from filter/bannertopdf.c:32: /usr/include/cups/ppd.h:382:13: note: declared here 382 | extern int ppdIsMarked(ppd_file_t *ppd, const char *keyword, | ^~~ filter/bannertopdf.c:158:9: warning: ‘ppdIsMarked’ is deprecated: Use cupsCopyDestInfo and friends instead. [-Wdeprecated-declarations] 158 | ppdIsMarked(ppd, "Duplex", "DuplexTumble") || | ^~~ In file included from filter/bannertopdf.c:32: /usr/include/cups/ppd.h:382:13: note: declared here 382 | extern int ppdIsMarked(ppd_file_t *ppd, const char *keyword, | ^~~ filter/bannertopdf.c:159:9: warning: ‘ppdIsMarked’ is deprecated: Use cupsCopyDestInfo and friends instead. [-Wdeprecated-declarations] 159 | ppdIsMarked(ppd, "JCLDuplex", "DuplexNoTumble") || | ^~~ In file included from filter/bannertopdf.c:32: /usr/include/cups/ppd.h:382:13: note: declared here 382 | extern int ppdIsMarked(ppd_file_t *ppd, const char *keyword, | ^~~ filter/bannertopdf.c:160:9: warning: ‘ppdIsMarked’ is deprecated: Use cupsCopyDestInfo and friends instead. [-Wdeprecated-declarations] 160 | ppdIsMarked(ppd, "JCLDuplex", "DuplexTumble") || | ^~~ In file included from filter/bannertopdf.c:32: /usr/include/cups/ppd.h:382:13: note: declared here 382 | extern int ppdIsMarked(ppd_file_t *ppd, const char *keyword, | ^~~ filter/bannertopdf.c:161:9: warning: ‘ppdIsMarked’ is deprecated: Use cupsCopyDestInfo and friends instead. [-Wdeprecated-declarations] 161 | ppdIsMarked(ppd, "EFDuplex", "DuplexNoTumble") || | ^~~ In file included from filter/bannertopdf.c:32: /usr/include/cups/ppd.h:382:13: note: declared here 382 | extern int ppdIsMarked(ppd_file_t *ppd, const char *keyword, | ^~~ filter/bannertopdf.c:162:9: warning: ‘ppdIsMarked’ is deprecated: Use cupsCopyDestInfo and friends instead. [-Wdeprecated-declarations] 162 | ppdIsMarked(ppd, "EFDuplex", "DuplexTumble") || | ^~~ In file included from filter/bannertopdf.c:32: /usr/include/cups/ppd.h:382:13: note: declared here 382 | extern int ppdIsMarked(ppd_file_t *ppd, const char *keyword, | ^~~ filter/bannertopdf.c:163:9: warning: ‘ppdIsMarked’ is deprecated: Use cupsCopyDestInfo and friends instead. [-Wdeprecated-declarations] 163 | ppdIsMarked(ppd, "KD03Duplex", "DuplexNoTumble") || | ^~~ In file included from filter/bannertopdf.c:32: /usr/include/cups/ppd.h:382:13: note: declared here 382 | extern int ppdIsMarked(ppd_file_t *ppd, const char *keyword, | ^~~ filter/bannertopdf.c:164:9: warning: ‘ppdIsMarked’ is deprecated: Use cupsCopyDestInfo and friends instead. [-Wdeprecated-declarations] 164 | ppdIsMarked(ppd, "KD03Duplex", "DuplexTumble"))) || | ^~~ In file included from filter/bannertopdf.c:32: /usr/include/cups/ppd.h:382:13: note: declared here 382 | extern int ppdIsMarked(ppd_file_t *ppd, const char *keyword, | ^~~ filter/bannertopdf.c: In function ‘get_known_opts’: filter/bannertopdf.c:347:7: warning: ‘ppdFindAttr’ is deprecated: Use cupsCopyDestInfo and friends instead. [-Wdeprecated-declarations] 347 | (attr = ppdFindAttr(ppd, "FileVersion", NULL)) ? | ^ In file included from filter/bannertopdf.c:32: /usr/include/cups/ppd.h:399:20: note: declared here 399 | extern ppd_attr_t *ppdFindAttr(ppd_file_t *ppd, const char *name, |^~~ filter/bannertopdf.c: In function ‘generate_banner_pdf’: filter/bannertopdf.c:450:19: warning: ‘ppdFindAttr’ is deprecated: Use cupsCopyDestInfo and friends instead. [-Wdeprecated-declarations] 450 | (attr = ppdFindAttr(ppd, "FileVersion", NULL)) ? attr->value : ""); | ^ In file included from filter/bannertopdf.c:32: /usr/include/cups/ppd.h:399:20: note: declared here 399 | extern ppd_attr_t *ppdFindAttr(ppd_file_t *ppd, const char *name, |
[blfs-dev] graphviz fails to build
See attached log file.
swig -c++ -ocaml -o gv_ocaml.cpp ./gv.i
SWIG:1: Warning 524: Experimental target language. Target language OCaml specified by -ocaml is an experimental language. Please read about SWIG experimental languages, http://swig.org/Doc4.0/Introduction.html#Introduction_experimental_status.
mv gv_ocaml.cpp gv_ocaml.cpp.orig
sed '/int caml_array_length/d' gv_ocaml.cpp.orig > gv_ocaml.cpp
rm gv_ocaml.cpp.orig
CXX libgv_ocaml_la-gv_ocaml.lo
gv_ocaml.cpp: In function 'long int caml_long_val_full(caml_value_t, const char*)':
gv_ocaml.cpp:1362:48: error: invalid conversion from 'const caml_value_t*' {aka 'const long int*'} to 'caml_value_t*' {aka 'long int*'} [-fpermissive]
1362 | CAML_VALUE *enum_to_int = caml_named_value(SWIG_MODULE "_enum_to_int");
|^~~~
||
|const caml_value_t* {aka const long int*}
gv_ocaml.cpp: In function 'int caml_ptr_val_internal(caml_value_t, void**, swig_type_info*)':
gv_ocaml.cpp:1416:37: error: invalid conversion from 'const caml_value_t*' {aka 'const long int*'} to 'caml_value_t*' {aka 'long int*'} [-fpermissive]
1416 | func_val = caml_named_value("caml_obj_ptr");
| ^~~~
| |
| const caml_value_t* {aka const long int*}
gv_ocaml.cpp: In function 'caml_value_t SWIG_Ocaml_ptr_to_val(const char*, void*, swig_type_info*)':
gv_ocaml.cpp:1529:47: error: invalid conversion from 'const caml_value_t*' {aka 'const long int*'} to 'caml_value_t*' {aka 'long int*'} [-fpermissive]
1529 | CAML_VALUE *fromval = caml_named_value(name);
| ^~
| |
| const caml_value_t* {aka const long int*}
make[4]: *** [Makefile:2227: libgv_ocaml_la-gv_ocaml.lo] Error 1
make[4]: Leaving directory '/var/lib/sources/graphviz/graphviz-2.42.1/tclpkg/gv'
make[3]: *** [Makefile:2758: all-recursive] Error 1
make[3]: Leaving directory '/var/lib/sources/graphviz/graphviz-2.42.1/tclpkg/gv'
make[2]: *** [Makefile:646: all-recursive] Error 1
make[2]: Leaving directory '/var/lib/sources/graphviz/graphviz-2.42.1/tclpkg'
make[1]: *** [Makefile:825: all-recursive] Error 1
make[1]: Leaving directory '/var/lib/sources/graphviz/graphviz-2.42.1'
make: *** [Makefile:633: all] Error 2
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
[blfs-dev] libmypaint
[image: image.png] -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] wacom
On Wed, Sep 4, 2019 at 8:59 PM Ken Moffat via blfs-dev wrote: > > On Wed, Sep 04, 2019 at 06:54:31PM -0600, Roger Koehler via blfs-dev wrote: > > Any ideas why wacom doesn't work in 9.0? > > If you are using libinput, the default command there has > -Dlibwacom=false > (looking at svn, updating my scripts, but I think 9.0 was the same) Thanks Ken. I think that just allows you to pull in the system libwacom.so if you have built it. I tried this but still don't see my device. I rebuilt the kernel since I hadn't installed the modules yet, but most of my kernel settings are set to build in the core. I have a few [M] settings for internet filtering, but not many. I thought maybe I missed one. But if I boot into my old system using the same kernel it works. Curious. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] wacom
On Thu, Sep 5, 2019 at 5:21 AM Roger Koehler wrote: > > On Wed, Sep 4, 2019 at 8:59 PM Ken Moffat via blfs-dev > wrote: > > > > On Wed, Sep 04, 2019 at 06:54:31PM -0600, Roger Koehler via blfs-dev wrote: > > > Any ideas why wacom doesn't work in 9.0? > > > > If you are using libinput, the default command there has > > -Dlibwacom=false > > (looking at svn, updating my scripts, but I think 9.0 was the same) > > Thanks Ken. I think that just allows you to pull in the system > libwacom.so if you have built it. I tried this but still don't see my > device. I rebuilt the kernel since I hadn't installed the modules yet, > but most of my kernel settings are set to build in the core. I have a > few [M] settings for internet filtering, but not many. I thought maybe > I missed one. But if I boot into my old system using the same kernel > it works. Curious. Old system: roger [ /var/lib/lfs/blfs-book ]$ xsetwacom --list Serial Wacom Tablet WACf004 stylusid: 12type: STYLUS Serial Wacom Tablet WACf004 eraserid: 13type: ERASER -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] doxygen
I am currently building BLFS 9.0. It seems a lot easier this time around. Good work! I just wanted to point out that git is required to build doxygen. (jhalfs tried to build it first.) -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] What's left for the 9.0 release?
On Sat, Aug 31, 2019, 9:33 AM Xi Ruoyao via blfs-dev < blfs-dev@lists.linuxfromscratch.org> wrote: > On 2019-08-30 21:44 +0200, Pierre Labastie via blfs-dev wrote: > > On 30/08/2019 17:44, Xi Ruoyao via blfs-dev wrote: > > > On 2019-08-30 10:24 -0500, Douglas R. Reno wrote: > > > > On 2019-08-30 10:22, Xi Ruoyao via blfs-dev wrote: > > > > > On 2019-08-30 09:20 -0500, Bruce Dubbs via blfs-dev wrote: > > > > > > All packages have now been tagged and all tickets closed for the > 9.0 > > > > > > release. What other things are remaining that we need to > address > > > > > > before > > > > > > the Sunday release? > > > > > > > > > > > >-- Bruce > > > > > > > > > > It seems #12448 and #12459 contain various security fixes. Should > we > > > > > backport > > > > > them to 9.0? > > > > > -- > > > > > Xi Ruoyao > > > > > School of Aerospace Science and Technology, Xidian University > > > > > > > > #12456 (Ruby) has a fix for two vulnerabilities - one from 2012 and > one > > > > from 2015. The problem with backporting updates is that I believe > that > > > > everything that links to them has to be retested. That being said > > > > though, I'd give a +1 to backporting them. > > > > > > I'll try a full jhalfs build to verify 9.0 tomorrow. I hope I can use > > > jhalfs > > > correctly and my 16-core workstation will work fine. But I can't > guarantee > > > any > > > success. > > > > > > > If you need anything, please tell me. I think a full blfs can be built by > > editing at most 30 scripts, most notably: > > I failed. Either I misused jhalfs or it has a bug. I got some "Error 2" > from > make and was able to "fix" some of them. But at last I can't continue > anymore. > > I'll read its documentation again... > The main things to remember before starting a jhalfs build are: 1. All necessary tools are installed. 2. You are either connected to the internet or you have all the necessary packages in your archive and you have a local copy of the book xml files. 3. You have mounted the partition you intend to install on. 4. The user you are logged in as has write permission on the mounted install partition 5. If you are using package management, make sure you have created or copied the two necessary scripts. If I remember those things, I usually don't have any errors. > -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Where are we with respect to keyboard settings in gdm (elogind book)
On Thu, Aug 29, 2019, 8:55 AM Bruce Dubbs via blfs-dev <
blfs-dev@lists.linuxfromscratch.org> wrote:
> On 8/29/19 8:40 AM, Pierre Labastie via blfs-dev wrote:
> > Hi,
> >
> > With the shortly coming release, I think it is time I give some
> information
> > about my findings relative to the setting of the keyboard layout for
> gdm. Note
> > that I have not come to a definitive answer, far from it!
> >
> > The main conclusion is that gdm uses gnome-shell, and that gnome-shell
> uses
> > systemd-localed for getting the keymap when it detects it is on a login
> > screen... So there are two approaches:
> > - add systemd- localed to the system. DJ has provided a patch, but I
> have been
> > unable to use it: or at least localectl does not launch systemd-localed,
> and
> > if I launch it manually before calling localectl, I get either "Function
> not
> > Implemented (for the set-keymap functions) or n/a for both vc-keymap and
> > x11-keymap... Note that systemd-localed runs for a short while, then
> exits...
> > But I think it would be the cleanest approach if we could make it work!
> > - tweak gnome-shell so that it uses the gsettings database (Bruce has
> provided
> > a sed for that, which works). But this leads to another problem, how to
> change
> > user settings for the "gdm" user. I have a workaround, which works to a
> > certain degree, but is not satisfactory, since it does not change the
> > screen-keyboard layout: copy the user dconf database to gdm user's home.
> I
> > still have to try Christopher's suggestions to override gsettings. It it
> works
> > it is cleaner I think. Now, I have a system where both keyboard layout
> and
> > screen-keyboard are azerty, but I am unable to know what put it in this
> state
> > (tried too many things). So there is a third solution, but I do not know
> what!
> > It certainly does not use either the gsettings override nor the user
> db... It
> > might be the following that I have tried (inspired by
> >
> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/desktop_migration_and_administration_guide/customizing-login-screen
> )
> >
> > I created /etc/dconf/profile/gdm with:
> > user-db:user
> > system-db:gdm
> > file-db:/usr/share/gdm/greeter-dconf-defaults
> >
> > Then I created a small gdm database in /etc/dconf/db/gdm.d/01-keyboard
> > [org/gnome/desktop/input-sources]
> > sources=[('xkb','fr)]
> >
> > Then I run dconf update... At first, it did nothing, but I was still
> using a
> > non-sed'ed gnome-shell. Then, when I changed to a sed'ed one, I got the
> French
> > layout...
> >
> > Something to try, but the gsettings override might be easier, if it
> works.
>
> I hope you are staying interested in this, but for the book, I don't
> think it is relevant. The intricacies of the interaction between gnome
> and systemd are what's wrong with the design of systemd and gnome.
>
> From the book's perspective I think we need to either remove gdm from
> the System V book or put in a big caveat that gdm does not work with
> non-us keyboards in the System V environment and to use another display
> manager or the command line to initiate gnome.
>
Does this mean that System V is dying and that I should start getting used
to systemd?
>
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: [blfs-dev] firefox and rsync
On Fri, Aug 23, 2019 at 6:06 AM Roger Koehler wrote: > > I just built and installed rsync, and now firefox crashes when I go to > certain websites (gmail included). I am using basic HTML view to write > this email. Is there a correlation? Disregard. I no longer am experiencing the issue after a system reboot. It may be related to the fact that I was running qemu just prior. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] firefox and rsync
I just built and installed rsync, and now firefox crashes when I go to certain websites (gmail included). I am using basic HTML view to write this email. Is there a correlation? -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] biber 2.13 checksum
I got 5468b8d4db232239c31978548f47786c, and it built successfully. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Xorg under blfs-9.0/elogind
On Sat, Aug 17, 2019 at 1:27 AM Pierre Labastie via blfs-dev wrote: > > On 17/08/2019 00:38, Douglas R. Reno via blfs-dev wrote: > > > > On 8/16/19 4:36 PM, Bruce Dubbs via blfs-dev wrote: > >> I've just completed xorg on a new blfs-9.0 SysV build. Here are some > >> observations. > >> > Ah, I just see that ConsoleKit is referenced on this page. Actually, now > elogind takes care of permissions, and the whole sentence about the user > belonging to the video group is not necessary. Will fix that. I miss ConsoleKit. I don't really like elogind. I understand that it is needed for Gnome, but could Console Kit be left in as an option, maybe as part of the xfce section? -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] xfce actions
After rebuilding the latest xfce, the shutdown, suspend, and hibernate options are greyed out. I am using elogind without a login screen (startx). -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] Sub::Quote-2.006003
This Perl dependency is missing a digit on the checksum (should have a '7' on the end). -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] aspell 0.60.7 compile error in prog/check_funs.cpp
mv -f $depbase.Tpo $depbase.Po prog/check_funs.cpp: In function ‘void print_truncate(FILE*, const char*, int)’: prog/check_funs.cpp:650:11: error: invalid type argument of unary ‘*’ (have ‘char’) 650 | if (**word == '\0') | ^~~~ make[1]: *** [Makefile:1477: prog/check_funs.o] Error 1 -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] xorg failure
On Sun, Jul 28, 2019 at 7:25 PM Ken Moffat via blfs-dev wrote: > > On Sun, Jul 28, 2019 at 06:58:14PM -0500, Bruce Dubbs via blfs-dev wrote: > > On 7/28/19 5:40 PM, Ken Moffat via blfs-dev wrote: > > > > > > So, jhalfs thingk dbus only needs to be built once ? > > > > > > The book recommends building it twice : > > > > > > D-Bus Dependencies > > > Recommended > > > > > > Xorg Libraries (for dbus-launch program) elogind-241.3 (first build > > > without, and then again after elogind is installed) > > > > Looks like jhalfs only identifies one build. Automating circular > > dependencies correctly is a tough job. > > > Agreed. > > > To me the above wording is a little ambiguous. I think the following might > > be better: > > > > Xorg Libraries and elogind-241.3 (first build > > before these packages, and then again after both are installed) > > > > I didn't initially see the ambiguity, but your wording does improve > it. > > However, going back to Roger's post which started this (and I'm > assuming he's using the sysv book), I wonder if elogind had not been > started by the bootscript ? To answer your questions: 1) Yes, I am using the sysv book, 2) Yes, elogind was indeed started, 3) Yes, I followed the build order prescribed by the book. As I side note, I noticed that after elogind is installed the settings in xfce no longer control sleep when the laptop lid is closed. I like to be able to close the lid and let it continue building, but now I have to leave it open or it will go to sleep. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] xorg failure
On Thu, Jul 25, 2019 at 11:23 AM Bruce Dubbs via blfs-dev wrote: > > On 7/25/19 12:09 PM, DJ Lucas via blfs-dev wrote: > > On July 25, 2019 11:36:27 AM CDT, Bruce Dubbs via blfs-dev > > wrote: > >> On 7/25/19 11:08 AM, Ken Moffat via blfs-dev wrote: > >>> On Thu, Jul 25, 2019 at 06:59:10AM -0600, Roger Koehler via blfs-dev > >> wrote: > >>>> The latest LFS/BLFS doesn't work on my Libreboot X200 Tablet: > >>>> > >>>> Fatal server error: > >>>> [ 14887.874] (EE) parse_vt_settings: Cannot open /dev/tty0 > >> (Permission denied) > >>>> > >>>> See attached log file. > >>> > >>> Googling, this sounds like a non-suid Xorg with startx. i.e. the > >>> switch --enable-install-setuid has been omitted. Ah, I think that > >>> might have been briefly removed after the elogind merge (not sure), > >>> but it is certainly in the current book for both sysv and systemd. > >>> > >>> From one of my google results, with some video drivers (including > >>> your intel, but not modesetting!) non-suid X works in destop > >>> environments but not with startx. > >> > >> --enable-install-setuid was removed again, but I cannot confirm that it > >> > >> works. We still need to sort that out. For now the easy way is to > >> > > It really shouldn't be necessary with any of the drivers in BLFS, but I've > > made a mistake someplace and, thus far, I have been unable to locate it. > > Let's just put it back in by default for now until that ah ha moment comes > > of it's own accord. > > Done at revision 21867. Reinstalling xorg-server with this setting gets me back up and running. Thanks. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] xorg failure
The latest LFS/BLFS doesn't work on my Libreboot X200 Tablet: Fatal server error: [ 14887.874] (EE) parse_vt_settings: Cannot open /dev/tty0 (Permission denied) See attached log file. [ 14887.800] X.Org X Server 1.20.5 X Protocol Version 11, Revision 0 [ 14887.807] Build Operating System: Linux 5.2.1-x200t-lfs1 x86_64 [ 14887.809] Current Operating System: Linux x200t-lfs1 5.2.2-x200t-lfs1 #14 SMP Sun Jul 21 09:11:15 MDT 2019 x86_64 [ 14887.809] Kernel command line: BOOT_IMAGE=/vmlinuz-5.2.2 root=/dev/sda2 ro quiet [ 14887.814] Build Date: 20 July 2019 10:32:26PM [ 14887.816] [ 14887.818] Current version of pixman: 0.38.4 [ 14887.823] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 14887.823] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 14887.832] (==) Log file: "/home/roger/.local/share/xorg/Xorg.0.log", Time: Wed Jul 24 21:51:21 2019 [ 14887.835] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 14887.836] (==) No Layout section. Using the first Screen section. [ 14887.836] (==) No screen section available. Using defaults. [ 14887.836] (**) |-->Screen "Default Screen Section" (0) [ 14887.836] (**) | |-->Monitor "" [ 14887.836] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 14887.836] (==) Automatically adding devices [ 14887.836] (==) Automatically enabling devices [ 14887.836] (==) Automatically adding GPU devices [ 14887.837] (==) Max clients allowed: 256, resource mask: 0x1f [ 14887.837] (==) FontPath set to: /usr/share/fonts/X11/misc/, /usr/share/fonts/X11/TTF/, /usr/share/fonts/X11/OTF/, /usr/share/fonts/X11/Type1/, /usr/share/fonts/X11/100dpi/, /usr/share/fonts/X11/75dpi/ [ 14887.837] (==) ModulePath set to "/usr/lib/xorg/modules" [ 14887.837] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 14887.837] (II) Loader magic: 0x616cc0 [ 14887.837] (II) Module ABI versions: [ 14887.837] X.Org ANSI C Emulation: 0.4 [ 14887.837] X.Org Video Driver: 24.0 [ 14887.837] X.Org XInput driver : 24.1 [ 14887.837] X.Org Server Extension : 10.0 [ 14887.842] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31 [ 14887.842] (II) xfree86: Adding drm device (/dev/dri/card0) [ 14887.843] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 10 paused 0 [ 14887.849] (--) PCI:*(0@0:2:0) 8086:2a42:17aa:20e4 rev 7, Mem @ 0xe100/4194304, 0xd000/268435456, I/O @ 0x3400/8, BIOS @ 0x/131072 [ 14887.849] (--) PCI: (0@0:2:1) 8086:2a43:17aa:20e4 rev 7, Mem @ 0xe140/1048576 [ 14887.849] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) [ 14887.849] (II) LoadModule: "glx" [ 14887.849] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 14887.865] (II) Module glx: vendor="X.Org Foundation" [ 14887.865] compiled for 1.20.5, module version = 1.0.0 [ 14887.865] ABI class: X.Org Server Extension, version 10.0 [ 14887.865] (==) Matched intel as autoconfigured driver 0 [ 14887.865] (==) Matched modesetting as autoconfigured driver 1 [ 14887.866] (==) Matched fbdev as autoconfigured driver 2 [ 14887.866] (==) Matched vesa as autoconfigured driver 3 [ 14887.866] (==) Assigned the driver to the xf86ConfigLayout [ 14887.866] (II) LoadModule: "intel" [ 14887.866] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so [ 14887.871] (II) Module intel: vendor="X.Org Foundation" [ 14887.871] compiled for 1.20.5, module version = 2.99.917 [ 14887.871] Module class: X.Org Video Driver [ 14887.871] ABI class: X.Org Video Driver, version 24.0 [ 14887.871] (II) LoadModule: "modesetting" [ 14887.871] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [ 14887.873] (II) Module modesetting: vendor="X.Org Foundation" [ 14887.873] compiled for 1.20.5, module version = 1.20.5 [ 14887.873] Module class: X.Org Video Driver [ 14887.873] ABI class: X.Org Video Driver, version 24.0 [ 14887.873] (II) LoadModule: "fbdev" [ 14887.873] (WW) Warning, couldn't open module fbdev [ 14887.873] (EE) Failed to load module "fbdev" (module does not exist, 0) [ 14887.873] (II) LoadModule: "vesa" [ 14887.874] (WW) Warning, couldn't open module vesa [ 14887.874] (EE) Failed to load module "vesa" (module does not exist, 0) [ 14887.874] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45, 4 Series, G45/G43, Q45/Q43, G41, B43 [ 14887.874] (II) intel: Driver for Intel(R) HD Graphics [ 14887.874] (II) intel: Driver for Intel(R) Iris(TM) Graphics [ 14887.874] (II) intel: Driver for
Re: [blfs-dev] libmypaint-1.3.0
On Fri, May 3, 2019 at 3:29 PM Roger Koehler wrote: > > On Thu, May 2, 2019, 9:36 PM Ken Moffat via blfs-dev > wrote: >> >> On Thu, May 02, 2019 at 08:15:20PM -0600, Roger Koehler via blfs-dev wrote: >> > Why is this package included in the book? What uses it? Any chance of >> > addoing the MyPaint package? >> >> ken@milliways ~ $find repos/BLFS-full/trunk/ -name '*.xml' | xargs grep >> 'linkend.*libmypaint' >> repos/BLFS-full/trunk/BOOK/general/graphlib/mypaint-brushes.xml: > role="runtime" linkend="libmypaint"/> >> repos/BLFS-full/trunk/BOOK/xsoft/other/gimp.xml: > linkend="libmypaint"/>, >> ken@milliways ~ $ >> >> Note that these versions are required by gimp-2.10, but I believe one >> or both is/are not the current versions. The links to both the >> brushes and the lib are "duplicated" from gimp because for the >> brushes, the dependency is runtime, whereas for gimp they are both >> needed at compile time. >> >> What needs MyPaint, or what do you use it for, and is it anything >> more than a straight CMMI or CMake or Meson build (i.e. something >> that users can build without major problems) ? In other words - >> what would be the benefit of adding it to the book (and perhaps >> duplicating the brushes and the lib) ? > > > I was just looking for a simple app that would allow me to work math problems > like on a whiteboard with my Wacom tablet and save my work. I tried building > MyPaint but ran into all sorts of issues, so I was hoping someone had already > figured it out. p.s. I ended up just using gimp. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] libmypaint-1.3.0
On Thu, May 2, 2019, 9:36 PM Ken Moffat via blfs-dev < blfs-dev@lists.linuxfromscratch.org> wrote: > On Thu, May 02, 2019 at 08:15:20PM -0600, Roger Koehler via blfs-dev wrote: > > Why is this package included in the book? What uses it? Any chance of > > addoing the MyPaint package? > > ken@milliways ~ $find repos/BLFS-full/trunk/ -name '*.xml' | xargs grep > 'linkend.*libmypaint' > repos/BLFS-full/trunk/BOOK/general/graphlib/mypaint-brushes.xml: > > repos/BLFS-full/trunk/BOOK/xsoft/other/gimp.xml: linkend="libmypaint"/>, > ken@milliways ~ $ > > Note that these versions are required by gimp-2.10, but I believe one > or both is/are not the current versions. The links to both the > brushes and the lib are "duplicated" from gimp because for the > brushes, the dependency is runtime, whereas for gimp they are both > needed at compile time. > > What needs MyPaint, or what do you use it for, and is it anything > more than a straight CMMI or CMake or Meson build (i.e. something > that users can build without major problems) ? In other words - > what would be the benefit of adding it to the book (and perhaps > duplicating the brushes and the lib) ? > I was just looking for a simple app that would allow me to work math problems like on a whiteboard with my Wacom tablet and save my work. I tried building MyPaint but ran into all sorts of issues, so I was hoping someone had already figured it out. > -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] libmypaint-1.3.0
Why is this package included in the book? What uses it? Any chance of addoing the MyPaint package? -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] pulseaudio runaway
On Tue, Apr 30, 2019, 3:50 PM Ken Moffat via blfs-dev < blfs-dev@lists.linuxfromscratch.org> wrote: > On Tue, Apr 30, 2019 at 04:13:44PM -0500, Bruce Dubbs via blfs-dev wrote: > > I've been noticing that sometimes pulseaudio consumes 100% of one core > and > > stays that way for hours. In one case I can close every application on > my > > desktop and pulseaudio still runs at 100%. > > > > It doesn't really affect things because I have four cores and response > stays > > fine, but it shouldn't be happening. > > > > Has anyone else seen this? > > > > -- Bruce > > Yes, but only on my AMD Phenom, and I think I've seen it across all > releases from the past few years. 'killall -KILL pulseaudio'. > > At one time I removed all its config files and let it regenerate > them when next used, but the issue remains. > I've stopped using pulseaudio. ALSA seems to be able to meet all of my needs. I also noticed the LXDE desktop constantly maxing out one of cores (Intel), so I just use xfce. > -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] gst10-plugins-base-1.16.0
On Fri, Apr 26, 2019 at 5:02 PM Bruce Dubbs via blfs-dev wrote: > > On 4/26/19 4:27 PM, Roger Koehler via blfs-dev wrote: > > On Fri, Apr 26, 2019 at 12:08 PM Bruce Dubbs via blfs-dev > > wrote: > >> > >> On 4/26/19 10:40 AM, Roger Koehler via blfs-dev wrote: > >>> [774/774] Linking target tests/examples/snapshot/snapshot. > >>> make[1]: Entering directory > >>> '/sources/gst10-plugins-base/gst-plugins-base-1.16.0/build' > >>> make[1]: *** No rule to make target 'install'. Stop. > >> > >> Missed that. Now fixed. Thanks for the report. > >> > >> -- Bruce > > > > It looks like a similar issue with the other gst10-plugins: > > Yes, I also missed that in gst-plugins-bad. Now fixed. gst-plugins-bad still doesn't install for me. gst-plugins-base does though. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] gst10-plugins-base-1.16.0
On Fri, Apr 26, 2019 at 12:08 PM Bruce Dubbs via blfs-dev wrote: > > On 4/26/19 10:40 AM, Roger Koehler via blfs-dev wrote: > > [774/774] Linking target tests/examples/snapshot/snapshot. > > make[1]: Entering directory > > '/sources/gst10-plugins-base/gst-plugins-base-1.16.0/build' > > make[1]: *** No rule to make target 'install'. Stop. > > Missed that. Now fixed. Thanks for the report. > >-- Bruce It looks like a similar issue with the other gst10-plugins: [689/689] Linking target tests/examples/playout. make[1]: Entering directory '/sources/gst10-plugins-bad/gst-plugins-bad-1.16.0/build' make[1]: *** No rule to make target 'install'. Stop. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] gst10-plugins-base-1.16.0
[774/774] Linking target tests/examples/snapshot/snapshot. make[1]: Entering directory '/sources/gst10-plugins-base/gst-plugins-base-1.16.0/build' make[1]: *** No rule to make target 'install'. Stop. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] MPlayer
On Wed, Apr 24, 2019 at 1:44 PM Pierre Labastie via blfs-dev wrote: > > On 24/04/2019 17:36, Roger Koehler via blfs-dev wrote: > > On Wed, Apr 24, 2019, 9:32 AM Bruce Dubbs via blfs-dev > > > <mailto:blfs-dev@lists.linuxfromscratch.org>> wrote: > > > > On 4/24/19 6:33 AM, Roger Koehler via blfs-dev wrote: > > > ../scripts/004-z-mplayer: line 69: ./configure: No such file or > > directory > > > > It's there in my tarball. > > > > 58d39f72bf7f3ddaa9e019224bffcb74 MPlayer-1.4.tar.xz > > > > > > It must be a jhalfs issue. > > > > The script for mplayer must be edited, because jhalfs does not do well with > the installation of clearlooks. But the 69th line is in a part, which should > work. > > Well, can you tell me a little more about the issue? What version of MPlayer > are you trying to install? What version of jhalfs are you using? Did the > tarball get extracted? It's because PACKAGE got overwritten. I think I renamed the second one to PACKAGE1 in the jhalfs generated script last time. That does the trick. > > Regards > Pierre Regards Roger -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] MPlayer
On Wed, Apr 24, 2019, 9:32 AM Bruce Dubbs via blfs-dev < blfs-dev@lists.linuxfromscratch.org> wrote: > On 4/24/19 6:33 AM, Roger Koehler via blfs-dev wrote: > > ../scripts/004-z-mplayer: line 69: ./configure: No such file or directory > > It's there in my tarball. > > 58d39f72bf7f3ddaa9e019224bffcb74 MPlayer-1.4.tar.xz > It must be a jhalfs issue. > -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] MPlayer
../scripts/004-z-mplayer: line 69: ./configure: No such file or directory -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] Linux-PAM-1.31-docs.tar.bz2
It looks like they changed to xz: https://github.com/linux-pam/linux-pam/releases/download/v1.3.1/Linux-PAM-1.3.1-docs.tar.xz -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] ghostscript-9.27
This link doesn't work: https://github.com/ArtifexSoftware/ghostpdl-downloads/releases/download/gs926/ghostscript-9.27.tar.gz -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] harfbuzz-2.4.0
I got: 49f111f9b52ae3d9b31c1a3631a320bd -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] mesa-19.0.1
I believe you meant to say: patch -Np1 -i ../mesa-19.0.1-add_xdemos-1.patch not patch -Np1 -i ../mesa-19.0.1-add_xdemos-2.patch The former is on the server, the latter is not. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] gnome-calculator
On Fri, Mar 29, 2019 at 9:00 AM Douglas R. Reno via blfs-dev < blfs-dev@lists.linuxfromscratch.org> wrote: > > On 3/29/19 7:58 AM, Roger Koehler via blfs-dev wrote: > > Still fails to build (using meson 0.49...): > > > > [1/46] Compiling Vala source ../lib/mpfr-glue.vala > > ../lib/currency.vala ../lib/equation.vala ../lib/equation-lexer.vala > > ../lib/equation-parser.vala ../lib/financial.vala > > ../lib/function-manager.vala ../lib/math-equation.vala > > ../lib/math-function.vala ../lib/math-variables.vala > > ../lib/number.vala ../lib/serializer.vala ../lib/unit.vala. > > FAILED: lib/76b5a35@@calculator@sta/mpfr-glue.c > > lib/76b5a35@@calculator@sta/currency.c > > lib/76b5a35@@calculator@sta/equation.c > > lib/76b5a35@@calculator@sta/equation-lexer.c > > lib/76b5a35@@calculator@sta/equation-parser.c > > lib/76b5a35@@calculator@sta/financial.c > > lib/76b5a35@@calculator@sta/function-manager.c > > lib/76b5a35@@calculator@sta/math-equation.c > > lib/76b5a35@@calculator@sta/math-function.c > > lib/76b5a35@@calculator@sta/math-variables.c > > lib/76b5a35@@calculator@sta/number.c > > lib/76b5a35@@calculator@sta/serializer.c > > lib/76b5a35@@calculator@sta/unit.c lib/calculator.h lib/calculator.vapi > > valac -C --debug --debug --vapidir > > /sources/gnome-calculator/gnome-calculator-3.30.1/vapi --pkg posix > > /sources/gnome-calculator/gnome-calculator-3.30.1/vapi/mpfr.vapi > > /sources/gnome-calculator/gnome-calculator-3.30.1/vapi/mpc.vapi --pkg > > libxml-2.0 --pkg libsoup-2.4 --pkg gtksourceview-3.0 --pkg gtk+-3.0 > > --pkg gobject-2.0 --target-glib ' 2.40.0' --pkg glib-2.0 --pkg gio-2.0 > > --color=always --directory lib/76b5a35@@calculator@sta --basedir > > ../lib --library calculator --header lib/calculator.h --vapi > > ../calculator.vapi --target-glib 2.40.0 ../lib/mpfr-glue.vala > > ../lib/currency.vala ../lib/equation.vala ../lib/equation-lexer.vala > > ../lib/equation-parser.vala ../lib/financial.vala > > ../lib/function-manager.vala ../lib/math-equation.vala > > ../lib/math-function.vala ../lib/math-variables.vala > > ../lib/number.vala ../lib/serializer.vala ../lib/unit.vala > > ../lib/equation-parser.vala:79.9-79.43: error: Assignment: Cannot > > convert from `GLib.List' to `GLib.List' > > this.token_list = token_list.copy(); > > ^^^ > > Compilation failed: 1 error(s), 0 warning(s) > > > > > Hi Roger, > > Try this commit and see if it helps: > > > https://gitlab.gnome.org/GNOME/gnome-calculator/commit/d89466a7e90d95b8a34fc0a3db6007599b243788 > > if so, this is a problem introduced by Vala. > That worked! Thanks! -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] gnome-calculator
Still fails to build (using meson 0.49...): [1/46] Compiling Vala source ../lib/mpfr-glue.vala ../lib/currency.vala ../lib/equation.vala ../lib/equation-lexer.vala ../lib/equation-parser.vala ../lib/financial.vala ../lib/function-manager.vala ../lib/math-equation.vala ../lib/math-function.vala ../lib/math-variables.vala ../lib/number.vala ../lib/serializer.vala ../lib/unit.vala. FAILED: lib/76b5a35@@calculator@sta/mpfr-glue.c lib/76b5a35@@calculator@sta/currency.c lib/76b5a35@@calculator@sta/equation.c lib/76b5a35@@calculator@sta/equation-lexer.c lib/76b5a35@@calculator@sta/equation-parser.c lib/76b5a35@@calculator@sta/financial.c lib/76b5a35@@calculator@sta/function-manager.c lib/76b5a35@@calculator@sta/math-equation.c lib/76b5a35@@calculator@sta/math-function.c lib/76b5a35@@calculator@sta/math-variables.c lib/76b5a35@@calculator@sta/number.c lib/76b5a35@@calculator@sta/serializer.c lib/76b5a35@@calculator@sta/unit.c lib/calculator.h lib/calculator.vapi valac -C --debug --debug --vapidir /sources/gnome-calculator/gnome-calculator-3.30.1/vapi --pkg posix /sources/gnome-calculator/gnome-calculator-3.30.1/vapi/mpfr.vapi /sources/gnome-calculator/gnome-calculator-3.30.1/vapi/mpc.vapi --pkg libxml-2.0 --pkg libsoup-2.4 --pkg gtksourceview-3.0 --pkg gtk+-3.0 --pkg gobject-2.0 --target-glib ' 2.40.0' --pkg glib-2.0 --pkg gio-2.0 --color=always --directory lib/76b5a35@@calculator@sta --basedir ../lib --library calculator --header lib/calculator.h --vapi ../calculator.vapi --target-glib 2.40.0 ../lib/mpfr-glue.vala ../lib/currency.vala ../lib/equation.vala ../lib/equation-lexer.vala ../lib/equation-parser.vala ../lib/financial.vala ../lib/function-manager.vala ../lib/math-equation.vala ../lib/math-function.vala ../lib/math-variables.vala ../lib/number.vala ../lib/serializer.vala ../lib/unit.vala ../lib/equation-parser.vala:79.9-79.43: error: Assignment: Cannot convert from `GLib.List' to `GLib.List' this.token_list = token_list.copy(); ^^^ Compilation failed: 1 error(s), 0 warning(s) -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] yaml-0.2.2
I am using the Sys V version: make[1]: Entering directory '/sources/yaml/libyaml-0.2.2' make[1]: *** No rule to make target 'build'. Stop -- 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 instructions
On Wed, Mar 27, 2019, 6:52 AM Pierre Labastie via blfs-dev < blfs-dev@lists.linuxfromscratch.org> wrote: > Hi, > > When making scripts from the book (either by copy/paste > or some use of xsltproc), the generated scripts have `&&' at > the end of each line. It allows to not execute the following > instructions if one instructions fail, but it defeats the use of > "set -e". From the bash man page under the set builtin, for > option -e (emphasis by me): > > Exit immediately if a pipeline (which may consist of a > single simple command), a list, or a compound command > (see SHELL GRAMMAR above), exits with a non-zero status. > *The shell does not exit if the command that fails is > part of the command list immediately following a while > or until keyword, part of the test following the if or > elif reserved words, part of any command executed in a > && or || list except the command following the final && > or ||, any command in a pipeline but the last, or if the > command's return value is being inverted with !.*[...] > > In short, with a construct like: > > set -e > instruction A && > instruction B && > instruction C > > The script does not exit if either instruction A or instruction B fails, > but the following instructions are not executed... This may lead to > a script completing successfully, while the package was in fact not > installed, or only partially installed or compiled! > > So why do we use those `&&' in the book??? > > I've tried to automatically remove the `&&' in jhalfs, but it is not > possible, because sometimes, the `... && ...' construct really really means > if ...; then ... > > There could be a solution: ask devs not to use `... && ...' when they mean > if ...; then ... > > Another is to not have `&&' at the end of line. Actually, what would we > lose? > For me, it makes it easy to see which commands go together when editing the jhalfs-generated scripts. For example, to remove the generation of API documentation when I don't have the necessary tools installed. However, I would gladly forego that luxury for the peace of mind in knowing that when a build completes successfully, it actually installed everything. > -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Meson defaults to debug builds
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 > > 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 > > peanut gallery, or dubious measurements, but sometimes interesting). > > > https://www.phoronix.com/scan.php?page=news_item=Fedora-Mesa-Meson-Debug-Build > > > > AFAICS we do NOT specify buildtype on any meson packages, but on > > cmake we usually specify Release builds ? > > > > It appears that fedora were specifying 'plain', and that left debug > > assertions in the build, which slowed down some things in games > > (e.g. loading levels). > > > > 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've now got verbose output for my test > > builds (ninja -v) and the default setup does not specify -DNDEBUG. > > > > On the current machine's setup (not building mesademos for this, I > > think I'm enabling everything in mesa, including wayland backend): > > > > Build by the book, with logs not in the measurement: > > mesa-19.0.0 1.5 GB > > DESTDIR 611 MB > > > > Specifying -Dbuildtype=release: > > mesa-19.0.0 374 MB > > DESTDIR 91 MB > > > > That uses -O3 (there are suggestions distros might not want to use > > that), and it passes -DNDEBUG. > > > > On my real build at the weekend, the log was unclear about the > > commands actually used (hence my need for ninja -v), but it noticed > > my CFLAGS and CXXFLAGS (-O2 -march=native). > > > > Doing another release build, but passing those (some parts are C, > > others are C++) the initial -O3 for the release is early in the > > arguments, my -O2 -march=native come much later so take effect. > > With that (although I probably only want to pass the march part if > > doing a release build on a fast machine) I get > > mesa-19.0.0 345 MB > > DESTDIR 75 MB. > > > > Summary: for mesa, -Dbuildtype=release looks like the way to go. > > > > The meson docs are at https://mesonbuild.com/Running-Meson.html and > > my reading of that page suggests that 'debugoptimized' is not always > > the default. > > > > Will look at some other meson packages later, if there is any > > interest in this. > FYI, meant to mention before, gnome- calculator has a meson related build failure. Two thoughts. First, what happens to the installed sizes if they are > stripped? Second, a quick check of BLFS shows 62 pakages with meson, > most in gnome. As a side note, there are 162 mentions of cmake. > >-- Bruce > -- > http://lists.linuxfromscratch.org/listinfo/blfs-dev > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page > -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] glib-networking-2.60.0.1
mkdir build && cdbuild && meson --prefix=/usr \ -Dlibproxy=false .. && ninja should be mkdir build && cdbuild && meson --prefix=/usr \ -Dlibproxy=disabled .. && ninja -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] A few issues with most recent book
On Sat, Mar 16, 2019, 2:16 PM Thomas Trepl via blfs-dev < blfs-dev@lists.linuxfromscratch.org> wrote: > Am Samstag, den 16.03.2019, 07:33 -0600 schrieb Roger Koehler via > blfs-dev: > > On Sat, Mar 16, 2019 at 3:39 AM Pierre Labastie via blfs-dev > > wrote: > > > For porting lxde to GTK+3, I have decided to rebuild completely > lfs/blfs with > > > most recent versions. > > > > I'd be interested in knowing if Qt builds for you. If it does, I think > > I will follow suit and do a fresh rebuild. > > Qt-5.12.2 just finished compiling (both i686 and x86_64). > Okay. Thanks. Here goes ... > -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] typo in gobject-introspection-1.60.0
On Tue, Mar 12, 2019 at 6:07 AM Roger Koehler wrote: > > gobject-introspection-1.60.0.tar.xz: OK > ../scripts/002-z-gobject-introspection: line 58: cd: buils: No such file or > directory > ninja: error: loading 'build.ninja': No such file or directory should be cd build (not builds - or buils) -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] cracklib 2.9.7
I waited 24 hours but get the same message: --2019-03-06 14:12:44-- https://github.com/cracklib/cracklib/releases/downloadv2.9.7/cracklib-2.9.7.tar.bz2 Resolving github.com... 192.30.253.113, 192.30.253.112 Connecting to github.com|192.30.253.113|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2019-03-06 14:12:44 ERROR 404: Not Found. --2019-03-06 14:12:45-- http://ftp.osuosl.org/pub/blfs/svn/c/cracklib-2.9.7.tar.bz2 Resolving ftp.osuosl.org... 64.50.236.52, 64.50.233.100, 140.211.166.134, ... Connecting to ftp.osuosl.org|64.50.236.52|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2019-03-06 14:12:45 ERROR 404: Not Found. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Is the i686 patch needed for Qtwebengine-5.12.1?
On Sun, Feb 24, 2019 at 12:15 AM Bruce Dubbs via blfs-dev wrote: > > On 2/24/19 12:53 AM, Ken Moffat via blfs-dev wrote: > > On Fri, Feb 08, 2019 at 11:49:04AM -0700, Roger Koehler via blfs-dev wrote: > >> On Fri, Feb 8, 2019 at 10:44 AM Pierre Labastie via blfs-dev > >> wrote: > >>> On 08/02/2019 17:21, Roger Koehler via blfs-dev wrote: > >>>> FYI, I am still unable to build Qt for some reason. > >>>> I am curious what others see in their log file. Search for vulkan. > >>>> > >>> My log file is mangled, since I used -j4, but I do see the same commands > >>> as in > >>> yours, except of course the last one... > >>> > >>> I suspect some old libQt5Core.so.5 file (it is a symlink) is found by the > >>> ld-linux-x86_64/so.2 loader, and that the symlink is broken. > >>> > >>> If you install qt5 in /opt try "find /opt -name libQt5Core\*". If you > >>> install > >>> in /usr try "find /usr -name libQt5Core\*". If something appears, try > >>> removing > >>> what appears... > >> > >> I have never successfully built Qt on this system, but several > >> attempts have left the following: > >> > >> roger [ ~ ]$ cd /opt > >> roger [ /opt ]$ ls * > >> qt5: > >> > >> qt-5.12.0: > >> > >> qt-5.12.1: > >> roger [ /opt ]$ ls -l > >> total 8 > >> lrwxrwxrwx 1 root root9 Feb 8 07:23 qt5 -> qt-5.12.1 > >> drwxr-xr-x 2 root root 4096 Jan 15 13:38 qt-5.12.0 > >> drwxr-xr-x 2 root root 4096 Feb 3 17:22 qt-5.12.1 > >> > >> Thanks, > >> Roger > > Since you are still having trouble, I went back and looked at this > > earlier post. It doesn't say if those directories are both empty > > (as implied by your "never successfully") or perhaps contain an > > incomplete broken install. > > > > To check that, > > ls -lR /opt/qt-5.12.* | less > > and see what is there. > > > > If there is something there, remove the directory. In fact you > > should remove the 5.12.0 directory anyway because it is at best > > taking up space (even if only a 4K inode with no subdirectories). > > > > And please check again that /etc/ld.so.conf knows about /opt/qt/lib. Yes. I deleted them and followed the book manually to build Qt and received the same error. The ld.so.conf isn't updated until after make install and all of the .desktop files are added. Up to this point, I build everything using jhalfs with tests disabled. My system (ThinkPad) is common enough, I didn't see a reason to wait for all of the tests. I haven't had any trouble with any other package. > I agree with that. My script begins with: > > VERSION=5.12.1 > export QT5PREFIX=/opt/qt5 > sudo rm -rf /opt/qt-$VERSION $QT5PREFIX > sudo mkdir -p $QT5PREFIX > ... > ./configure -prefix $QT5PREFIX \ > ... > > > So I install int the directory, not symlink, /opt/qt5 > > At the end of the script, assuming success, I do: > > sudo mv $QT5PREFIX /opt/qt-$VERSION && > sudo ln -svfn qt-$VERSION /opt/qt5 -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Qt 5.12.1
On Sat, Feb 23, 2019 at 6:33 PM Roger Koehler wrote: > > On Fri, Feb 22, 2019 at 3:30 PM Roger Koehler > wrote: > > > > On Fri, Feb 22, 2019 at 3:09 PM Roger Koehler > > wrote: > > > > > > On Fri, Feb 22, 2019 at 2:59 PM Roger Koehler > > > wrote: > > > > > > > > On Wed, Feb 20, 2019 at 8:30 PM Bruce Dubbs via blfs-dev > > > > wrote: > > > > > > > > > > On 2/20/19 8:45 PM, Roger Koehler via blfs-dev wrote: > > > > > > > > > > > Sorry, I attached the wrong file. That was the script that I ran. > > > > > > Here's the log. > > > > > > > > > > make[3]: Entering directory > > > > > '/var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/src/gui' > > > > > /var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/bin/qmake -o > > > > > Makefile gui.pro > > > > > /var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/src/gui/qvkgen_wrapper.sh > > > > > vulkan/vk.xml > > > > > /var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/header.LGPL > > > > > vulkan/qvulkanfunctions > > > > > /var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/bin/qvkgen: error > > > > > while loading shared libraries: libQt5Core.so.5: cannot open shared > > > > > object file: No such file or directory > > > > > > > > > > It looks like this is happening long before install. Checking my log, > > > > > libQt5Core.so.5 is built on line 875 on my log and the problem is > > > > > showing up on line 1042. > > > > > > > > > > I looks like the library should be in qtbase/src/corelib. If > > > > > libQt5Core.so.5 is there, run ldd on it and see if it can find all the > > > > > components it needs. > > > > > > Here is where the problem is: > > (See previous post for image.) > > Why isn't it finding it? > > So, I copied libQtCore.so.5.2.1 from the qtbase/lib build area to > /usr/lib, ran ldconfig, did a make clean and make, and it still can't > find it! p.s. I also manually created the libQtCore.so.5 and libQtCore.so symbolic links in /usr/lib before ldconfig. > I guess I'm going to have to go back to debian if I want to use > anything that requires qt, or copy the binaries. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Qt 5.12.1
On Fri, Feb 22, 2019 at 3:30 PM Roger Koehler wrote: > > On Fri, Feb 22, 2019 at 3:09 PM Roger Koehler > wrote: > > > > On Fri, Feb 22, 2019 at 2:59 PM Roger Koehler > > wrote: > > > > > > On Wed, Feb 20, 2019 at 8:30 PM Bruce Dubbs via blfs-dev > > > wrote: > > > > > > > > On 2/20/19 8:45 PM, Roger Koehler via blfs-dev wrote: > > > > > > > > > Sorry, I attached the wrong file. That was the script that I ran. > > > > > Here's the log. > > > > > > > > make[3]: Entering directory > > > > '/var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/src/gui' > > > > /var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/bin/qmake -o > > > > Makefile gui.pro > > > > /var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/src/gui/qvkgen_wrapper.sh > > > > vulkan/vk.xml > > > > /var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/header.LGPL > > > > vulkan/qvulkanfunctions > > > > /var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/bin/qvkgen: error > > > > while loading shared libraries: libQt5Core.so.5: cannot open shared > > > > object file: No such file or directory > > > > > > > > It looks like this is happening long before install. Checking my log, > > > > libQt5Core.so.5 is built on line 875 on my log and the problem is > > > > showing up on line 1042. > > > > > > > > I looks like the library should be in qtbase/src/corelib. If > > > > libQt5Core.so.5 is there, run ldd on it and see if it can find all the > > > > components it needs. > > > > Here is where the problem is: > (See previous post for image.) > Why isn't it finding it? So, I copied libQtCore.so.5.2.1 from the qtbase/lib build area to /usr/lib, ran ldconfig, did a make clean and make, and it still can't find it! I guess I'm going to have to go back to debian if I want to use anything that requires qt, or copy the binaries. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Qt 5.12.1
On Fri, Feb 22, 2019 at 3:09 PM Roger Koehler wrote: > > On Fri, Feb 22, 2019 at 2:59 PM Roger Koehler wrote: > > > > On Wed, Feb 20, 2019 at 8:30 PM Bruce Dubbs via blfs-dev < blfs-dev@lists.linuxfromscratch.org> wrote: > > > > > > On 2/20/19 8:45 PM, Roger Koehler via blfs-dev wrote: > > > > > > > Sorry, I attached the wrong file. That was the script that I ran. > > > > Here's the log. > > > > > > make[3]: Entering directory > > > '/var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/src/gui' > > > /var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/bin/qmake -o > > > Makefile gui.pro > > > /var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/src/gui/qvkgen_wrapper.sh > > > vulkan/vk.xml > > > /var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/header.LGPL > > > vulkan/qvulkanfunctions > > > /var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/bin/qvkgen: error > > > while loading shared libraries: libQt5Core.so.5: cannot open shared > > > object file: No such file or directory > > > > > > It looks like this is happening long before install. Checking my log, > > > libQt5Core.so.5 is built on line 875 on my log and the problem is > > > showing up on line 1042. > > > > > > I looks like the library should be in qtbase/src/corelib. If > > > libQt5Core.so.5 is there, run ldd on it and see if it can find all the > > > components it needs. > > Here is where the problem is: [image: image.png] Why isn't it finding it? -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Qt 5.12.1
On Wed, Feb 20, 2019 at 8:30 PM Bruce Dubbs via blfs-dev < blfs-dev@lists.linuxfromscratch.org> wrote: > > On 2/20/19 8:45 PM, Roger Koehler via blfs-dev wrote: > > > Sorry, I attached the wrong file. That was the script that I ran. > > Here's the log. > > make[3]: Entering directory > '/var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/src/gui' > /var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/bin/qmake -o > Makefile gui.pro > /var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/src/gui/qvkgen_wrapper.sh > vulkan/vk.xml > /var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/header.LGPL > vulkan/qvulkanfunctions > /var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/bin/qvkgen: error > while loading shared libraries: libQt5Core.so.5: cannot open shared > object file: No such file or directory > > It looks like this is happening long before install. Checking my log, > libQt5Core.so.5 is built on line 875 on my log and the problem is > showing up on line 1042. > > I looks like the library should be in qtbase/src/corelib. If > libQt5Core.so.5 is there, run ldd on it and see if it can find all the > components it needs. It isn't there: [image: image.png] I've attached another log file with a little more context. qt.log Description: Binary data -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Qt 5.12.1
On Wed, Feb 20, 2019 at 7:40 PM Roger Koehler wrote:
>
> On Mon, Feb 18, 2019 at 12:41 PM Bruce Dubbs via blfs-dev
> wrote:
> >
> > On 2/18/19 12:46 PM, Roger Koehler via blfs-dev wrote:
> > > I built a new SysV system from scratch using jhalfs with the latest svn
> > > release, and I am still unable to build Qt. I'm surprised that no one
> > > else has run into this issue (see my recent posts on this list).
> > >
> > > I have used all of the recommended and required dependencies and only
> > > minor edits to the scripts generated by jhalfs so as not to need doxygen
> > > or texlive or, in the case of highlight, qt.
> >
> > It might help to see the script you actually used. I built qt over the
> > weekend with no problems. I used:
> >
> > VERSION=5.12.1
> >
> > export QT5PREFIX=/opt/qt5
> > sudo rm -rf /opt/qt-$VERSION $QT5PREFIX
> > sudo mkdir -p $QT5PREFIX
> >
> >
> > find . -name "*.pr[io]" | xargs sed -i 's/python/&3/' &&
> >
> > ./configure -prefix $QT5PREFIX \
> > -sysconfdir /etc/xdg \
> > -confirm-license \
> > -opensource \
> > -dbus-linked \
> > -openssl-linked \
> > -system-harfbuzz \
> > -system-sqlite \
> > -nomake examples \
> > -no-rpath\
> > -skip qtwebengine&&
> >
> > make -j4 &&
> >
> > $SUDO make install &&
> >
> > $SUDO find $QT5PREFIX/ -name \*.prl \
> >-exec sed -i -e '/^QMAKE_PRL_BUILD_DIR/d;' {} \; &&
> >
> > $SUDO mv $QT5PREFIX /opt/qt-$VERSION &&
> > $SUDO ln -svfn qt-$VERSION /opt/qt5
> >
>
> > After it stops, build again at -j1 so you can find where the build
> > errors out. We need to see that to help.
> >
> > Let me note that that the space required is very large. Make sure you
> > are not running out of disk space or, less likely, memory.
>
> Bruce,
>
> I used your script only with make -j1. Same problem. I copied the log
> output where the error occurred in the attached file.
Sorry, I attached the wrong file. That was the script that I ran.
Here's the log.
qt.log
Description: Binary data
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: [blfs-dev] Qt 5.12.1
On Mon, Feb 18, 2019 at 12:41 PM Bruce Dubbs via blfs-dev
wrote:
>
> On 2/18/19 12:46 PM, Roger Koehler via blfs-dev wrote:
> > I built a new SysV system from scratch using jhalfs with the latest svn
> > release, and I am still unable to build Qt. I'm surprised that no one
> > else has run into this issue (see my recent posts on this list).
> >
> > I have used all of the recommended and required dependencies and only
> > minor edits to the scripts generated by jhalfs so as not to need doxygen
> > or texlive or, in the case of highlight, qt.
>
> It might help to see the script you actually used. I built qt over the
> weekend with no problems. I used:
>
> VERSION=5.12.1
>
> export QT5PREFIX=/opt/qt5
> sudo rm -rf /opt/qt-$VERSION $QT5PREFIX
> sudo mkdir -p $QT5PREFIX
>
>
> find . -name "*.pr[io]" | xargs sed -i 's/python/&3/' &&
>
> ./configure -prefix $QT5PREFIX \
> -sysconfdir /etc/xdg \
> -confirm-license \
> -opensource \
> -dbus-linked \
> -openssl-linked \
> -system-harfbuzz \
> -system-sqlite \
> -nomake examples \
> -no-rpath\
> -skip qtwebengine&&
>
> make -j4 &&
>
> $SUDO make install &&
>
> $SUDO find $QT5PREFIX/ -name \*.prl \
>-exec sed -i -e '/^QMAKE_PRL_BUILD_DIR/d;' {} \; &&
>
> $SUDO mv $QT5PREFIX /opt/qt-$VERSION &&
> $SUDO ln -svfn qt-$VERSION /opt/qt5
>
> After it stops, build again at -j1 so you can find where the build
> errors out. We need to see that to help.
>
> Let me note that that the space required is very large. Make sure you
> are not running out of disk space or, less likely, memory.
Bruce,
I used your script only with make -j1. Same problem. I copied the log
output where the error occurred in the attached file.
I have 8 GB of RAM and 8 GB of swap space and over 150 GB of disk space.
I am using an Lenovo X200 Tablet ThinkPad. I don't understand why my
system is so different.
Thanks,
Roger
qt
Description: Binary data
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
[blfs-dev] Qt 5.12.1
I built a new SysV system from scratch using jhalfs with the latest svn release, and I am still unable to build Qt. I'm surprised that noone else has run into this issue (see my recent posts on this list). I have used all of the recommended and required dependencies and only minor edits to the scripts generated by jhalfs so as not to need doxygen or texlive or, in the case of highlight, qt. I did make two departures from a default build: 1) I used Linux 4.9.158, and 2) I mounted /var to a different partition and used /var/lib/sources for my source archive. /opt is at the same partition as /usr (root). The first thing I did after LFS was complete was install DHCP client and wpa_supplicant (without dbus or qt) so that I could wirelessly connect to the internet. Then I rebuilt shadow with Pam and Cracklib and Python3. Then ALSA, followed by X Windows. The very next thing I wanted to do is build Qt. All dependencies built fine, but then Qt bombed out at the exact same place as before: vulkan. Any ideas? Thanks, Roger -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] scons checksum failed
scons-3.0.4.tar.gz: FAILED md5sum: WARNING: 1 computed checksum did NOT match -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Is the i686 patch needed for Qtwebengine-5.12.1?
On Fri, Feb 8, 2019 at 10:44 AM Pierre Labastie via blfs-dev wrote: > On 08/02/2019 17:21, Roger Koehler via blfs-dev wrote: > > FYI, I am still unable to build Qt for some reason. > > I am curious what others see in their log file. Search for vulkan. > > > My log file is mangled, since I used -j4, but I do see the same commands as in > yours, except of course the last one... > > I suspect some old libQt5Core.so.5 file (it is a symlink) is found by the > ld-linux-x86_64/so.2 loader, and that the symlink is broken. > > If you install qt5 in /opt try "find /opt -name libQt5Core\*". If you install > in /usr try "find /usr -name libQt5Core\*". If something appears, try removing > what appears... I have never successfully built Qt on this system, but several attempts have left the following: roger [ ~ ]$ cd /opt roger [ /opt ]$ ls * qt5: qt-5.12.0: qt-5.12.1: roger [ /opt ]$ ls -l total 8 lrwxrwxrwx 1 root root9 Feb 8 07:23 qt5 -> qt-5.12.1 drwxr-xr-x 2 root root 4096 Jan 15 13:38 qt-5.12.0 drwxr-xr-x 2 root root 4096 Feb 3 17:22 qt-5.12.1 Thanks, Roger -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Is the i686 patch needed for Qtwebengine-5.12.1?
On Fri, Feb 8, 2019 at 2:22 AM Pierre Labastie via blfs-dev wrote: > > Hi, > > Trying to build qtwebengine-5.12.1 (for x86_64), I applied the patch (done > automatically by jhalfs), and the build failed quickly. Looking at the source, > it seems to me that the proper macro is now defined if gcc is used... So I > wonder whether the patch is still needed. Maybe, Douglas can confirm it is > not. Otherwise, I'll update my 32 bit VM and try (may take some time). FYI, I am still unable to build Qt for some reason. Using make -j1 I get these messages leading up to the error: rm -f libQt5Xml.so.5.12.1 libQt5Xml.so libQt5Xml.so.5 libQt5Xml.so.5.12 g++ -Wl,--no-undefined -Wl,--version-script,QtXml.version -Wl,-O1 -fuse-ld=gold -Wl,--enable-new-dtags -shared -Wl,-Bsymbolic- functions -Wl,-soname,libQt5Xml.so.5 -o libQt5Xml.so.5.12.1 .obj/qdom.o .obj/qxml.o -L/var/lib/sources/qt5/qt-everywhere-src- 5.12.1/qtbase/lib -lQt5Core -lpthread ln -s libQt5Xml.so.5.12.1 libQt5Xml.so ln -s libQt5Xml.so.5.12.1 libQt5Xml.so.5 ln -s libQt5Xml.so.5.12.1 libQt5Xml.so.5.12 rm -f ../../lib/libQt5Xml.so.5.12.1 mv -f libQt5Xml.so.5.12.1 ../../lib/libQt5Xml.so.5.12.1 rm -f ../../lib/libQt5Xml.so rm -f ../../lib/libQt5Xml.so.5 rm -f ../../lib/libQt5Xml.so.5.12 mv -f libQt5Xml.so ../../lib/libQt5Xml.so mv -f libQt5Xml.so.5 ../../lib/libQt5Xml.so.5 mv -f libQt5Xml.so.5.12 ../../lib/libQt5Xml.so.5.12 make[4]: Leaving directory '/var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/src/xml' cd tools/qvkgen/ && ( test -e Makefile || /var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/bin/qmake -o Makefile /var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/src/tools/qvkgen/qvkgen.pro ) && make -f Makefile make[4]: Entering directory '/var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/src/tools/qvkgen' g++ -c -pipe -O2 -std=c++1z -fno-exceptions -Wall -W -Wvla -Wdate-time -Wshift-overflow=2 -Wduplicated-cond -Wno-stringop-overflow -D_REENTRANT -fPIC -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_USE_QSTRINGBUILDER -DQT_NO_EXCEPTIONS -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG -DQT_CORE_LIB -I. -I../../../include -I../../../include/QtCore -I.moc -I../../../mkspecs/linux-g++ -o .obj/qvkgen.o qvkgen.cpp g++ -Wl,-O1 -fuse-ld=gold -Wl,--enable-new-dtags -o ../../../bin/qvkgen .obj/qvkgen.o -L/var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/lib -lQt5Core -lpthread make[4]: Leaving directory '/var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/src/tools/qvkgen' cd gui/ && ( test -e Makefile || /var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/bin/qmake -o Makefile /var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/src/gui/gui.pro ) && make -f Makefile make[4]: Entering directory '/var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/src/gui' /var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/src/gui/qvkgen_wrapper.sh vulkan/vk.xml /var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/header.LGPL vulkan/qvulkanfunctions /var/lib/sources/qt5/qt-everywhere-src-5.12.1/qtbase/bin/qvkgen: error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory make[4]: *** [Makefile:2063: vulkan/qvulkanfunctions.h] Error 127 I am curious what others see in their log file. Search for vulkan. Thanks, Roger -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Qt5
On Wed, Jan 16, 2019 at 9:41 AM Roger Koehler wrote: > > On Wed, Jan 16, 2019 at 8:51 AM Bruce Dubbs via blfs-dev > wrote: > > > > On 01/16/2019 06:31 AM, Roger Koehler via blfs-dev wrote: > > > On Tue, Jan 15, 2019 at 8:43 PM Ken Moffat via blfs-dev > > > wrote: > > >> > > >> On Tue, Jan 15, 2019 at 04:31:44PM -0700, Roger Koehler via blfs-dev > > >> wrote: > > >>> Since there is this note: > > >>> > > >>> -skip qtwebengine: This switch disables building the QtWebEngine. The > > >>> BLFS > > >>> editors have chosen to build qtwebengine-5.12.0 separately. > > >>> > > >>> Should qtwebengine be listed as a dependency? > > >>> > > >> > > >> No, it is shipped as part of Qt5 but the only package in the book > > >> which uses it it falkon, and I think there is one external web > > >> browser (perhaps text-only) which can use it. And its build is > > >> excessively long and big for people who don't need it. > > >> > > >>> I don't have it installed yet and Qt5 doesn't build: > > >>> > > >>> ln -s libQt5Network.so.5.12.0 libQt5Network.so > > >>> ln -s libQt5Network.so.5.12.0 libQt5Network.so.5 > > >>> ln -s libQt5Network.so.5.12.0 libQt5Network.so.5.12 > > >>> rm -f ../../lib/libQt5Network.so.5.12.0 > > >>> mv -f libQt5Network.so.5.12.0 ../../lib/libQt5Network.so.5.12.0 > > >>> rm -f ../../lib/libQt5Network.so > > >>> rm -f ../../lib/libQt5Network.so.5 > > >>> rm -f ../../lib/libQt5Network.so.5.12 > > >>> mv -f libQt5Network.so ../../lib/libQt5Network.so > > >>> mv -f libQt5Network.so.5 ../../lib/libQt5Network.so.5 > > >>> mv -f libQt5Network.so.5.12 ../../lib/libQt5Network.so.5.12 > > >>> make[4]: Leaving directory > > >>> '/var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/src/network' > > >>> make[3]: Leaving directory > > >>> '/var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/src' > > >>> make[2]: *** [Makefile:49: sub-src-make_first] Error 2 > > >>> make[2]: Leaving directory > > >>> '/var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase' > > >>> make[1]: *** [Makefile:83: module-qtbase-make_first] Error 2 > > >>> make[1]: Leaving directory > > >>> '/var/lib/sources/qt5/qt-everywhere-src-5.12.0' > > >> > > >> In my own logs [ -j4 ] that chunk of output starts about 3000 lines > > >> into the log. You should know enough by now to recognise that in > > >> almost all cases (except packages which use rust) the actual error > > >> message on a multicore build can be a long way before all the other > > >> parallel builds stop. > > >> > > >> If you have a log, try looking for 'Error ' in the earlier lines. > > > > > > Good point. I changed to make -j1 to make it easier, and this is where > > > it bombs out: > > > > > > make[4]: Entering directory > > > '/var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/src/gui' > > > /var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/src/gui/qvkgen_wrapper.sh > > > vulkan/vk.xml > > > /var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/header.LGPL > > > vulkan/qvulkanfunctions > > > /var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/bin/qvkgen: error > > > while loading shared libraries: libQt5Core.so.5: cannot open shared > > > object file: No such file or directory > > > make[4]: *** [Makefile:2061: vulkan/qvulkanfunctions.h] Error 127 > > > make[4]: Leaving directory > > > '/var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/src/gui' > > > > Is qt being installed in in /usr or /opt? If /opt, make sure > > /etc/ld.so.conf is updated and in either case run ldconfig. > > Right. That is done at the end of the script. I'll move it to the front ... Same error. Does this mean I need the binaries before I can build? -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Qt5
On Wed, Jan 16, 2019 at 8:51 AM Bruce Dubbs via blfs-dev wrote: > > On 01/16/2019 06:31 AM, Roger Koehler via blfs-dev wrote: > > On Tue, Jan 15, 2019 at 8:43 PM Ken Moffat via blfs-dev > > wrote: > >> > >> On Tue, Jan 15, 2019 at 04:31:44PM -0700, Roger Koehler via blfs-dev wrote: > >>> Since there is this note: > >>> > >>> -skip qtwebengine: This switch disables building the QtWebEngine. The BLFS > >>> editors have chosen to build qtwebengine-5.12.0 separately. > >>> > >>> Should qtwebengine be listed as a dependency? > >>> > >> > >> No, it is shipped as part of Qt5 but the only package in the book > >> which uses it it falkon, and I think there is one external web > >> browser (perhaps text-only) which can use it. And its build is > >> excessively long and big for people who don't need it. > >> > >>> I don't have it installed yet and Qt5 doesn't build: > >>> > >>> ln -s libQt5Network.so.5.12.0 libQt5Network.so > >>> ln -s libQt5Network.so.5.12.0 libQt5Network.so.5 > >>> ln -s libQt5Network.so.5.12.0 libQt5Network.so.5.12 > >>> rm -f ../../lib/libQt5Network.so.5.12.0 > >>> mv -f libQt5Network.so.5.12.0 ../../lib/libQt5Network.so.5.12.0 > >>> rm -f ../../lib/libQt5Network.so > >>> rm -f ../../lib/libQt5Network.so.5 > >>> rm -f ../../lib/libQt5Network.so.5.12 > >>> mv -f libQt5Network.so ../../lib/libQt5Network.so > >>> mv -f libQt5Network.so.5 ../../lib/libQt5Network.so.5 > >>> mv -f libQt5Network.so.5.12 ../../lib/libQt5Network.so.5.12 > >>> make[4]: Leaving directory > >>> '/var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/src/network' > >>> make[3]: Leaving directory > >>> '/var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/src' > >>> make[2]: *** [Makefile:49: sub-src-make_first] Error 2 > >>> make[2]: Leaving directory > >>> '/var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase' > >>> make[1]: *** [Makefile:83: module-qtbase-make_first] Error 2 > >>> make[1]: Leaving directory '/var/lib/sources/qt5/qt-everywhere-src-5.12.0' > >> > >> In my own logs [ -j4 ] that chunk of output starts about 3000 lines > >> into the log. You should know enough by now to recognise that in > >> almost all cases (except packages which use rust) the actual error > >> message on a multicore build can be a long way before all the other > >> parallel builds stop. > >> > >> If you have a log, try looking for 'Error ' in the earlier lines. > > > > Good point. I changed to make -j1 to make it easier, and this is where > > it bombs out: > > > > make[4]: Entering directory > > '/var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/src/gui' > > /var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/src/gui/qvkgen_wrapper.sh > > vulkan/vk.xml > > /var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/header.LGPL > > vulkan/qvulkanfunctions > > /var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/bin/qvkgen: error > > while loading shared libraries: libQt5Core.so.5: cannot open shared > > object file: No such file or directory > > make[4]: *** [Makefile:2061: vulkan/qvulkanfunctions.h] Error 127 > > make[4]: Leaving directory > > '/var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/src/gui' > > Is qt being installed in in /usr or /opt? If /opt, make sure > /etc/ld.so.conf is updated and in either case run ldconfig. Right. That is done at the end of the script. I'll move it to the front ... -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Qt5
On Tue, Jan 15, 2019 at 8:43 PM Ken Moffat via blfs-dev wrote: > > On Tue, Jan 15, 2019 at 04:31:44PM -0700, Roger Koehler via blfs-dev wrote: > > Since there is this note: > > > > -skip qtwebengine: This switch disables building the QtWebEngine. The BLFS > > editors have chosen to build qtwebengine-5.12.0 separately. > > > > Should qtwebengine be listed as a dependency? > > > > No, it is shipped as part of Qt5 but the only package in the book > which uses it it falkon, and I think there is one external web > browser (perhaps text-only) which can use it. And its build is > excessively long and big for people who don't need it. > > > I don't have it installed yet and Qt5 doesn't build: > > > > ln -s libQt5Network.so.5.12.0 libQt5Network.so > > ln -s libQt5Network.so.5.12.0 libQt5Network.so.5 > > ln -s libQt5Network.so.5.12.0 libQt5Network.so.5.12 > > rm -f ../../lib/libQt5Network.so.5.12.0 > > mv -f libQt5Network.so.5.12.0 ../../lib/libQt5Network.so.5.12.0 > > rm -f ../../lib/libQt5Network.so > > rm -f ../../lib/libQt5Network.so.5 > > rm -f ../../lib/libQt5Network.so.5.12 > > mv -f libQt5Network.so ../../lib/libQt5Network.so > > mv -f libQt5Network.so.5 ../../lib/libQt5Network.so.5 > > mv -f libQt5Network.so.5.12 ../../lib/libQt5Network.so.5.12 > > make[4]: Leaving directory > > '/var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/src/network' > > make[3]: Leaving directory > > '/var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/src' > > make[2]: *** [Makefile:49: sub-src-make_first] Error 2 > > make[2]: Leaving directory > > '/var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase' > > make[1]: *** [Makefile:83: module-qtbase-make_first] Error 2 > > make[1]: Leaving directory '/var/lib/sources/qt5/qt-everywhere-src-5.12.0' > > In my own logs [ -j4 ] that chunk of output starts about 3000 lines > into the log. You should know enough by now to recognise that in > almost all cases (except packages which use rust) the actual error > message on a multicore build can be a long way before all the other > parallel builds stop. > > If you have a log, try looking for 'Error ' in the earlier lines. Good point. I changed to make -j1 to make it easier, and this is where it bombs out: make[4]: Entering directory '/var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/src/gui' /var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/src/gui/qvkgen_wrapper.sh vulkan/vk.xml /var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/header.LGPL vulkan/qvulkanfunctions /var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/bin/qvkgen: error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory make[4]: *** [Makefile:2061: vulkan/qvulkanfunctions.h] Error 127 make[4]: Leaving directory '/var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/src/gui' -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Qt5
On Tue, Jan 15, 2019 at 5:43 PM Roger Koehler wrote: > > On Tue, Jan 15, 2019 at 5:04 PM Douglas R. Reno via blfs-dev > wrote: > > On 1/15/19 6:03 PM, Roger Koehler via blfs-dev wrote: > > > On Tue, Jan 15, 2019 at 4:31 PM Roger Koehler > > > wrote: > > >> Since there is this note: > > >> > > >> -skip qtwebengine: This switch disables building the QtWebEngine. The > > >> BLFS editors have chosen to build qtwebengine-5.12.0 separately. > > >> > > >> Should qtwebengine be listed as a dependency? > > >> > > >> I don't have it installed yet and Qt5 doesn't build: > > >> > > >> ln -s libQt5Network.so.5.12.0 libQt5Network.so > > >> ln -s libQt5Network.so.5.12.0 libQt5Network.so.5 > > >> ln -s libQt5Network.so.5.12.0 libQt5Network.so.5.12 > > >> rm -f ../../lib/libQt5Network.so.5.12.0 > > >> mv -f libQt5Network.so.5.12.0 ../../lib/libQt5Network.so.5.12.0 > > >> rm -f ../../lib/libQt5Network.so > > >> rm -f ../../lib/libQt5Network.so.5 > > >> rm -f ../../lib/libQt5Network.so.5.12 > > >> mv -f libQt5Network.so ../../lib/libQt5Network.so > > >> mv -f libQt5Network.so.5 ../../lib/libQt5Network.so.5 > > >> mv -f libQt5Network.so.5.12 ../../lib/libQt5Network.so.5.12 > > >> make[4]: Leaving directory > > >> '/var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/src/network' > > >> make[3]: Leaving directory > > >> '/var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/src' > > >> make[2]: *** [Makefile:49: sub-src-make_first] Error 2 > > >> make[2]: Leaving directory > > >> '/var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase' > > >> make[1]: *** [Makefile:83: module-qtbase-make_first] Error 2 > > >> make[1]: Leaving directory > > >> '/var/lib/sources/qt5/qt-everywhere-src-5.12.0' > > > Probably unrelated. I get the same error if I remove the switch. > > > > > > Are you missing any of the dependencies? It works fine on my end, and > > I've built it on three separate systems over the past couple weeks. > > It seems like I should get a message from configure if I were: > > Configure summary: > > Build type: linux-g++ (x86_64, CPU features: mmx sse sse2) > Compiler: gcc 8.2.0 > Configuration: use_gold_linker sse2 aesni sse3 ssse3 sse4_1 sse4_2 avx > avx2 avx512f avx512bw avx512cd avx512dq avx512er avx512 > ifma avx512pf avx512vbmi avx512vl compile_examples enable_new_dtags > f16c largefile precompile_header rdrnd shani x86SimdAlways > shared release c++11 c++14 c++1z concurrent dbus reduce_exports > reduce_relocations stl > Build options: > Mode ... release > Optimize release build for size no > Building shared libraries .. yes > Using C standard ... C11 > Using C++ standard . C++1z > Using ccache ... no > Using gold linker .. yes > Using new DTAGS yes > Using precompiled headers .. yes > Using LTCG . no > Target compiler supports: > SSE .. SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 > AVX .. AVX AVX2 > AVX512 ... F ER CD PF DQ BW VL IFMA VBMI > Other x86 AES F16C RDRAND SHA > Intrinsics without -mXXX option .. yes > Build parts libs tools > Qt modules and options: > Qt Concurrent .. yes > Qt D-Bus ... yes > Qt D-Bus directly linked to libdbus yes > Qt Gui . yes > Qt Network . yes > Qt Sql . yes > Qt Testlib . yes > Qt Widgets . yes > Qt Xml . yes > Support enabled for: > Using pkg-config ... yes > udev ... yes > Using system zlib .. yes > Qt Core: > DoubleConversion ... yes > Using system DoubleConversion no > GLib ... yes > iconv .. no > ICU yes > Tracing backend > Logging backends: > journald . no > syslog
Re: [blfs-dev] Qt5
On Tue, Jan 15, 2019 at 5:04 PM Douglas R. Reno via blfs-dev wrote: > On 1/15/19 6:03 PM, Roger Koehler via blfs-dev wrote: > > On Tue, Jan 15, 2019 at 4:31 PM Roger Koehler > > wrote: > >> Since there is this note: > >> > >> -skip qtwebengine: This switch disables building the QtWebEngine. The BLFS > >> editors have chosen to build qtwebengine-5.12.0 separately. > >> > >> Should qtwebengine be listed as a dependency? > >> > >> I don't have it installed yet and Qt5 doesn't build: > >> > >> ln -s libQt5Network.so.5.12.0 libQt5Network.so > >> ln -s libQt5Network.so.5.12.0 libQt5Network.so.5 > >> ln -s libQt5Network.so.5.12.0 libQt5Network.so.5.12 > >> rm -f ../../lib/libQt5Network.so.5.12.0 > >> mv -f libQt5Network.so.5.12.0 ../../lib/libQt5Network.so.5.12.0 > >> rm -f ../../lib/libQt5Network.so > >> rm -f ../../lib/libQt5Network.so.5 > >> rm -f ../../lib/libQt5Network.so.5.12 > >> mv -f libQt5Network.so ../../lib/libQt5Network.so > >> mv -f libQt5Network.so.5 ../../lib/libQt5Network.so.5 > >> mv -f libQt5Network.so.5.12 ../../lib/libQt5Network.so.5.12 > >> make[4]: Leaving directory > >> '/var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/src/network' > >> make[3]: Leaving directory > >> '/var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/src' > >> make[2]: *** [Makefile:49: sub-src-make_first] Error 2 > >> make[2]: Leaving directory > >> '/var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase' > >> make[1]: *** [Makefile:83: module-qtbase-make_first] Error 2 > >> make[1]: Leaving directory '/var/lib/sources/qt5/qt-everywhere-src-5.12.0' > > Probably unrelated. I get the same error if I remove the switch. > > > Are you missing any of the dependencies? It works fine on my end, and > I've built it on three separate systems over the past couple weeks. It seems like I should get a message from configure if I were: Configure summary: Build type: linux-g++ (x86_64, CPU features: mmx sse sse2) Compiler: gcc 8.2.0 Configuration: use_gold_linker sse2 aesni sse3 ssse3 sse4_1 sse4_2 avx avx2 avx512f avx512bw avx512cd avx512dq avx512er avx512 ifma avx512pf avx512vbmi avx512vl compile_examples enable_new_dtags f16c largefile precompile_header rdrnd shani x86SimdAlways shared release c++11 c++14 c++1z concurrent dbus reduce_exports reduce_relocations stl Build options: Mode ... release Optimize release build for size no Building shared libraries .. yes Using C standard ... C11 Using C++ standard . C++1z Using ccache ... no Using gold linker .. yes Using new DTAGS yes Using precompiled headers .. yes Using LTCG . no Target compiler supports: SSE .. SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 AVX .. AVX AVX2 AVX512 ... F ER CD PF DQ BW VL IFMA VBMI Other x86 AES F16C RDRAND SHA Intrinsics without -mXXX option .. yes Build parts libs tools Qt modules and options: Qt Concurrent .. yes Qt D-Bus ... yes Qt D-Bus directly linked to libdbus yes Qt Gui . yes Qt Network . yes Qt Sql . yes Qt Testlib . yes Qt Widgets . yes Qt Xml . yes Support enabled for: Using pkg-config ... yes udev ... yes Using system zlib .. yes Qt Core: DoubleConversion ... yes Using system DoubleConversion no GLib ... yes iconv .. no ICU yes Tracing backend Logging backends: journald . no syslog ... no slog2 no Using system PCRE2 . yes Qt Network: getifaddrs() ... yes IPv6 ifname yes libproxy ... no Linux AF_NETLINK ... yes OpenSSL yes Qt directly linked to OpenSSL yes OpenSSL 1.1 yes DTLS ... yes SCTP ..
Re: [blfs-dev] Qt5
On Tue, Jan 15, 2019 at 4:31 PM Roger Koehler wrote: > > Since there is this note: > > -skip qtwebengine: This switch disables building the QtWebEngine. The BLFS > editors have chosen to build qtwebengine-5.12.0 separately. > > Should qtwebengine be listed as a dependency? > > I don't have it installed yet and Qt5 doesn't build: > > ln -s libQt5Network.so.5.12.0 libQt5Network.so > ln -s libQt5Network.so.5.12.0 libQt5Network.so.5 > ln -s libQt5Network.so.5.12.0 libQt5Network.so.5.12 > rm -f ../../lib/libQt5Network.so.5.12.0 > mv -f libQt5Network.so.5.12.0 ../../lib/libQt5Network.so.5.12.0 > rm -f ../../lib/libQt5Network.so > rm -f ../../lib/libQt5Network.so.5 > rm -f ../../lib/libQt5Network.so.5.12 > mv -f libQt5Network.so ../../lib/libQt5Network.so > mv -f libQt5Network.so.5 ../../lib/libQt5Network.so.5 > mv -f libQt5Network.so.5.12 ../../lib/libQt5Network.so.5.12 > make[4]: Leaving directory > '/var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/src/network' > make[3]: Leaving directory > '/var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/src' > make[2]: *** [Makefile:49: sub-src-make_first] Error 2 > make[2]: Leaving directory > '/var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase' > make[1]: *** [Makefile:83: module-qtbase-make_first] Error 2 > make[1]: Leaving directory '/var/lib/sources/qt5/qt-everywhere-src-5.12.0' Probably unrelated. I get the same error if I remove the switch. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] Qt5
Since there is this note: -skip qtwebengine: This switch disables building the QtWebEngine. The BLFS editors have chosen to build qtwebengine-5.12.0 separately. Should qtwebengine be listed as a dependency? I don't have it installed yet and Qt5 doesn't build: ln -s libQt5Network.so.5.12.0 libQt5Network.so ln -s libQt5Network.so.5.12.0 libQt5Network.so.5 ln -s libQt5Network.so.5.12.0 libQt5Network.so.5.12 rm -f ../../lib/libQt5Network.so.5.12.0 mv -f libQt5Network.so.5.12.0 ../../lib/libQt5Network.so.5.12.0 rm -f ../../lib/libQt5Network.so rm -f ../../lib/libQt5Network.so.5 rm -f ../../lib/libQt5Network.so.5.12 mv -f libQt5Network.so ../../lib/libQt5Network.so mv -f libQt5Network.so.5 ../../lib/libQt5Network.so.5 mv -f libQt5Network.so.5.12 ../../lib/libQt5Network.so.5.12 make[4]: Leaving directory '/var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/src/network' make[3]: Leaving directory '/var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase/src' make[2]: *** [Makefile:49: sub-src-make_first] Error 2 make[2]: Leaving directory '/var/lib/sources/qt5/qt-everywhere-src-5.12.0/qtbase' make[1]: *** [Makefile:83: module-qtbase-make_first] Error 2 make[1]: Leaving directory '/var/lib/sources/qt5/qt-everywhere-src-5.12.0' -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] evince-3.30.2
I had to add the following switches to .configure: --without-gspell --disable-nautilus -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] nss 3.41
On Mon, Dec 24, 2018 at 12:14 PM Ken Moffat via blfs-dev wrote: > > On Mon, Dec 24, 2018 at 06:39:47AM -0700, Roger Koehler via blfs-dev wrote: > > Correct link: > > https://archive.mozilla.org/pub/security/nss/releases/NSS_3_41_RTM/src/nss-3.41.tar.gz > > > Thanks for the report, fixed in r20869. > > > Also, it hasn't been copied to > > http://ftp.osuosl.org/pub/blfs/svn/n/nss-3.41.tar.gz (if it had, I > > wouldn't have checked on the link above). > > Copying to there requires manual action, and always happens later - > it might take a few days. In general, trying the link in the > development book (and therefore noticing when that is broken) is > better. True, but in this case, a patch is required. So, at least that needs to be posted for the instructions to work. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] nss 3.41
Correct link: https://archive.mozilla.org/pub/security/nss/releases/NSS_3_41_RTM/src/nss-3.41.tar.gz Also, it hasn't been copied to http://ftp.osuosl.org/pub/blfs/svn/n/nss-3.41.tar.gz (if it had, I wouldn't have checked on the link above). -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] penabled wacom
On Fri, Dec 21, 2018 at 12:01 PM Roger Koehler
wrote:
>
> I have to add the following for my penabled wacom to work, as root:
>
> cat > /etc/udev/rules.d/10-wacom.rules << EOF
> ACTION!="add|change", GOTO="wacom_end"
> # Match all wacom tablets with a serial ID starting with WACf or FUJ*
> ATTRS{id}=="WACf*" ENV{NAME}="Serial Wacom Tablet",
> ENV{ID_INPUT}="1", ENV{ID_INPUT_TABLET}="1"
> ATTRS{id}=="FUJ*" ENV{NAME}="Serial Wacom Tablet",
> ENV{ID_INPUT}="1", ENV{ID_INPUT_TABLET}="1"
> LABEL="wacom_end"
> EOF
For more information, see:
http://www.thinkwiki.org/wiki/Wacom_Serial_Tablet_PC_Stylus#Wacom_Serial_Tablet_PC_Stylus
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
[blfs-dev] penabled wacom
I have to add the following for my penabled wacom to work, as root:
cat > /etc/udev/rules.d/10-wacom.rules << EOF
ACTION!="add|change", GOTO="wacom_end"
# Match all wacom tablets with a serial ID starting with WACf or FUJ*
ATTRS{id}=="WACf*" ENV{NAME}="Serial Wacom Tablet",
ENV{ID_INPUT}="1", ENV{ID_INPUT_TABLET}="1"
ATTRS{id}=="FUJ*" ENV{NAME}="Serial Wacom Tablet",
ENV{ID_INPUT}="1", ENV{ID_INPUT_TABLET}="1"
LABEL="wacom_end"
EOF
--
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
On Thu, Dec 20, 2018, 8:48 AM Thanos Baloukas via blfs-dev < blfs-dev@lists.linuxfromscratch.org 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: > >> 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. 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. The good news is that it now builds for me! Thanks for the help. This is a great list. -- 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
On Sun, Dec 16, 2018, 12:30 PM Brendan L via blfs-dev < blfs-dev@lists.linuxfromscratch.org wrote: > On Sat, Dec 15, 2018 at 6:47 PM Roger Koehler via blfs-dev > 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. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Kernel issues
On Mon, Dec 17, 2018 at 4:22 PM Roger Koehler wrote: > > On Mon, Dec 17, 2018 at 3:21 PM Bruce Dubbs via blfs-dev > wrote: > > > > Requesting help. > > > > I'm rebuilding my laptop with latest development lfs/blfs and am having > > some kernel 4.19.8 issues. > > > > My laptop has both wired and wireless network interfaces. The wired > > interface is fine but the wireless interface is not being recognized. > > > > For kernel 4.13.8, everything is fine. The firmware related kernel > > options are: > > > > CONFIG_PREVENT_FIRMWARE_BUILD=y > > CONFIG_FIRMWARE_IN_KERNEL=y > > CONFIG_EXTRA_FIRMWARE="intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq > > iwlwifi-7260-17.ucode" > > CONFIG_EXTRA_FIRMWARE_DIR="firmware" > > CONFIG_FIRMWARE_MEMMAP=y > > > > and dmesg gives: > > > > [1.516228] Bluetooth: hci0: Intel Bluetooth firmware file: > > intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq > > [1.734116] Bluetooth: hci0: Intel Bluetooth firmware patch completed > > and activated > > [5.077436] iwlwifi :01:00.0: loaded firmware version 17.459231.0 > > op_mode iwlmvm > > > > For 4.19.8 I have: > > > > CONFIG_PREVENT_FIRMWARE_BUILD=y > > CONFIG_EXTRA_FIRMWARE="intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq > > iwlwifi-7260-17.ucode" > > CONFIG_EXTRA_FIRMWARE_DIR="firmware" > > CONFIG_FIRMWARE_MEMMAP=y > > > > There is no CONFIG_FIRMWARE_IN_KERNEL option for this kernel version. > > > > dmesg now gives only: > > > > [0.316853] platform regulatory.0: Direct firmware load for > > regulatory.db failed with error -2 > > > > There are some things I found about something called regdb, but that > > doesn't explain to me why the firmware isn't loading. > > > > Any ideas? > > I'm not much help, but I thought I would chime in and let you know > that I was having similar issues, so I built LFS 8.0 and BLFS 8.0 so > that I could use the longest running stable kernel (currently > 4.9.146). p.s. It is the minor revision currently in use by Debian 9.6. (Projected EOL Jan. 2023) -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Kernel issues
On Mon, Dec 17, 2018 at 3:21 PM Bruce Dubbs via blfs-dev wrote: > > Requesting help. > > I'm rebuilding my laptop with latest development lfs/blfs and am having > some kernel 4.19.8 issues. > > My laptop has both wired and wireless network interfaces. The wired > interface is fine but the wireless interface is not being recognized. > > For kernel 4.13.8, everything is fine. The firmware related kernel > options are: > > CONFIG_PREVENT_FIRMWARE_BUILD=y > CONFIG_FIRMWARE_IN_KERNEL=y > CONFIG_EXTRA_FIRMWARE="intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq > iwlwifi-7260-17.ucode" > CONFIG_EXTRA_FIRMWARE_DIR="firmware" > CONFIG_FIRMWARE_MEMMAP=y > > and dmesg gives: > > [1.516228] Bluetooth: hci0: Intel Bluetooth firmware file: > intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq > [1.734116] Bluetooth: hci0: Intel Bluetooth firmware patch completed > and activated > [5.077436] iwlwifi :01:00.0: loaded firmware version 17.459231.0 > op_mode iwlmvm > > For 4.19.8 I have: > > CONFIG_PREVENT_FIRMWARE_BUILD=y > CONFIG_EXTRA_FIRMWARE="intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq > iwlwifi-7260-17.ucode" > CONFIG_EXTRA_FIRMWARE_DIR="firmware" > CONFIG_FIRMWARE_MEMMAP=y > > There is no CONFIG_FIRMWARE_IN_KERNEL option for this kernel version. > > dmesg now gives only: > > [0.316853] platform regulatory.0: Direct firmware load for > regulatory.db failed with error -2 > > There are some things I found about something called regdb, but that > doesn't explain to me why the firmware isn't loading. > > Any ideas? I'm not much help, but I thought I would chime in and let you know that I was having similar issues, so I built LFS 8.0 and BLFS 8.0 so that I could use the longest running stable kernel (currently 4.9.146). -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] NetworkManager-1.14.2
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. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] gnutls-3.6.5
On Sat, Dec 15, 2018 at 5:14 PM Bruce Dubbs via blfs-dev wrote: > > On 12/15/2018 05:48 PM, Roger Koehler via blfs-dev wrote: > > On Sat, Dec 15, 2018 at 4:30 PM Bruce Dubbs via blfs-dev > > wrote: > >> > >> On 12/15/2018 05:20 PM, Roger Koehler via blfs-dev wrote: > >>> On Sat, Dec 15, 2018 at 3:39 PM Roger Koehler > >>> wrote: > >>>> > >>>> On Sat, Dec 15, 2018 at 3:18 PM Ken Moffat via blfs-dev > >>>> wrote: > >>>>> > >>>>> On Sat, Dec 15, 2018 at 03:06:27PM -0700, Roger Koehler via blfs-dev > >>>>> wrote: > >>>>>> On Sat, Dec 15, 2018 at 2:49 PM Ken Moffat via blfs-dev > >>>>>> wrote: > >>>>>>> > >>>>>>> On Sat, Dec 15, 2018 at 02:06:25PM -0700, Roger Koehler via blfs-dev > >>>>>>> wrote: > >>>>>>>> configure can't file libnettle for some reason. > >>>>>>> > >>>>>>> Have you installed nettle-3.4.1 ? That version is now the minimum > >>>>>>> required - both of them turned out to be affected by the > >>>>>>> side-channel vulnerability, see > >>>>>>> > >>>>>>> http://lists.gnu.org/archive/html/info-gnu/2018-12/msg1.html > >>>>>>> > >>>>>>> I have just installed gnutls-3.6.5 on my most recent system, after > >>>>>>> upgrading nettle. > >>>>>> > >>>>>> I just reinstalled Nettle 3.4.1 following the book. All 3 tests pass. > >>>>>> Tried again. Still same configure error. If I am the only one > >>>>>> experiencing this issue, I'll refrain from posting further. > >>>>> > >>>>> I initially tried building gnutle in /tmp, and the initial NETTLE > >>>>> test failed. Then I built nettle and installed that to /tmp/NETTLE > >>>>> : the initial test for NETTLE passed, but a later test to check for > >>>>> nettle_sec_rsa_decrypt failed because configure was linking to > >>>>> libnettle.so and getting the old system version. > >>>>> > >>>>> So in my case I did a straight upgrade. > >>>>> > >>>>> If yours is still failing in the initial NETTLE test, look at > >>>>> config.log and also look at /usr/lib/pkgconfig/nettle.pc to confirm > >>>>> that the version is indeed 3.4.1. > >>>>> > >>>>> Alternatively, if it fails on the later test, check that > >>>>> /usr/lib/nibnettle.so is a symplink to libnettle.so.6.5 (instead of > >>>>> to 6.4). > >>>> > >>>> Bingo: > >>>> > >>>> libnettle: /usr/lib/libnettle.so /usr/lib64/libnettle.so > >>>> roger [ /var/lib/sources/gnutls/gnutls-3.6.5 ]$ ls -l > >>>> /usr/lib/libnettle.so > >>>> lrwxrwxrwx 1 root root 16 Nov 26 18:45 /usr/lib/libnettle.so -> > >>>> libnettle.so.6.4 > >>>> roger [ /var/lib/sources/gnutls/gnutls-3.6.5 ]$ ls -l > >>>> /usr/lib64/libnettle.so > >>>> lrwxrwxrwx 1 root root 16 Dec 15 15:02 /usr/lib64/libnettle.so -> > >>>> libnettle.so.6.5 > >>>> > >>>> The install only updated one of the links and apparently didn't update > >>>> the pkgconfig files. > >>> > >>> It looks like Nettle 3.4.1 is only installed in /usr/lib64/. Also, the > >>> book tries to chmod in /usr/lib/ and complains because the files don't > >>> exist (I blew away my old installation). Also, even after running > >>> ldconfig, the gnutls configure script is looking for it in /usr/lib/. > >>> So, the files need to be copied to /usr/lib (after running chmod). > >> > >> LFS 6.5. Creating Directories > >> > >> case $(uname -m) in > >>x86_64) mkdir -v /lib64 ;; > >> esac > >> > >> You did not do that? > > > > Yes. I see those instruction in > > /jhalfs/lfs-commands/chapter06/070-creatingdirs > > > Oops, sorry. I was thinking that there was a symlink between /lib and > /lib64. That's obsolete. However, we do not have /usr/lib64 at all. > Something must have incorrectly created that, unless you are building > 32-bit libraries separately. I just built another system using jhalfs with the development books. I'll let you know if I run into the same problem. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] gnutls-3.6.5
On Sat, Dec 15, 2018 at 4:30 PM Bruce Dubbs via blfs-dev wrote: > > On 12/15/2018 05:20 PM, Roger Koehler via blfs-dev wrote: > > On Sat, Dec 15, 2018 at 3:39 PM Roger Koehler > > wrote: > >> > >> On Sat, Dec 15, 2018 at 3:18 PM Ken Moffat via blfs-dev > >> wrote: > >>> > >>> On Sat, Dec 15, 2018 at 03:06:27PM -0700, Roger Koehler via blfs-dev > >>> wrote: > >>>> On Sat, Dec 15, 2018 at 2:49 PM Ken Moffat via blfs-dev > >>>> wrote: > >>>>> > >>>>> On Sat, Dec 15, 2018 at 02:06:25PM -0700, Roger Koehler via blfs-dev > >>>>> wrote: > >>>>>> configure can't file libnettle for some reason. > >>>>> > >>>>> Have you installed nettle-3.4.1 ? That version is now the minimum > >>>>> required - both of them turned out to be affected by the > >>>>> side-channel vulnerability, see > >>>>> > >>>>> http://lists.gnu.org/archive/html/info-gnu/2018-12/msg1.html > >>>>> > >>>>> I have just installed gnutls-3.6.5 on my most recent system, after > >>>>> upgrading nettle. > >>>> > >>>> I just reinstalled Nettle 3.4.1 following the book. All 3 tests pass. > >>>> Tried again. Still same configure error. If I am the only one > >>>> experiencing this issue, I'll refrain from posting further. > >>> > >>> I initially tried building gnutle in /tmp, and the initial NETTLE > >>> test failed. Then I built nettle and installed that to /tmp/NETTLE > >>> : the initial test for NETTLE passed, but a later test to check for > >>> nettle_sec_rsa_decrypt failed because configure was linking to > >>> libnettle.so and getting the old system version. > >>> > >>> So in my case I did a straight upgrade. > >>> > >>> If yours is still failing in the initial NETTLE test, look at > >>> config.log and also look at /usr/lib/pkgconfig/nettle.pc to confirm > >>> that the version is indeed 3.4.1. > >>> > >>> Alternatively, if it fails on the later test, check that > >>> /usr/lib/nibnettle.so is a symplink to libnettle.so.6.5 (instead of > >>> to 6.4). > >> > >> Bingo: > >> > >> libnettle: /usr/lib/libnettle.so /usr/lib64/libnettle.so > >> roger [ /var/lib/sources/gnutls/gnutls-3.6.5 ]$ ls -l /usr/lib/libnettle.so > >> lrwxrwxrwx 1 root root 16 Nov 26 18:45 /usr/lib/libnettle.so -> > >> libnettle.so.6.4 > >> roger [ /var/lib/sources/gnutls/gnutls-3.6.5 ]$ ls -l > >> /usr/lib64/libnettle.so > >> lrwxrwxrwx 1 root root 16 Dec 15 15:02 /usr/lib64/libnettle.so -> > >> libnettle.so.6.5 > >> > >> The install only updated one of the links and apparently didn't update > >> the pkgconfig files. > > > > It looks like Nettle 3.4.1 is only installed in /usr/lib64/. Also, the > > book tries to chmod in /usr/lib/ and complains because the files don't > > exist (I blew away my old installation). Also, even after running > > ldconfig, the gnutls configure script is looking for it in /usr/lib/. > > So, the files need to be copied to /usr/lib (after running chmod). > > LFS 6.5. Creating Directories > > case $(uname -m) in > x86_64) mkdir -v /lib64 ;; > esac > > You did not do that? Yes. I see those instruction in /jhalfs/lfs-commands/chapter06/070-creatingdirs -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] gnutls-3.6.5
On Sat, Dec 15, 2018 at 3:39 PM Roger Koehler wrote: > > On Sat, Dec 15, 2018 at 3:18 PM Ken Moffat via blfs-dev > wrote: > > > > On Sat, Dec 15, 2018 at 03:06:27PM -0700, Roger Koehler via blfs-dev wrote: > > > On Sat, Dec 15, 2018 at 2:49 PM Ken Moffat via blfs-dev > > > wrote: > > > > > > > > On Sat, Dec 15, 2018 at 02:06:25PM -0700, Roger Koehler via blfs-dev > > > > wrote: > > > > > configure can't file libnettle for some reason. > > > > > > > > Have you installed nettle-3.4.1 ? That version is now the minimum > > > > required - both of them turned out to be affected by the > > > > side-channel vulnerability, see > > > > > > > > http://lists.gnu.org/archive/html/info-gnu/2018-12/msg1.html > > > > > > > > I have just installed gnutls-3.6.5 on my most recent system, after > > > > upgrading nettle. > > > > > > I just reinstalled Nettle 3.4.1 following the book. All 3 tests pass. > > > Tried again. Still same configure error. If I am the only one > > > experiencing this issue, I'll refrain from posting further. > > > > I initially tried building gnutle in /tmp, and the initial NETTLE > > test failed. Then I built nettle and installed that to /tmp/NETTLE > > : the initial test for NETTLE passed, but a later test to check for > > nettle_sec_rsa_decrypt failed because configure was linking to > > libnettle.so and getting the old system version. > > > > So in my case I did a straight upgrade. > > > > If yours is still failing in the initial NETTLE test, look at > > config.log and also look at /usr/lib/pkgconfig/nettle.pc to confirm > > that the version is indeed 3.4.1. > > > > Alternatively, if it fails on the later test, check that > > /usr/lib/nibnettle.so is a symplink to libnettle.so.6.5 (instead of > > to 6.4). > > Bingo: > > libnettle: /usr/lib/libnettle.so /usr/lib64/libnettle.so > roger [ /var/lib/sources/gnutls/gnutls-3.6.5 ]$ ls -l /usr/lib/libnettle.so > lrwxrwxrwx 1 root root 16 Nov 26 18:45 /usr/lib/libnettle.so -> > libnettle.so.6.4 > roger [ /var/lib/sources/gnutls/gnutls-3.6.5 ]$ ls -l /usr/lib64/libnettle.so > lrwxrwxrwx 1 root root 16 Dec 15 15:02 /usr/lib64/libnettle.so -> > libnettle.so.6.5 > > The install only updated one of the links and apparently didn't update > the pkgconfig files. It looks like Nettle 3.4.1 is only installed in /usr/lib64/. Also, the book tries to chmod in /usr/lib/ and complains because the files don't exist (I blew away my old installation). Also, even after running ldconfig, the gnutls configure script is looking for it in /usr/lib/. So, the files need to be copied to /usr/lib (after running chmod). -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] gnutls-3.6.5
On Sat, Dec 15, 2018 at 3:18 PM Ken Moffat via blfs-dev wrote: > > On Sat, Dec 15, 2018 at 03:06:27PM -0700, Roger Koehler via blfs-dev wrote: > > On Sat, Dec 15, 2018 at 2:49 PM Ken Moffat via blfs-dev > > wrote: > > > > > > On Sat, Dec 15, 2018 at 02:06:25PM -0700, Roger Koehler via blfs-dev > > > wrote: > > > > configure can't file libnettle for some reason. > > > > > > Have you installed nettle-3.4.1 ? That version is now the minimum > > > required - both of them turned out to be affected by the > > > side-channel vulnerability, see > > > > > > http://lists.gnu.org/archive/html/info-gnu/2018-12/msg1.html > > > > > > I have just installed gnutls-3.6.5 on my most recent system, after > > > upgrading nettle. > > > > I just reinstalled Nettle 3.4.1 following the book. All 3 tests pass. > > Tried again. Still same configure error. If I am the only one > > experiencing this issue, I'll refrain from posting further. > > I initially tried building gnutle in /tmp, and the initial NETTLE > test failed. Then I built nettle and installed that to /tmp/NETTLE > : the initial test for NETTLE passed, but a later test to check for > nettle_sec_rsa_decrypt failed because configure was linking to > libnettle.so and getting the old system version. > > So in my case I did a straight upgrade. > > If yours is still failing in the initial NETTLE test, look at > config.log and also look at /usr/lib/pkgconfig/nettle.pc to confirm > that the version is indeed 3.4.1. > > Alternatively, if it fails on the later test, check that > /usr/lib/nibnettle.so is a symplink to libnettle.so.6.5 (instead of > to 6.4). Bingo: libnettle: /usr/lib/libnettle.so /usr/lib64/libnettle.so roger [ /var/lib/sources/gnutls/gnutls-3.6.5 ]$ ls -l /usr/lib/libnettle.so lrwxrwxrwx 1 root root 16 Nov 26 18:45 /usr/lib/libnettle.so -> libnettle.so.6.4 roger [ /var/lib/sources/gnutls/gnutls-3.6.5 ]$ ls -l /usr/lib64/libnettle.so lrwxrwxrwx 1 root root 16 Dec 15 15:02 /usr/lib64/libnettle.so -> libnettle.so.6.5 The install only updated one of the links and apparently didn't update the pkgconfig files. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] gnutls-3.6.5
On Sat, Dec 15, 2018 at 3:13 PM Bruce Dubbs via blfs-dev
wrote:
>
> On 12/15/2018 04:06 PM, Roger Koehler via blfs-dev wrote:
> > On Sat, Dec 15, 2018 at 2:49 PM Ken Moffat via blfs-dev
> > wrote:
> >>
> >> On Sat, Dec 15, 2018 at 02:06:25PM -0700, Roger Koehler via blfs-dev wrote:
> >>> configure can't file libnettle for some reason.
> >>
> >> Have you installed nettle-3.4.1 ? That version is now the minimum
> >> required - both of them turned out to be affected by the
> >> side-channel vulnerability, see
> >>
> >> http://lists.gnu.org/archive/html/info-gnu/2018-12/msg1.html
> >>
> >> I have just installed gnutls-3.6.5 on my most recent system, after
> >> upgrading nettle.
> >
> > I just reinstalled Nettle 3.4.1 following the book. All 3 tests pass.
> > Tried again. Still same configure error. If I am the only one
> > experiencing this issue, I'll refrain from posting further.
>
> When you figure it out, I think others here will be interested in what
> caused the problem.
>
> For these types of problems you need to dig into what configure is doing
> to isolate the problem. It may be as simple as a
> /usr/lib/pkgconfig/nettle.pc issue.
>
>
> prefix=/usr
> exec_prefix=${prefix}
> libdir=${exec_prefix}/lib
> includedir=${prefix}/include
>
> Name: Nettle
> Description: Nettle low-level cryptographic library (symmetric algorithms)
> URL: http://www.lysator.liu.se/~nisse/nettle
> Version: 3.4.1
> Libs: -L${libdir} -lnettle
> Cflags: -I${includedir}
Interesting. Mine still says 3.4 even after installing 3.4.1. Can I
manually edit this file?
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: [blfs-dev] gnutls-3.6.5
On Sat, Dec 15, 2018 at 2:49 PM Ken Moffat via blfs-dev wrote: > > On Sat, Dec 15, 2018 at 02:06:25PM -0700, Roger Koehler via blfs-dev wrote: > > configure can't file libnettle for some reason. > > Have you installed nettle-3.4.1 ? That version is now the minimum > required - both of them turned out to be affected by the > side-channel vulnerability, see > > http://lists.gnu.org/archive/html/info-gnu/2018-12/msg1.html > > I have just installed gnutls-3.6.5 on my most recent system, after > upgrading nettle. I just reinstalled Nettle 3.4.1 following the book. All 3 tests pass. Tried again. Still same configure error. If I am the only one experiencing this issue, I'll refrain from posting further. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] gnutls-3.6.5
On Sat, Dec 15, 2018 at 2:40 PM Ryan Marsaw via blfs-dev wrote: > > On Sat, 15 Dec 2018, Roger Koehler via blfs-dev wrote: > > > On Sat, Dec 15, 2018 at 2:30 PM Roger Koehler > > wrote: > >> > >> On Sat, Dec 15, 2018 at 2:24 PM Bruce Dubbs via blfs-dev > >> wrote: > >> > > >> > On 12/15/2018 03:06 PM, Roger Koehler via blfs-dev wrote: > >> > > configure can't file libnettle for some reason. > >> > > >> > Try running ldconfig. > >> > >> That's the first thing that I tried. > >> > >> 'whereis libnettle' yields: > >> libnettle: /usr/lib/libnettle.so /usr/lib64/libnettle.so > > > > I am running the script generated by jhalfs blfs_root. > > Log file: > > > > checking for NETTLE... no > > configure: error: > > *** > > *** Libnettle 3.4 was not found. > > -- > > http://lists.linuxfromscratch.org/listinfo/blfs-dev > > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > > Unsubscribe: See the above information page > > What version of nettle are you using? When I first attempted to install > gnutls 3.6.5 I got a configure error stating that nettle version 3.4.1 > was needed. nettle 3.4 was not new enough. I reinstalled Nettle 3.4.1 to be sure. Same configure error. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] gnutls-3.6.5
On Sat, Dec 15, 2018 at 2:30 PM Roger Koehler wrote: > > On Sat, Dec 15, 2018 at 2:24 PM Bruce Dubbs via blfs-dev > wrote: > > > > On 12/15/2018 03:06 PM, Roger Koehler via blfs-dev wrote: > > > configure can't file libnettle for some reason. > > > > Try running ldconfig. > > That's the first thing that I tried. > > 'whereis libnettle' yields: > libnettle: /usr/lib/libnettle.so /usr/lib64/libnettle.so I am running the script generated by jhalfs blfs_root. Log file: checking for NETTLE... no configure: error: *** *** Libnettle 3.4 was not found. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] gnutls-3.6.5
On Sat, Dec 15, 2018 at 2:24 PM Bruce Dubbs via blfs-dev wrote: > > On 12/15/2018 03:06 PM, Roger Koehler via blfs-dev wrote: > > configure can't file libnettle for some reason. > > Try running ldconfig. That's the first thing that I tried. 'whereis libnettle' yields: libnettle: /usr/lib/libnettle.so /usr/lib64/libnettle.so -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] gnutls-3.6.5
configure can't file libnettle for some reason. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] network-manager-applet Command Explanations
"-Denable-wwan=false" should be "-Dwwan=false" -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] gvfs
libusb is required to build gvfs. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] volume-key
SWIG should be added to the list of required packages to build volume-key. It is not optional. Roger -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
