Re: [blfs-dev] Tagging status
Bruce Dubbs wrote: Bruce Dubbs wrote: Bruce Dubbs wrote: We are doing very well for the first weekend after package freeze: lfs81 tags remaining: 518 lfs82 tags : 274 Tickets targeted for 8.2: 34 === As of Tue Feb 20 05:46:29 UTC 2018 lfs81 tags remaining: 457 lfs82 tags : 335 Tickets targeted for 8.2: 20 I have a bunch of multimedia packages ready (~45) to tag, but not tonight. === As of Thu Feb 22 05:07:06 UTC 2018 lfs81 tags remaining: 272 lfs82 tags : 521 Tickets targeted for 8.2: 16 I tried to get the feh and mercurial tickets done today but am still trying to straighten out some issues. Some of these packages require a LOT of dependencies and have substantial circular dependencies if trying to build all the optional deps. Sat Feb 24 22:42:59 CST 2018 lfs81 tags remaining: 199 lfs82 tags : 594 Tickets targeted for 8.2: 13 I finished up kf5 today and will get the kf5-apps and plasma tomorrow. I also plan to do lxde and some other misc packages. A lot of the outstanding packages are systemd related, mostly gnome. DJ and I ran into some problems with java. We can't build junit or freetts. We probably need to update juint to version 4.12. Not sure about freetts and I haven't checked fop or IcedTea-Web. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Report on my issue with gcc include next (missing math.h header)
Hello again, Probably offtopic but I've been on medical leave for a month (starting out on 2nd of February) and one of my symptoms have been a total lack of focusing ability, thus the uncertainty in my report or any subsequent answer. :) Al -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Report on my issue with gcc include next (missing math.h header)
> Ah, so this is all specific to systems where gcc has been rebuilt to > add extra languages, maybe, maybe not, which is why I'm trying to reproduce it under a brand new user account with as few variables defined as possible under which, I downloaded ALFS trunk via svn (ditto with LFS and BLFS). > and then it gave problems with: > > · building mesa > > · building a new LFS That's right. mesa was attempted once but the new LFS was retried many times under different conditions (one LFS built by hand with the only change was to install BLFS gcc with extra languages, another attempt under LFS which was built by ALFS on a debian base) and then some more. > If so, maybe people who rebuild gcc to add extra > languages have some suggestions ? Maybe but on this list, there has been no recent report since I've been registered to this list (~2 months ago). I'll go as far as I can and will ask for backup if needed (most of my work positions have been like that. I take LFS as a job too). Al -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] ptlib issue
There was a problem with ptlib and glibc-2.27. I came up with a sed in addition to the other patches and seds: sed -e '/WCHAR;/s:^://:' \ -e '/UINT;/ s:^://:' \ -e '/limits.h/a #include sqltypes.h' \ -i include/ptlib/unix/ptlib/contain.h I would like to get someone to test it to confirm the it does allow the build to complete. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Report on my issue with gcc include next (missing math.h header)
On Sat, Feb 24, 2018 at 06:10:52PM -0500, Alain Toussaint wrote: > > Is this affecting you because you have recompiled gcc in BLFS (to > > get extra languages) before you got to mesa ? > > > > Yes. I did many tests over the week and tried both mesa, at first, then > building an LFS system (gcc) > with ALFS and by hand. > > I don't know if mesa uses -isystem in its build but gcc does so. > > Alain Ah, so this is all specific to systems where gcc has been rebuilt to add extra languages, and then it gave problems with: · building mesa · building a new LFS Is that correct ? If so, maybe people who rebuild gcc to add extra languages have some suggestions ? ĸen -- Truth, in front of her huge walk-in wardrobe, selected black leather boots with stiletto heels for such a barefaced truth. - Unseen Academicals -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Report on my issue with gcc include next (missing math.h header)
> Is this affecting you because you have recompiled gcc in BLFS (to > get extra languages) before you got to mesa ? > Yes. I did many tests over the week and tried both mesa, at first, then building an LFS system (gcc) with ALFS and by hand. I don't know if mesa uses -isystem in its build but gcc does so. Alain -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] vesa xorg-server driver missing
Tim Tassonis wrote: Hi all I'm just about to build the xorg-server drivers and noticed that the vesa driver has gone from the book. I'm not an expert in xorg and I could successfully start my xserver using the fbdev driver in my qemu vm that I started with vga=std. However, the current vesa driver xf86-video-vesa-2.4.0.tar.gz builds and runs fine with current lfs/blfs. Is there a reason that it got dropped, maybe like there be no actual hardware or virtual environment requring it? We archived the vesa driver three years ago. At the time, the vesa driver was causing the xorg-server to hang. You are the first to mention that it is no longer there since then. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] ntfs-3g-2017.3.23 optional dependency on fuse2
On http://www.linuxfromscratch.org/blfs/view/systemd/postlfs/ntfs-3g.html the 'fuse 2.x' link is external, while fuse2 is in the book. sed -i '/fuse 2.x/c\ ' \ postlfs/filesystems/ntfs-3g.xml -- Thanos -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] vesa xorg-server driver missing
Hi all I'm just about to build the xorg-server drivers and noticed that the vesa driver has gone from the book. I'm not an expert in xorg and I could successfully start my xserver using the fbdev driver in my qemu vm that I started with vga=std. However, the current vesa driver xf86-video-vesa-2.4.0.tar.gz builds and runs fine with current lfs/blfs. Is there a reason that it got dropped, maybe like there be no actual hardware or virtual environment requring it? Bye Tim -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] Report on my issue with gcc include next (missing math.h header)
Hello, For a reminder, this is the issue that I was posting at: http://lists.linuxfromscratch.org/pipermail/blfs-dev/2018-February/033969.html After basic investigation, I saw the issue being reported there on gcc bugzilla marked as WONTFIX: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70129 The issue is with the -isystem /usr/include directive with g++ when it is used to import a C header into the C++ program (in my case, it happen during compilation of g++ itself). The most comprehensive fix would be to replace every occurance of: #include_next (or any other C header ending with *.h) with #include using namespace std (anonymous namespace? I'm not familiar with the concept of namespace). But I have to admit this fix would amount to a massive undertaking if only 25% of the softwares in LFS/BLFS would be fixed. I'm also thinking about my last few attempts at building LFS with a supplementary gcc installation by BLFS method (i.e. C,C++, Fortran, go, objc and objc++) by hand under which I let LFS gcc chapter 5 second installation, chapter 6 installation and BLFS installation enabling bootstraping (I use --enable-bootstrap) because the installation might use precompiled headers, for which the fix is reported here: http://answers.opencv.org/question/183401/gcc7-stdlibh-no-such-file-or-directory-include_next-stdlib h/ I'll try another build tonight switching all precompiled headers off but still bootstraping the build to see if that fix it. Second step would be to drop off the --enable-bootstrap (i.e. -- disable-bootstrap in all case or at least, during all the LFS build steps). Alain -- 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 drivers
Douglas R. Reno wrote: On Fri, Feb 23, 2018 at 10:21 PM, Bruce Dubbs> wrote: I have been trying to finish up tagging xorg today. We still have four drivers to go: x/installing/x7driver-wacom.xml: _checked; x/installing/x7driver-vmware.xml: _built; x/installing/x7driver-amdgpu.xml: _checked; x/installing/x7driver-vmmouse.xml: _built; I have built all of the above and they seem to be fine, but I have no way to test them. Should I just mark all four lfs82_built and move on or is there a way someone has to test them? Wacom and AMDGPU work. Thanks Douglas. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] cyrus-sasl does not support parallel builds
Pierre Labastie wrote: Hi, when building cyrus-sasl (at -j5), I get: --- /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. /include -I../include -DOBSOLETE_CRAM_ATTR=1 -Wall -W -g -O2 -MT db_berkeley.l o -MD -MP -MF .deps/db_berkeley.Tpo -c -o db_berkeley.lo db_berkeley.c gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../include -DOBSOLETE_CRAM_ATTR=1 -Wall -W -g -O2 -MT db_berkeley.o -MD -MP -MF .deps/db_berkeley.Tpo -c -o db_be rkeley.o db_berkeley.c gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../include -DOBSOLETE_CRAM_ATTR=1 -Wall -W -g -O2 -MT allockey.o -MD -MP -MF .deps/allockey.Tpo -c -o allockey.o allockey.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../include -DOBSOLETE_CRAM_ATTR=1 -Wall -W -g -O2 -MT db_berkeley.lo -MD -MP -MF .deps/db_berkeley.Tpo -c db_berkeley.c -fPIC -DPIC -o .libs/db_berkeley.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../include -DOBSOLETE_CRAM_ATTR=1 -Wall -W -g -O2 -MT allockey.lo -MD -MP -MF .deps/allockey.Tpo -c allockey.c -fPIC -DPIC -o .libs/allockey.o mv -f .deps/allockey.Tpo .deps/allockey.Po mv -f .deps/db_berkeley.Tpo .deps/db_berkeley.Po mv -f .deps/db_berkeley.Tpo .deps/db_berkeley.Plo mv: impossible d'évaluer '.deps/db_berkeley.Tpo': Aucun fichier ou dossier de ce type (mv: cannot stat '.deps/db_berkeley.Tpo': No such file or directory) - Sure that if a file is moved, it cannot be moved again. It compiles OK at -j1. Fixed at r19855 It built fine for me a couple of days ago at -j4. Must be a race situation. --- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] xorg drivers
Cyrillo Baggins wrote: Hi, I can confirm both xf86-video-vmware 13.2.1 xf86-input-vmmouse 13.1.0 work fine in VMware workstation 14, if you use libinput, vmmouse driver is not required. Thank you. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] xorg drivers
On Fri, Feb 23, 2018 at 10:21 PM, Bruce Dubbswrote: > I have been trying to finish up tagging xorg today. We still have four > drivers to go: > > x/installing/x7driver-wacom.xml: _checked; > x/installing/x7driver-vmware.xml: _built; > x/installing/x7driver-amdgpu.xml: _checked; > x/installing/x7driver-vmmouse.xml: _built; > > I have built all of the above and they seem to be fine, but I have no way > to test them. Should I just mark all four lfs82_built and move on or is > there a way someone has to test them? > > -- Bruce > -- > http://lists.linuxfromscratch.org/listinfo/blfs-dev > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page > Wacom and AMDGPU work. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] cyrus-sasl does not support parallel builds
Hi, when building cyrus-sasl (at -j5), I get: --- /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. /include -I../include -DOBSOLETE_CRAM_ATTR=1 -Wall -W -g -O2 -MT db_berkeley.l o -MD -MP -MF .deps/db_berkeley.Tpo -c -o db_berkeley.lo db_berkeley.c gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../include -DOBSOLETE_CRAM_ATTR=1 -Wall -W -g -O2 -MT db_berkeley.o -MD -MP -MF .deps/db_berkeley.Tpo -c -o db_be rkeley.o db_berkeley.c gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../include -DOBSOLETE_CRAM_ATTR=1 -Wall -W -g -O2 -MT allockey.o -MD -MP -MF .deps/allockey.Tpo -c -o allockey.o allockey.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../include -DOBSOLETE_CRAM_ATTR=1 -Wall -W -g -O2 -MT db_berkeley.lo -MD -MP -MF .deps/db_berkeley.Tpo -c db_berkeley.c -fPIC -DPIC -o .libs/db_berkeley.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../include -DOBSOLETE_CRAM_ATTR=1 -Wall -W -g -O2 -MT allockey.lo -MD -MP -MF .deps/allockey.Tpo -c allockey.c -fPIC -DPIC -o .libs/allockey.o mv -f .deps/allockey.Tpo .deps/allockey.Po mv -f .deps/db_berkeley.Tpo .deps/db_berkeley.Po mv -f .deps/db_berkeley.Tpo .deps/db_berkeley.Plo mv: impossible d'évaluer '.deps/db_berkeley.Tpo': Aucun fichier ou dossier de ce type (mv: cannot stat '.deps/db_berkeley.Tpo': No such file or directory) - Sure that if a file is moved, it cannot be moved again. It compiles OK at -j1. Fixed at r19855 Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] wayland-protocols and mesa
Hi, On Fri, 23 Feb 2018, Tim Tassonis wrote: Does anybody else use mesa without wayland? I used to for quite some time. The reason for me to start with wayland (and mesa support for it) was gtk4 (3.91.*), which refused to build without at some point. Other packages using wayland now (gtk3, webkitgtk, qt5, vlc) "seemed to have no issues without it" before. Uwe -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page