Re: [blfs-support] xine-ui-0.99.7 build failure
Le 07/04/2014 22:24, Robin a écrit : > On 7 April 2014 19:46, Robin wrote: >> ^ >> network.c: In function ‘main’: >> network.c:1258:39: error: ‘CPPFunction’ undeclared (first use in this >> function) >>rl_attempted_completion_function = (CPPFunction *)completion_function; >>^ >> [...] >> Seems to match https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741847 >> >> Patch was applied. xine-lib-1.2.4, shared-mime-info-1.2, AAlib-1.4rc5 >> and cURL-7.35.0 dependencies installed. >> >> >> Thanks >> >> -- >> rob > > > Changes in readline? > > Just building LVM2, same problem. > > Noticed this in BLFS Version 2014-04-06 LVM2: > > sed -i s/CPPFunction/rl_completion_func_t/ tools/lvm.c > > Some packages are still using functions which have been deprecated in readline since 2004... As of readline 6.3, these function are not available anymore, so the said packages fail... I guess we may expect to find a few other places where this hits... I create a ticket for xine-ui, but do not fix it tonight, it is too late... Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Sudo
Le 04/04/2014 12:27, Fernando de Oliveira a écrit : > Em 04-04-2014 06:24, Pierre Labastie escreveu: >> >>> I go have a look and correct if necessary. >>> >>> Pierre >> Done at r12930. > My script is as the book now. I had that change to be done, probably > more than one update ago, thought had done it. Perhaps it got back > during the discussion about removing libexec, then not doing it for > sudo. But I should have noticed it. Apologies to all. > No big deal, I took it, because I thought you'd prefer update the GNOME packages, rather than correcting a harmless typo... Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Sudo
Le 04/04/2014 11:11, Pierre Labastie a écrit : Le 04/04/2014 10:54, Richard Melville a écrit : On Thu, 03 Apr 2014 6:46:05 PM Richard Melville wrote: > There's an error in the book's suggested configure commands: > --libexecdir=/usr/lib/sudo should be --libexecdir=/usr/lib. Both current > books have this error which surely would produce "two" sudo directories; > one below the other. > > Richard You are incorrect there Richard. I have used those instructions for sudo and it does NOT as you state produce two sudo directories. Maybe we are both right :-) I didn't run make && make install with the book's instructions so I can't confirm that two directories *are* produced. Try running ./configure --help and looking at the maintainers instructions. Christopher I's a fact, however, that if you run --libexecdir=/usr/lib/sudo you *will* receive a warning from the configure script that reads: WARNING: libexecdir should not include the "sudo" subdirectory. Running --libexecdir=/usr/lib does not produce the warning, but still provides the required /usr/lib/sudo. If, as you say, two directories *aren't* produced then the configure script must be compensating for the error. However, it is *still* an error and should be rectified in the book. I go have a look and correct if necessary. Pierre Done at r12930. Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Sudo
Le 04/04/2014 10:54, Richard Melville a écrit : On Thu, 03 Apr 2014 6:46:05 PM Richard Melville wrote: > There's an error in the book's suggested configure commands: > --libexecdir=/usr/lib/sudo should be --libexecdir=/usr/lib. Both current > books have this error which surely would produce "two" sudo directories; > one below the other. > > Richard You are incorrect there Richard. I have used those instructions for sudo and it does NOT as you state produce two sudo directories. Maybe we are both right :-) I didn't run make && make install with the book's instructions so I can't confirm that two directories *are* produced. Try running ./configure --help and looking at the maintainers instructions. Christopher I's a fact, however, that if you run --libexecdir=/usr/lib/sudo you *will* receive a warning from the configure script that reads: WARNING: libexecdir should not include the "sudo" subdirectory. Running --libexecdir=/usr/lib does not produce the warning, but still provides the required /usr/lib/sudo. If, as you say, two directories *aren't* produced then the configure script must be compensating for the error. However, it is *still* an error and should be rectified in the book. I go have a look and correct if necessary. Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] GPM-1.20.7 autogen.sh error
Le 03/04/2014 12:36, Robin a écrit : > I'm just going through LFS 9.3 - extra packages - so am still in chroot. > > The error: > > libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and > libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree. > libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. > configure.ac:43: error: possibly undefined macro: AC_PROG_LIBTOOL >If this token and others are legitimate, please use m4_pattern_allow. >See the Autoconf documentation. > > > Thanks > I have the "libtoolize" lines in my log, but no error. Was in chroot, using LFS 7.5. It does not seem there have been changes in the autotools since 7.5, nor in GPM, so even if you are using development, it should be the same. Are you still using the SVN-LFS-20140331 version? Maybe one of the added packages (acl, attr, libcap,...) has triggered that, since they are built before the autotools. Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] php configure: error: DBA: Could not find necessary header file(s).
Le 29/03/2014 12:53, Pierre Lorenzon a écrit : > > > Hi, > > php : 5.5.10 in svn version of the blfs book. > > I wonder why i get this error since gdbm or things like that > are said to be optional dependencies in the book and not > mandatory. A --disable-dba seems to have no effect when > configuring. > > > So are these databases supports in fact mandatory in which case > the blfs book should be modified at this point or is there a > way to avoid this error even if dbm like things are not > installed ? > > Regards > > Pierre > gdbm is installed in LFS, so we do not mention it in the dependencies. Of course, at least one database manager must be present with the current instructions. If you want to disable totally database support, I think there are switches for doing that. Try "configure --help | less" and look for "dba". I guess you should find that. Of course, you have to remove --with-gdbm. If you try the current svn version of the book, it is possible that the new blfs-bootscripts version has not been packaged yet. You can find it (unpackaged) at: svn co svn//www.linuxfromscratch.org/BLFS/trunk/bootscripts Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Qca-2.0.3 Qca-2.0.3
Le 28/03/2014 18:28, Bruce Dubbs a écrit : > Pierre Labastie wrote: >> Le 28/03/2014 17:31, Bruce Dubbs a écrit : >>> Fernando de Oliveira wrote: >>>> Em 28-03-2014 02:56, m...@pc-networking-services.com escreveu: >>>>> Hello again, >>>>> >>>>> same thing in qca: >>>>> >>>>> ./configure --prefix=$QTDIR >>>>> >>>>> should be: >>>>> >>>>> ./configure --prefix=$QT4DIR \ >>>> Fixed in svn at r12901. >>>> >>>> Thanks. >>>> >>>> This, I changed in Qt4 page in the last days of the package freeze, >>>> IIRC, but did not really knew there was an entity in general.ent that >>>> needed to be modified. This fixes all other you reported and some more. >>>> >>>> Perhaps an entry in the errata for BLFS-7.5 would be necessary, Bruce or >>>> Pierre? >>> OK, I'll take care of it. >>> >>> -- Bruce >>> >> I think I've seen a couple of other things, which could go the the errata: >> - gtk+3 as a dependency of openjdk should be gtk+2 >> - tell either that nss is recommended for openjdk, or to suppress the >> --enable-nss switch (we chose the first in the development book) >> - (minor) tell that the rm command in xorg-fonts should begin with as_root > I'm working on a few other things. Can you provide the wording you want > to see? I can update from that. > > Will do. I need to leave now, so will be back in 2 or 3 hours. I think I have the rights to write to the errata, so I might as well directly write what I think there, unless you prefer me to send it to you first. I could take care of the Qt4 thing too. Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Iced Tea again!!!!!
Le 23/03/2014 18:10, Ken Moffat a écrit : >[long thread] > > > I'm surprised that this now appears to be a systemd issue - I had > assumed that all the pain there would be in replacing bootscripts. > But, the links in other posts seem to bear that out. So, you should > probably look at other distros using systemd - probably fedora and > arch will be your best bets - to see if there is anything relevant > there. Links in : > http://www.linuxfromscratch.org/blfs/view/svn/introduction/beyond.html > > ĸen > Well, systemd has not only changed the way the system boots, it also wants all libraries and executables under /usr. Since the icedtea build system uses hardcoded paths, and some of those paths begin with /bin or /sbin, you need a patch. There is already a patch in the book, which changes some of the paths for building within the LFS layout, but the systemd layout needs more changes... Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Iced Tea again!!!!!
Le 23/03/2014 10:36, m...@pc-networking-services.com a écrit : >>> On Sun, Mar 23, 2014 at 01:01:18PM +1300, m...@pc-networking-services.com >>> wrote: Hello, Well this is ridiculous. I have reached the point after a few days of installing the systemd 7.5 version of LFS, and going through the configuration of quite a number of other packages following BLFS 7.5 stable to the point of having a working graphical interface, so decide now is a good time to install java again. I set everything up as per the instructions, which I did when I first set it up following the previous version of LFS. [...] make/sanity-rules.gmk:71: recipe for target 'post-sanity' failed make[1]: *** [post-sanity] Error 1 make[1]: Leaving directory '/opt/icedtea-2.4.1/openjdk-boot' Makefile:2465: recipe for target 'stamps/icedtea-boot.stamp' failed make: *** [stamps/icedtea-boot.stamp] Error 2 >> [...] > > Hello again, > > I have done some digging around on google and find that this issue was > first reported in JULY last year about people compiling on a SYSTEMD > system. > > Please note right through I have stated SYSTEMD. There does not appear to > be a SYSTEMD version of BLFS. Which would explain why things are not > working as it seems that only ONE developer actually has a systemd version > working, > > In the article I found it states this from, I believe possibly someone who > had been involved in developing for LFS/BLFS at the time: > > > Tushar Teredesai | 31 Jul 17:57 2013 > Re: compiling java on the systemd lfs branch fails > > On Wed, Jul 31, 2013 at 8:59 PM, Nathan Coulson gmail.com> > wrote: >> >> I guess the two choices would be to move those programs back to /bin >> in the systemd branch, patch java in the systemd version to not use >> hardcoded paths, or patch both variations of blfs. >> > > When I first compiled jdk for lfs, I had patched their build system to > use the program versions from PATH instead of hardcoded locations. The > patch may have been dropped at some point. This flexibility of using > commands from the path is useful for lfsers who have their homegrown > package manager which replaces the standard file copy/move commands > with their own logging versions. > > --Tushar. > > > Now I need to ask, where is this patch? I need java working and I need > the patch. > > The link to the BLFS-Dev where this was posted is: > > http://comments.gmane.org/gmane.linux.lfs.beyond.devel/24299 > > I see that Bruce, who seems to still be actively involved did not like the > suggestion of sym-linking, so now I am left with a system that can not be > completed as the INSTRUCTIONS are lacking and incorrect for a SYSTEMD > system. > > Regards, > > Christopher. > Hi Christopher, I understand your frustration, but nobody is in charge of a systemd BLFS version, so you are on your own building BLFS above LFS-systemd. For the issues you have, you may have a look at: http://www.linuxfromscratch.org/patches/downloads/openjdk/openjdk-6-b10-remove_fixed_paths-1.patch as well as the current: http://www.linuxfromscratch.org/patches/downloads/icedtea/icedtea-2.4.5-fixed_paths-1.patch You could also try to see where the various XXX_YYY_PATH variables are defined and change them to all begin with /usr. Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] running lfs as guestOS on virtulisation setup
Le 07/03/2014 16:42, lux-integ a écrit : > I did not know about qemu-img nor qemu-nbd > (Indicently do you know of any documentation on these utilities I can read ? ) > The html documentation shipped with qemu,and the man page for qemu-img are good for qemu-img (I think you need qemu-img convert). For qemu-nbd. I used: http://blog.vmsplice.net/2011/02/how-to-access-virtual-machine-image.html with thesse 2 differences: - I did not use kpartx - the command for disconnection is "nbd-client -d /dev/nbd0". Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] running lfs as guestOS on virtulisation setup
Le 07/03/2014 10:11, lux-integ a écrit : > Greetings, > > I have recently been dabbling with 2 virtualiisation programs on linux. These > are qemu/kvm ( http://www.qemu.org http://www.linux-kvm.org ) and VirtualBox > ( http://www.virtualbox.org ). Both install as host on a typical LFS setup I > use ( cpu =amd64, pure 64bit build, kernel-3.10.something ).. Both have > 'menus' for installing standard linux 'distros' (i.e. from opticalDisks as > guest-OS. BUT I want to use lfs/blfs as a guest. I am spoilt by its stability > and knowing-where-things-are etc.. Here are some questions. to which aswers > and comments to would be welcomed:- > > --Is there a way to install lfs/blfs as guestOS on typcal virtualisation > setups using say qemu or virtualBox? I do not know much about virtualbox, but can give some pointers about qemu: I do not know exactly what you mean with the item above: Do you want to: (i) build LFS/BLFS in the virtual machine, or (ii) just have it as a guest OS, after building it on the host machine? For (i), the best is to install a standard distro on the virtual machine, then build LFS/BLFS with this distro. For (ii), you can: - copy an existing LFS/BLFS to a virtual disk (using for example qemu-img), or - use qemu-nbd to see a virtual disk as a system disk, and build to that disk (you need the nbd kernel module, and the nbd-client utility). > --is it possible to install the guest blfsOS first then install the hostOS > then somehow containorise the guest to run as a user process > I think qemu as a "user" mode, which does just that. I have not much played with it. Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] PHP-5.5.3 configure issue
Le 01/03/2014 19:41, Alexey Orishko a écrit : > On Sat, Mar 1, 2014 at 7:23 PM, Pierre Labastie > wrote: >> Le 01/03/2014 18:24, Alexey Orishko a écrit : >> GDBM (uppercase for gdbm), is built in LFS. We never mention LFS packages in >> the dependencies. QDBM and GDBM are not the same. >> If you have built LFS following the book, the error comes from something >> else. >> >> You may look at config.log to know more. > > I'm building php in chroot after CLFS build. I guess I simply need to > add that part > from LFS book. > By the way, is there any BCLFS book variant? > > Regards, > Alexey > Well, You can also install one of the databases mentioned on the php page (berkeley DB for example), and figure out what the proper switch is (--with-db4). Be aware that the init scripts are rather different in CLFS and LFS. There is a wiki for CBLFS at http://cblfs.cross-lfs.org/index.php/Main_Page BTW, thanks for the heads up concerning the broken link to QDBM site. Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] PHP-5.5.3 configure issue
Le 01/03/2014 18:24, Alexey Orishko a écrit : > Hi guys, > > I'm building php from blfs-7.4 and configure failed with error: > DBA: Could not find necessary header file(s). > It looks the reason for the failure is "--with-gdbm " flag and a lack of QDBM. > > Why is --with-gdbm flag used in php ./configure while QDBM package is > not "required one" and configure fails without it? > > In the php chapter QDBM is listed as > "Optional Data Management Utilities and Libraries" > no version provided neither a correct link to web site. > > I got error - This site has been moved. Correct link is: > http://fallabs.com/qdbm/ > > Regards, > Alexey > > PS. I didn't check upcoming 7.5 book > GDBM (uppercase for gdbm), is built in LFS. We never mention LFS packages in the dependencies. QDBM and GDBM are not the same. If you have built LFS following the book, the error comes from something else. You may look at config.log to know more. Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] CLFS unreachable
Le 25/02/2014 08:40, Pierre Lorenzon a écrit : > Hi All, > > > Sorry for this message whose place is probably not here ! When > clicking on the clfs item from lfs site I get : > >> Cannot retrieve URL: http://cross-lfs.org/ >> 404 Not Found >> -- >> This domain is not configured for this service. Please add it to your >> account. >> -- >> Header information >> W3m-current-url: http://cross-lfs.org/ >> W3m-document-charset: US-ASCII >> HTTP/1.0 404 Not Found >> Date: Tue, 25 Feb 2014 02:58:47 GMT >> Server: Apache/2.2.22 (Ubuntu) >> X-Powered-By: PHP/5.3.10-1ubuntu3.9 >> Set-Cookie: uid=cross-lfs530886200be0e8.25834774; expires=Thu, 27-Mar-2014 >> 02:58:47 GMT >> Vary: Accept-Encoding >> Content-Encoding: gzip >> Content-Length: 101 >> Content-Type: text/html >> Set-Cookie: WEBUK=; Expires=Thu, 01-Jan-1970 00:00:01 GMT; path=/ > >I posted on clfs mailing lists that are surely more suitable >for my request but even if I suscribed to these lists I did >not saw my messages. So I suspect that the site hosting clfs >is something like down and that mailing lists as well are no >longer available. > >Can somebody confirm that the problem does not come from my >system even if I tried from several accounts on my machine >and from another account on another system. Once I'll know >that the origine of the problem is not on my own system I'll >patiently wait that things goes better ! > >Regards > >Pierre This mail seems to be the last on the list: http://article.gmane.org/gmane.linux.lfs.clfs.support/2932 Previous mails geive some indications. Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] BLFS 7.4 boot scripts
Le 31/12/2013 16:05, Pierre Labastie a écrit : > Le 31/12/2013 15:49, Pierre M.R. a écrit : >> The link below looks to be broken: >> >> http://www.linuxfromscratch.org/blfs/downloads/svn/blfs-bootscripts-20130908.tar.bz2 >> >> Does that mean those scripts are banned ? >> >> Pierre >> > If you want to use the 7.4 version of the BLFS book, look at the errata: > http://www.linuxfromscratch.org/blfs/errata/stable/ > > For the bootscripts, you can change /svn/ to /7.4 in the url you have. > > Regards > Pierre > I mean "to /7.4/" -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] BLFS 7.4 boot scripts
Le 31/12/2013 15:49, Pierre M.R. a écrit : > The link below looks to be broken: > > http://www.linuxfromscratch.org/blfs/downloads/svn/blfs-bootscripts-20130908.tar.bz2 > > Does that mean those scripts are banned ? > > Pierre > If you want to use the 7.4 version of the BLFS book, look at the errata: http://www.linuxfromscratch.org/blfs/errata/stable/ For the bootscripts, you can change /svn/ to /7.4 in the url you have. Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] elfutils-0.156 Make Errors
Le 28/12/2013 17:33, Douglas R. Reno a écrit : > > > > On Sat, Dec 28, 2013 at 3:33 AM, Pierre Labastie <mailto:pierre.labas...@neuf.fr>> wrote: > > Le 28/12/2013 04:17, Douglas R. Reno a écrit : > > Hello everyone, > > > > BLFS Version: 7.4 Stable > > LFS Version: 7.3 Stable > > Brief Hardware Description: Intel Pentium III-M, Dell Latitude C800, > 256mb RAM > > > > I get an error while making elfutils. It says something about libdw. Are > there > > any dependencies I am missing? I have libxml2, expat, etc. as required > for > > MesaLib. Here are the errors > > > > gcc -std=gnu99 -Wall -Wshadow -Werror -Wunused -Wextra -Wformat=2 -g > -02 -o > > libdw.so -shared -o libdw.so -Wl,--soname,libdw.so.1,-z,defs \ > > -Wl,--enable-new-dtags,-rpath,/usr/lib/elfutils \ > > -Wl,--version-script,libdw.map,--no-undefined \ > > -Wl,--whole-archive libdw_pic.a ../libdwfl/libdwfl_pic.a > > ../libebl/libebl.a ../libelf/libelf.so -Wl,--no-whole-archive \ > > -ldl -llzma -lbz2 -lz > > if readelf -d libdw.so | fgrep -q TEXTREL; then exit 1; fi > > make[3]: *** [libdw.so] Error 1 > > make[3]: Leaving directory > '/home/renodr/src/p2wget/xc/elfutils-0.156/libdw' > > make[2]: *** [all] Error 2 > > make[2]: Leaving directory > '/home/renodr/src/p2wget/xc/elfutils-0.156/libdw' > > make[1]: *** [all-recursive] Error 1 > > make[1]: Leaving directory '/home/renodr/src/p2wget/xc/elfutils-0.156' > > make: *** [all] Error 2 > I have exactly the same commands in my logs, but they give no error. > > Try to change to /home/renodr/src/p2wget/xc/elfutils-0.156/libdw, run > readelf -d libdw.so, and see where TEXREL occurs (it should not, but it > looks > like it does). > > > > If this helps, I am building as root because I am in a chroot > environment > > attempting to build this. I want to get the X Window System installed > and edit > > /etc/inittab so that it starts twm on startup. I can restart my PC and > logon > > as renodr if needed though. > > I do not think it should change anything, unless you are doing weird > things > with permission or ownerships. Could be the PATH though. Did you enter > chroot > using the command at page 6.66 "Cleaning up"? Are the virtual kernel > filesystems mounted (maybe not needed, but just in case)? > > Pierre > > -- > http://linuxfromscratch.org/mailman/listinfo/blfs-support > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page > > Adding onto my previous post: > > renodr [ ~/src/p2wget/xc/elfutils-0.156/libdw ]$ readelf -d libdw.so | grep > "TEXTREL" > 0x0016 (TEXTREL) 0x0 > 0x001e (FLAGS)TEXTREL > > So it appears that it was built in. > > > Well I do not know what makes textrel pop up. It definitely is not there on my installation (running readelf -d /usr/lib/libdw-0.157.so after installing). But I see that you have an old processor, and that might be the clue. Googling, I found: http://www.akkadia.org/drepper/textrelocs.html (elfutils has been written by U. Drepper, and that explains why he does not like textrel). and http://article.gmane.org/gmane.comp.sysutils.elfutils.devel/1755 (about what you can do to see what is going on). Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] elfutils-0.156 Make Errors
Le 28/12/2013 04:17, Douglas R. Reno a écrit : > Hello everyone, > > BLFS Version: 7.4 Stable > LFS Version: 7.3 Stable > Brief Hardware Description: Intel Pentium III-M, Dell Latitude C800, 256mb RAM > > I get an error while making elfutils. It says something about libdw. Are there > any dependencies I am missing? I have libxml2, expat, etc. as required for > MesaLib. Here are the errors > > gcc -std=gnu99 -Wall -Wshadow -Werror -Wunused -Wextra -Wformat=2 -g -02 -o > libdw.so -shared -o libdw.so -Wl,--soname,libdw.so.1,-z,defs \ > -Wl,--enable-new-dtags,-rpath,/usr/lib/elfutils \ > -Wl,--version-script,libdw.map,--no-undefined \ > -Wl,--whole-archive libdw_pic.a ../libdwfl/libdwfl_pic.a > ../libebl/libebl.a ../libelf/libelf.so -Wl,--no-whole-archive \ > -ldl -llzma -lbz2 -lz > if readelf -d libdw.so | fgrep -q TEXTREL; then exit 1; fi > make[3]: *** [libdw.so] Error 1 > make[3]: Leaving directory '/home/renodr/src/p2wget/xc/elfutils-0.156/libdw' > make[2]: *** [all] Error 2 > make[2]: Leaving directory '/home/renodr/src/p2wget/xc/elfutils-0.156/libdw' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory '/home/renodr/src/p2wget/xc/elfutils-0.156' > make: *** [all] Error 2 I have exactly the same commands in my logs, but they give no error. Try to change to /home/renodr/src/p2wget/xc/elfutils-0.156/libdw, run readelf -d libdw.so, and see where TEXREL occurs (it should not, but it looks like it does). > > If this helps, I am building as root because I am in a chroot environment > attempting to build this. I want to get the X Window System installed and edit > /etc/inittab so that it starts twm on startup. I can restart my PC and logon > as renodr if needed though. I do not think it should change anything, unless you are doing weird things with permission or ownerships. Could be the PATH though. Did you enter chroot using the command at page 6.66 "Cleaning up"? Are the virtual kernel filesystems mounted (maybe not needed, but just in case)? Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] PNGNQ Build Fails
Le 27/12/2013 22:16, Dan McGhee a écrit : > I know this is not specifically a BLFS package, but I'm trying to build > it as an adjunct and helper to GIMP. > > The build fails with: > >> rwpng.c:310:40: error: 'Z_BEST_COMPRESSION' undeclared (first use in >> this function) >> png_set_compression_level(png_ptr, Z_BEST_COMPRESSION); >> ^ >> make[2]: *** [rwpng.o] Error 1 > > because > >> rwpng.c: In function 'rwpng_version_info': >> rwpng.c:52:7: error: 'ZLIB_VERSION' undeclared (first use in this >> function) >>ZLIB_VERSION, zlib_version); >>^ >> rwpng.c:52:7: note: each undeclared identifier is reported only once >> for each function it appears in >> rwpng.c:52:21: error: 'zlib_version' undeclared (first use in this >> function) >>ZLIB_VERSION, zlib_version); >> ^ > > The "config.log" which the executable "config.status" calls in an > command has: > >> 364Configured with: /usr/src/gcc-4.8.1/gcc-4.8.1/configure >> --prefix=/usr --libexecdir=/usr/lib --enable-shared >> --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu >> --enable-languages=c,c++ --disable-multilib --disable-bootstrap >> --disable-install-libiberty --with-system-zlib= I think this line describes the "gcc" configuration options (when you built gcc). It has nothing to do with the switch you passed to configure for this package. > > I used only "--prefix=/usr --libdir=/usr/lib --includedir=/usr/include" > and neither libdir nor includedir got passed. I used those hoping to > help the configure script to find zlib. > > The "config.log" has the following lines containing "zlib." > >> configure:5218: checking for library containing zlibVersion >> /usr/src/pngnq-1.1/pngnq-1.1/conftest.c:43: undefined reference to >> `zlibVersion' >> | char zlibVersion (); >> | return zlibVersion (); >> ac_cv_search_zlibVersion=-lz Well, configure should bomb out when meeting an undefined reference to some zlib object, unless there is a bundled zlib library. > > Looking at line 364 above, the "/usr/src/gcc-4.8.1/gcc-4.8.1/configure" > and the fact that the configure script recognized only the > "--prefix=/usr" switch got my attention. Is this a situation in which > autoconf or autoreconf would work? If so, I don't now how to use those > without following instructions in the book and would need help. Again, this line is just for gcc, so do not worry. > > Another possibility would be for me to edit the line > "ac_cv_search_zlibVersion=-lz" but I would not know what to put in place > of -lz. First try to figure out why configure does not find zlib... > > The "/usr/src/gcc-4.8.1" sequence made me suspect that my Package Users > system was getting in the way. I tried to build pngnq as me and got > exactly the same results in all areas. > > I'd appreciate some pointers. Look at configure around line 5218, and try to see what configure is doing to find zlib (not always easy, because configure scripts are hard to read, but you may find a small program text that you may try to compile, and see what comes out). Also, try to see what the logic is, which leads to setting -lz, while zlib is not found Try building as root. Read the beginning of rwpng.c, trying to see why zlib.h is not included. Yyou might see something like: -- #ifdef SOME_SYMBOL #include then try to find where SOME_SYMBOL is defined. Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Xorg required dep when following links in BLFS
Le 23/12/2013 16:56, Bruce Dubbs a écrit : > akhiezer wrote: >>> From: William Harrington >>> To: BLFS Support List >>> Date: Mon, 23 Dec 2013 04:07:25 -0600 >>> Subject: [blfs-support] Xorg required dep when following links in BLFS >>> >>> Greetings, >>> >>> There is a problem with BLFS and Xorg deps when someone follows the >>> links for required dependencies of Xorg libs. >>> >>> An example: >>> >>> When a user attempts to build WIreshark, the require deps will take >>> them all the way to xorg-proto. >>> >>> I have also been told that util-macros isn't required for xproto. I >>> haven't confirmed, so I won't deal with that here. >>> >>> THe problem is, that when someone is following required dependencies >>> and gets to xorg-proto or util macros, XORG_PREFIX won't be set if >>> they follow dependencies rather than going straight to the Xorg >>> introduction page. >>> >>> xorg-proto ( which has util-macros as required dependency) does not >>> have Xorg introduction as a required dependency where XORG_PREFIX and >>> XORG_CONFIG is set. >>> >>> This is a problem and has been for some time. Users constantly come to >>> support (more irc than the mailing list) with issues regarding >>> libraries and headers not found. Of course, we don't support zombies, >>> but clearly, if you go from top to bottom and then someone decides >>> that they would want to install Xorg dependencies while following >>> required dependency links, they don't get XORG_CONFIG or XORG_PREFIX >>> set. >>> >>> Since the Xorg libs will eventually link the required deps all the way >>> to util-macros as a required dependency of xorg-proto, I think it'd be >>> a suggestion to have the xorg introduction as a dependency of util- >>> macros or xorg-proto or both. >>> >>> A lot of people do follow links rather than know if they want to build >>> some or all of Xorg, and when they do this, they don't get to the Xorg >>> introduction page for Xorg. People can argue all they want that users >>> should know if they want any or all of Xorg installed before building >>> an app that may use a GUI. The problem is that the required dependency >>> chain is broken. I followed Wireshark all the way back to util-macros, >>> and nothing about XORG_PREFIX and XORG_CONFIG was mentioned. >>> >> >> >> Might it be best addressed in blfs chapter 2 or 3, if it's considered to >> be a 'global', 'overview' kind of issue? BLFS users are ~expected to have >> processed those chapters. That would help avoid a lot of repetition >> elsewhere? > > From a practical matter, those sections will be skipped by a lot of > users. Adding the preface matter as a prereq to a couple of packages > seems to be the minimal solution. > >-- Bruce > ISTR that at a time, it was said that any page in the X chapter was a prereq for the following. That explains why the pages are not in alphabetical order. And that's how I implemented it in jhalfs-blfs (same for the KDE chapter, actually). Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] JSON-C fails to build
Le 21/12/2013 16:54, Dan McGhee a écrit : > On 12/21/2013 01:40 AM, Chris Staub wrote: >> I don't normally use json-c, but as I use package users myself I thought >> I'd try it. I got exactly the same build failure when I used "-j4" with >> make, and BLFS does say that this package does not support parallel >> builds. It worked fine once I removed the -j. If it worked as root it's >> probably just because you don't have MAKEFLAGS or something defined as root. > This happened again for me with cdparanoia, which also, as the book > says, does not support a parallel build. I'm not sure how to set, change > or remove these flags. > > Dan > The -j flag for make is either set on the command line (takes precedence) or in MAKEFLAGS. Try "echo $MAKEFLAGS", to see what is in there. If it is empty, well, this is something else. Do you use some kinf of cache (say config.site or so)? MAKEFLAGS is maybe defined there. OTOH, it is always possible to replace "make" with "make -j1", whether in scripts or on the command line. Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Troubles Building NSS-3.15.3 [Corrected Major Error]
Le 06/12/2013 18:12, Dan McGhee a écrit : > On 12/06/2013 02:51 AM, Pierre Labastie wrote: >> Le 05/12/2013 19:21, Dan McGhee a écrit : >>> On 12/05/2013 11:20 AM, Dan McGhee wrote: >>>> This build has failed three times for me. Here is the applicable >>>> portion of the build log: >>>> [What I originally included was an excerpt from my "error" log. I >>>> apologize for the mistake. >>>> [...] >>>>1420 Fatal error: can't create >>>> Linux3.8_x86_64_glibc_PTH_64_OPT.OBJ/pk11cert.o: No such file or >>>> directory >>>>[...] >> This means the directory Linux3.8_x86_64_glibc_PTH_64_OPT.OBJ does not >> exist. >>>>1445 make[2]: *** >>>> [Linux3.8_x86_64_glibc_PTH_64_OPT.OBJ/pk11cert.o] Error 2 >>>>1446 make[2]: *** Waiting for unfinished jobs >>>>1447 pk11load.c: In function 'SECMOD_UnloadModule': >>>>[...] >> You are using job parallelization, aren't you? Delete the build >> directory and start anew without the -j flag. ISTR job parallelization >> is broken for NSS. And the first error really looks like some directory, >> which should have been created before the "long statement", had not... >>> The first time it failed, it failed because it couldn't make the >>> directory. Now it's an object file--as was the second failure. Now I >>> am in need of help, because I don't know how to translate the long >>> statements. >> Regards >> Pierre >> > For some reason I was compiling NSS in my Ubuntu host system using the > chroot environment. Pierre's reference to a parallel build, and since > I wasn't trying to do one, got me looking. Sorry if I was wrong: I read [Linux3.8_x86_64_glibc_PTH_64_OPT.OBJ/pk11cert.o] Error 2 1446 make[2]: *** Waiting for unfinished jobs And I thought that "make" wouldn't have to wait for unfinished jobs if not doing a parallel build. Anyway, glad you found how to compile it. Regards, Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] du on / produces errors from /proc
Le 06/12/2013 10:56, Richard Melville a écrit : > > Le 05/12/2013 18:18, Richard Melville a ?crit : > > Does anybody know what causes the following:- > > > > du: cannot access '/proc/602/task/602/fd/4': No such file or > directory > > du: cannot access '/proc/602/task/602/fdinfo/4': No such file or > directory > > du: cannot access '/proc/602/fd/4': No such file or directory > > du: cannot access '/proc/602/fdinfo/4': No such file or directory > > > > > What were you doing? Building some package? What is the command which > generated that output? > > Regards > Pierre > > > I was just checking disk space with du -sh / as root. That was the > only output apart from the requested disk space. > > Richard > > /proc/602 is a system directory associated to the process number 602. I guess du first finds 602 inside proc when listing the directory /proc, then tries to open it. If 602 is a transcient process (that is it runs for a short time), it may happen that it has disappeared before the second time it is accessed. You may add --exclude=/proc to the command linen but I think it is harmless. Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Troubles Building NSS-3.15.3 [Corrected Major Error]
Le 05/12/2013 19:21, Dan McGhee a écrit : > On 12/05/2013 11:20 AM, Dan McGhee wrote: >> This build has failed three times for me. Here is the applicable >> portion of the build log: >> [What I originally included was an excerpt from my "error" log. I >> apologize for the mistake. > > >> [...] >> 1420 Fatal error: can't create >> Linux3.8_x86_64_glibc_PTH_64_OPT.OBJ/pk11cert.o: No such file or >> directory >> [...] This means the directory Linux3.8_x86_64_glibc_PTH_64_OPT.OBJ does not exist. >> 1445 make[2]: *** >> [Linux3.8_x86_64_glibc_PTH_64_OPT.OBJ/pk11cert.o] Error 2 >> 1446 make[2]: *** Waiting for unfinished jobs >> 1447 pk11load.c: In function 'SECMOD_UnloadModule': >> [...] You are using job parallelization, aren't you? Delete the build directory and start anew without the -j flag. ISTR job parallelization is broken for NSS. And the first error really looks like some directory, which should have been created before the "long statement", had not... > > The first time it failed, it failed because it couldn't make the > directory. Now it's an object file--as was the second failure. Now I > am in need of help, because I don't know how to translate the long > statements. Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] du on / produces errors from /proc
Le 05/12/2013 18:18, Richard Melville a écrit : > Does anybody know what causes the following:- > > du: cannot access '/proc/602/task/602/fd/4': No such file or directory > du: cannot access '/proc/602/task/602/fdinfo/4': No such file or directory > du: cannot access '/proc/602/fd/4': No such file or directory > du: cannot access '/proc/602/fdinfo/4': No such file or directory > > What were you doing? Building some package? What is the command which generated that output? Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] problem using BS or DEL key
Le 04/12/2013 20:38, Alexey Orishko a écrit : > On Wed, Dec 4, 2013 at 7:27 PM, Ken Moffat wrote: >> >> I now wonder if you are using a non-unicode console font ? > > I've built LFS using ALFS scripts and didn't change anything regarding > fonts... should I? ALFS (jhalfs) does not set anything for fonts... It only sets LANG in /etc/profile, which has nothing to do with the keyboard nor with the screen font. That is, you end up with an US keyboard layout and linux default font. If The Norwegian keyboard is different from the US keyboard, you'll get misplaced keys (for example, hitting 'a' on a French keyboard returns 'q'). And the default linux font is not unicode... You need to manually edit /etc/sysconfig/console Some people in this thread have given examples of what they use. Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Trouble with OpenJDK-1.7.0.45/IcedTea-2.4.3 Installation
Le 03/12/2013 14:01, Alan Feuerbacher a écrit : > In installing OpenJDK-1.7.0.45/IcedTea-2.4.3 I've got to the BLFS book's > section "Configuring OpenJDK". I'm confused by the instructions. > > The 1st instruction says: > > > There are now two OpenJDK SDKs installed in /opt. You should decide on > which one you would like to use as the default. For example if you > decide to use the precompiled OpenJDK, do the following as the root user: > > ln -v -nsf OpenJDK-1.7.0.45-bin /opt/jdk This create a symbolic link /opt/jdk-->OpenJDK-1.7.0.45-bin, that is, when you set: > > > The 2nd instruction contains the line "JAVA_HOME=/opt/jdk". JAVA_HOME is actually pointing to /opt/OpenJDK-1.7.0.45-bin Just remove '-bin' if you want to use the just compiled OpenJDK. > > The 3rd instruction has several references to "opt/jdk". > > The 4th instruction has the line "cd /opt/jdk". > > So these instructions assume that somewhere in the instructions above, > the directory "/opt/jdk" has been created. No. /opt/jdk is a pointer to a directory, not a directory itself. > But nowhere above do I see > that directory being created. > > The 1st instruction has you create a link that I don't understand. Since > I want to use the COMPILED OpenJDK, I did not execute the "ln" command. > After things did not work, I experimented and did this: > > mkdir /opt/jdk Do not do that, just the next line (rmdir /opt/jdk first): > ln -v -nsf OpenJDK-1.7.0.45 /opt/jdk > > This created a link in /opt/jdk: "OpenJDK-1.7.0.45 -> OpenJDK-1.7.0.45" > which I don't understand. There are some variations on the ln -s syntax: ln -s , creates a symbolic link inside the directory referred to by , whose name is , and pointing to ... Now: ln -s , creates a symbolic link , pointing to , inside the directory refrred to by path2. If path1 is a relative path, it is relative to path2. So, if the second argument is a path to a directory, it creates something inside it. If it is a path to a non-existent file, it creates that file. I think it fails if the second argument is an already existing file. More information at "man ls". Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Using and Configuring Sudo
Le 21/11/2013 19:45, Dan McGhee a écrit : > This is the first time I have setup and configured 'sudo' in an LFS > build. I'm trying to learn this so that if I add an account for someone > besides me I can set it up. > > I want to be able to run halt, shutdown and reboot without invoking sudo > or su and without using a password. I know I can do this by adding > /sbin to my LFS path, but that would forestall any learning I'm trying > to do. > > I think that the first thing I must do is add aliases to either .bashrc > or .bash_profile for 'sudo reboot' et al. Once I figure out which file > to put that in I think it's just a matter of > > alias= > > Then I need to edit the line "dan ALL=(ALL) ALL" in /etc/sudoers to read: > > dan ALL=(ALL) ALL:NOPASSWD /sbin/halt,/sbin/shutdown,/sbin/reboot > > Am I on the right track? > Hi Dan, I think you want: dan ALL=(ALL) NOPASSWD: /sbin/halt,/sbin/shutdown,/sbin/reboot allows user dan to run only those three commands, without a password or maybe: dan ALL=(ALL) ALL, NOPASSWD: /sbin/halt,/sbin/shutdown,/sbin/reboot allows user Dan to run any command with a password, and the 3 commands without a password. But beware: the first ALL (the one after dan) means that user dan can run the commands when connected from anywhere. Since those commands are for machine maintenance, I would restrict the user to run from the machine. So the beginning before the '=' sign might be: dan dan_machine = Then the (ALL) in parenthesis means that the command can be run as any user. since the default is root, I would suppress that part (I guess you want the commands to be run as root). So the line could eventually be: dan dan_machine = NOPASSWD: /sbin/halt,/sbin/shutdown,/sbin/reboot I suggest you add a file (say 10-dan) in /etc/sudoers.d containing only that line. (If /etc/sudoers.d does not exist, create it as root with mode 550). The file 10-dan should have mode 440, and should belong to root too. Once you have created /etc/sudoers.d, then it is advised to use: su -c 'sudoedit /etc/sudoers.d/10-dan' (if that does not open the editor you like, add EDITOR=/usr/bin/youreditor before sudoedit). Now, if you want user dan to be able to run any command as any user from any host (giving his own password), the file may read: dan dan_machine = NOPASSWD: /sbin/halt,/sbin/shutdown,/sbin/reboot dan ALL=(ALL) ALL Hope it helps Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Xorg-7.7 Does not Detect Input Devices on 64-bit Build
Le 02/11/2013 08:08, John Frankish a écrit : > Ref: Beyond Linux From Scratch - Version 2013-11-01 Part VI. X + Window > Managers > > I built Xorg-7.7 in the same way on the same machine in both 32-bit and > 64-bit versions. > > The 32-bit version works without problems, but the 64-bit version does not > seem to detect the keyboard/mouse. After issuing the "startx" command, the > x-window desktop appears, but the mouse and keyboard are unresponsive and the > only way out is to turn the power off. > > By symlinking the Xorg.0.log to permanent storage and/or using ssh from > another machine, I managed to get the Xorg.0.log (it was identical in both > cases), but it doesn't appear to give many clues (see below). > > Any troubleshooting pointers would be appreciated. > Do you have somthing like: [25.470] (II) LoadModule: "evdev" in the log? If not, It might be that you forgot to compile the evdev driver. (see Xorg drivers page). Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] attr-2.4.47 (attr-2.4.46 too) tests fails
On 02/06/2013 15:56, Mateusz Kaźmierczak wrote: > Welcome, > I built an LFS 7.3 and starting an BLFS. I have an xfs filesystem > on / and ext4 on /home. I enabled in kernel XFS support. When > I try run command "make tests" it's fails. It is good to ignore >these errors and install package? > > Test log is as follows (make tests): > > *** attr.test *** > [...] > [16] $ setfattr -n user. -v value f -- failed > setfattr: f: Zły argument!= setfattr: f: Invalid argument It looks like the tests want error messages in English, and they are emitted in Polish... Try to run them with LANG=C. Also, as explained in the book, the filesystems should support extended attributes, but I cannot tell whether the other errors (those not about error messages) come from that. Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Any application that uses akonadi will not work
Le 24/04/2013 21:47, Niels Terp a écrit : > > > Funny enough, I was just having the same problem. After following the above > akonadi now seems to use sqlite. But I have more akonadi errors: > > "No resource agents found" > > "Current Akonadi server error log found" > > "Previous Akonadi server error log found" > > The two later seems to be connected to the mouse pad, so I don't consider > them serious. But the first one seems to stop all aplications that use the > akonadi service ? > > I do not know much about akonadi, which I just discovered today, because it was sending nasty error messages. the page http://userbase.kde.org/Akonadi was of some help: one way to get some information about what is going on is to launch: akonadictl start You'll get a lot of more or less informative messages. If it tells you that the server is already running, type: akonadictl stop then start again. If the only thing that is missing is some agents, you might want to try to run kmail (*). I think it creates its own agents, for example when you use tools/account wizard. Pierre (*) there are other applications using akonadi, which I have not tried yet: KAddressBook, KOrganizer, Kjots, KAlarm... -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Report on building KDE
Le 24/04/2013 18:35, Bruce Dubbs a écrit : > Armin K. wrote: >> On 04/21/2013 08:19 PM, Pierre Labastie wrote: >>> Conclusion : if you run qemu-kvm with the default VGA emulation, build the >>> cirrus Xorg driver... >>> I guess, you could also set the VM to use VMWare VGA and build the VMWare >>> driver... Not tried (yet). >>> >>> Pierre >>> >> Added Cirrus driver to the book. >> >>From memory, doesn't Qemu use qxl driver? I never used it, since I use >> VMware Player, and its 3D driver is superior to any other available out >> there. > Qemu can use several drivers: > > name "i82559a", bus PCI, desc "Intel i82559A Ethernet" > name "i82559b", bus PCI, desc "Intel i82559B Ethernet" > name "i82559c", bus PCI, desc "Intel i82559C Ethernet" > name "i82550", bus PCI, desc "Intel i82550 Ethernet" > name "i82551", bus PCI, desc "Intel i82551 Ethernet" > name "i82559er",bus PCI, desc "Intel i82559ER Ethernet" > name "i82562", bus PCI, desc "Intel i82562 Ethernet" > name "e1000", bus PCI, desc "Intel Gigabit Ethernet" > name "i82557a", bus PCI, desc "Intel i82557A Ethernet" > name "i82557b", bus PCI, desc "Intel i82557B Ethernet" > name "i82557c", bus PCI, desc "Intel i82557C Ethernet" > name "i82801", bus PCI, desc "Intel i82801 Ethernet" > name "i82558a", bus PCI, desc "Intel i82558A Ethernet" > name "i82558b", bus PCI, desc "Intel i82558B Ethernet" > > But all are intel. I think e1000 is the default. > > -- bruce I think we were talking about graphic card emulations, not network card. Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-support] sqlite and akonadi
Hi, It seems that akonadi wants to use MySQL, even if it is not installed. I found how to disable that: Open ~/.config/akonadi/akonadiserverrc, and leave only: [%General] Driver=QSQLITE3 Then restart akonadi (or any application which is akonadi aware, for example kmail). Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Report on building KDE
Le 24/04/2013 11:59, Armin K. a écrit : > On 04/21/2013 08:19 PM, Pierre Labastie wrote: >> Conclusion : if you run qemu-kvm with the default VGA emulation, build the >> cirrus Xorg driver... >> I guess, you could also set the VM to use VMWare VGA and build the VMWare >> driver... Not tried (yet). >> >> Pierre >> > Added Cirrus driver to the book. > > From memory, doesn't Qemu use qxl driver? I never used it, since I use > VMware Player, and its 3D driver is superior to any other available out > there. Well, do you mean that 2FPS with glxgears is not enough?:-) Qemu can emulate all 3 cards/drivers, depending on the command-line options (never tried VMware actually). But if you do not specify anything, it uses Cirrus. Normally, Cirrus is svga compatible, so the svga driver should be enough, but as you could see, it was unable to draw correctly some windows in the KDE desktop (twm was OK though). Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-support] Report on building KDE
Hi, Just a few informations about building KDE 4.10 with LFS-SVN-20130419. On a virtual machine (qemu-kvm). Building all recommended deps. Everything went rather smoothly. I have not seen the error recently reported in kde-baseapps. So it might be a dependency problem, or a bug in GCC-4.7, corrected in GCC-4.8. OTH, I had to build QJSON (there is a tarball, version 0.8.1, at sourceforge), otherwise, kdepimlibs could not be built. This package should find its way to the book and be marked as required for kdepimlibs (there is a bug report already). The main problem has been that I got very distorted windows when I launched KDE (see http://www.fileswap.com/dl/Hj2gf07KJ/). I tried various things with no success, then noticed in Xorg.log that the server was expecting the cirrus driver. Actually, I had only built 3 xorg drivers: evdev, vesa and fbdev, the last one being useless since I had not built fb support in the kernel... X was therefore using VESA. So I downloaded and built the cirrus driver (simple CMMI, with ./configure $XORG_CONFIG), and the problem was gone. Conclusion : if you run qemu-kvm with the default VGA emulation, build the cirrus Xorg driver... I guess, you could also set the VM to use VMWare VGA and build the VMWare driver... Not tried (yet). Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Building X with GCC-4.8.0 on a x86_64 machine
Le 02/04/2013 19:50, NP a écrit : > Hi, > > Tried to build X on a brand new LFS SVN-20130329 base > (Linux-3.8.4/GCC-4.8.0) with x86_64 architecture. > > Got build errors with 2 packages in the Xorg applications : > - luit-1.1.1 > - xmodmap-0.7.0 > > In both cases the reported error was "implicit declaration of function". > I had to add #define _GNU_SOURCE (above other #define statements) in > sys.c for luit and in xmodmap.c for xmodmap to remove the errors. > With LFS-SVN-20130403, I got the same errors with luit and xmodmap. Actually, they are warnings treated as errors. I added --disable-selective-werror to the configure switches, and could build them. Maybe we could use that until upstream fixes it. Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] My current desktop packages
Le 16/04/2013 13:47, LM a écrit : > > Ken Moffat wrote: > > LFS itself took about 3 hours. > > That is very impressive. Was experimenting with a build of just gcc > over the weekend and that took 4 hours by itself. Didn't try the -j > option. Some of the systems I've tried it on just locked up with it. > I try to maintain a list of packages who do not accept the -j option, for jhalfs (actually, not tested for a while). All I have is: BLACK_LIST="attr autoconf coreutils dejagnu gettext gperf groff man-db vim" attr and gperf are for the systemd branch. Only the tests actually need -j1, as well as for coreutils and vim. For the others, I have not tested for a while, but they do not take long anyway. All the LFS packages not listed in $BLACK_LIST build fine on linux with -jX (X=3..15, tried quite a few distributions on virtual machines, both 32 et 64 bit, on two 64 bit hosts, one with a core i5 at 2,6 GHz, and the other one with two quadcore CPU, Xeon E5620 at 1,6 Ghz with hyperthreading). FWIW, a full 7.3 build on a bi-processor Xeon E5620 (quad core) at 1,6 GHz with -j5 took ~2 h, running only the toolchain tests (chapter 6 glibc, binutils, gmp, mpfr, mpc and gcc). With -j5, gcc took 31 mn, build, test, install. I have almost the same timings with a core i5 at 2,6 GHz (slightly faster actually). Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Guile-2.0.7 build failed
Le 01/04/2013 19:41, Fernando de Oliveira a écrit : > In one of my systems, LFS7.0 "svn", failed to build. Log attached. > Below, log tail. > > I would like to understand the problem. > > Can't it be related to the errors/warnings above in your log about pairs.c when "SNARFing" pairs.doc? What happens if some file in the long 'cat' is missing for example? Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] ntp depends on libcap2 when use "-u" option.
Le 11/03/2013 15:01, xinglp a écrit : > 2013/3/11 Armin K.: >> On 03/11/2013 03:57 AM, xinglp wrote: >>> We just need to install libcap2 before ntp, and it will auto detect. >>> >> Thanks for the info. I had libcap2 present at build time since I install >> it early so I didn't notice. I've been using -u ever since. > You can verify it by run 'ldd $(which ntpd)|grep libcap'. > BTW: Where can I get the information of a package is need by others > and vice-versa in some other distro. > On distros based on Debian (that is Ubuntu, Knoppix...), I launch aptitude, then I look for the package (type / as a shortcut, then the name of the package). then type return when the name of the package you seek is highlighted. You get some information about the package, one of which is the dependencies (Depends). For example, for ntp, it lists: adduser libc6 libcap2 libedit2 libopts25 libssl1.0.0 lsb-base netbase --- It also lists which packages depend on the one you are looking at. In case you do not know which package owns a specific file, you can use 'apt-file search'. To install apt-file: > sudo apt-get install apt-file > sudo apt-file update You cannot get all the build dependencies this way. 'apt-build info' seems to do the trick, but I do not have much experience with it. Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Firefox 18.0.1 users
Le 05/02/2013 18:14, alex lupu a écrit : > The wait is over. 18.0.2 is finally out! > > For a full (and definitive) coverage of the whys and wherefores of > these point releases you can refer to the last post in the > BLFS-support thread, "Firefox 16.0.1 users", cca. Oct 27, 2012. > (if available - sometime after the move). It is there : http://article.gmane.org/gmane.linux.lfs.beyond.support/45132 Cheers Pierre PS : I do not endorse the "full (and definitive)" statement :-) -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] ftp client question
On 27/01/2013 15:55, lux-integ wrote: > Greetings > > I need to transfer a few tBytes of data between two machines. Both have > vsftpd installed. I assumed that both had an ftp client as ftp was > part of one of the core programs of LFS/CLFS. Having set-up vsftpd (server) > on the source-machine, on the destination-machine > at shell prompt I typed :- > > ftp user@othermachine.domain > > only to find I have no 'ftp (i.e. client) executible'. > > I have sftp but since it is only data between two neighbouring machines I > thought a simple even if insucure > method would suffice. Advice and suggestions on available ftp clients would > be much appreciated. > > > Thanks in advance > luxInteg ftp (the client) is installed by ineutils in LFS (do not know whether CLFS has it). It is in /usr/bin. I checked on my installation of LFS/BLFS: it is there. Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
