Re: [blfs-support] LLVM lib path
On 01/06/2013 08:51 AM, Simon Geard wrote: A curious question, for anyone who might know. Why, in the LLVM instructions, do we go to such lengths to put all the libraries in a subdirectory of /usr/lib, only to add an entry to ld.so.conf to ensure everything can find them? I ask because I missed that last bit without noticing at the time, only to have some other package try and run clang and fail with library loading issues. And neither the book, nor the patch offers any explanation of why we want to fix installation paths for libraries. Note - I'm aware that the patch also fixes the locations of stuff in /etc and /usr/share/doc, no problem there. It's just the reasons for forcing everything into /usr/lib/llvm that has me puzzled. Simon. Well, I guess answer is simple. We didn't want to polute /usr/lib with ~100 static libraries which are only used by programs that use LLVM. Entry to ld.so.conf is added because there are few shared libraries, ensuring that they can be loaded at runtime. Some time ago, LLVM was installed into /opt/llvm by default because of mentioned reason, but we agreed to install it into /usr hierarchy - just changed the libdir. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] CPU frequency control
Ken Moffat wrote: On Sat, Jan 05, 2013 at 05:30:43PM -0500, Baho Utot wrote: As for cpu frequency, I think that mine is by default set to ondemand on this machine. Just loading the module or building it into the kernel won't suffice. Please note that I don't build the driver as a module. For my x86_64 machines I've always used ondemand and just set up a bootscript. The following is what I'm using for LFS-7.2. On a multiprocessor system it needs to be repeated for each cpu [ cpu0..3 in my case ]. #!/bin/sh . /lib/lsb/init-functions case ${1} in start|demand) log_info_msg Enabling ondemand cpu frequency echo ondemand /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor evaluate_retval ;; powersave) log_info_msg Enabling powersave cpu frequency echo powersave /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor evaluate_retval ;; performance) log_info_msg Enabling performance cpu frequency echo performance /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor evaluate_retval ;; *) echo Usage: ${0} {start|demand|powersave|performance} exit 1 ;; esac I wasn't intending show you my code to modify this after it has been copied in, because it is really ugly, but in the end it's easier to show it as one way which works to copy and alter the relevant lines. The debugging info is there in case it fails - only ever tested with 4 CPUs. # if more than 1 cpu, replicate for all of them - print debug info while it checks echo -n searching to see if more than one cpu... let EXTRACPUS=`cat /proc/cpuinfo | grep MHz | wc | awk '{ print --$1 }'` if [ $EXTRACPUS -gt 0 ]; then echo yes PREV=0 THIS=1 echo entering loop for $EXTRACPUS pass(es), copying $PREV to $THIS while [ $EXTRACPUS -gt 0 ]; do echo adding cpufreq for processor $THIS sed -i /cpu$PREV/s/\(^.*\)$PREV\(.*$\)/\1$PREV\2\n\1$THIS\2/g \ /etc/rc.d/init.d/cpufreq # let returns zero for non-zero result and vice versa let PREV=$PREV+1 let THIS=$THIS+1 let EXTRACPUS=$EXTRACPUS-1 echo debug, after this pass values are $EXTRACPUS $PREV $THIS done fi My old ppc64 was much more involved - had to load powernowd to be able to control the frequency. I'll also note that you can specify a default governor in the kernel. ĸen In the kernel source code there is a app called cpupower that one just needs to build. It can then be used as a user not root to set what ever governor that you want. This could be included on the kernel build page or made standalone. the cpupower app just requires cpupower frequency-set -g governor and it sets for all cpu cores, you can also change on the fly. One just needs the governor modules loaded or built into the kernel for this to work. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] CPU frequency control
Bruce Dubbs wrote: Baho Utot wrote: I was looking for the edguide as a pdf, not the BLFS. I would be nice to known if the ebook reader could handle the BLFS.pdf though. Here you go: http://anduin.linuxfromscratch.org/~bdubbs/ There are lots of warnings for line or page overflow. -- Bruce Ok but this warning I can not get around. Not Found The requested URL /~bdubbs/edguide/ was not found on this server. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] CPU frequency control
Baho Utot wrote: Bruce Dubbs wrote: Baho Utot wrote: I was looking for the edguide as a pdf, not the BLFS. I would be nice to known if the ebook reader could handle the BLFS.pdf though. Here you go: http://anduin.linuxfromscratch.org/~bdubbs/ There are lots of warnings for line or page overflow. -- Bruce Ok but this warning I can not get around. Not Found The requested URL /~bdubbs/edguide/ was not found on this server. I didn't update that, the only valid link is the pdf version of blfs. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-support] systemd - udev - bewilderment
I'm in the same position as Ken Moffatt was on 2012.08.21. Problems with gudev in udev-lfs-188, and for the same reason: I'm trying to build gudev so I can build colord for cups. Well, I'm getting different error messages: begin excerpted text lfsdev@holland: /sources/systemd-193 = make -f udev-lfs-188/Makefile.lfs keymap CC src/shared/log.c In file included from src/shared/log.c:34:0: src/shared/missing.h:87:6: warning: HAVE_DECL_PIVOT_ROOT is not defined [-Wundef] src/shared/missing.h:185:6: warning: HAVE_DECL_GETTID is not defined [-Wundef] src/shared/missing.h:222:8: error: redefinition of 'struct file_handle' In file included from /usr/include/fcntl.h:32:0, from src/shared/log.c:26: /usr/include/bits/fcntl.h:251:8: note: originally defined here In file included from src/shared/log.c:34:0: src/shared/missing.h:228:19: error: conflicting types for 'name_to_handle_at' In file included from /usr/include/fcntl.h:32:0, from src/shared/log.c:26: /usr/include/bits/fcntl.h:324:12: note: previous declaration of 'name_to_handle_at' was here In file included from src/shared/log.c:34:0: src/shared/missing.h:237:6: error: #error neither secure_getenv nor __secure_getenv are available end excerpt Here's my present situation: [1] I built LFS 7.2 and then a bunch of BLFS stuff, enough to get me a working LXDE and now I've just started on the path to LibreOffice [2] In LFS 7.2, I built udev from systemd-193, not -188. I don't have notes from that day's build activities. [3] Today, I downloaded udev-lfs-188-3.tar.bz2, unpacked, and put the whole tree into systemd-193 remaining from my LFS build. Now, supposing this is all wrong, what should I do to fix it? Redo the LFS 6.61 chapter with a different systemd? -- Regards Jim Michmerhuizenhttp://michmer.net Actions speak louder than words ... but not as clearly -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] systemd - udev - bewilderment
On 01/07/2013 12:58 AM, Jim Michmerhuizen wrote: I'm in the same position as Ken Moffatt was on 2012.08.21. Problems with gudev in udev-lfs-188, and for the same reason: I'm trying to build gudev so I can build colord for cups. Well, I'm getting different error messages: begin excerpted text lfsdev@holland: /sources/systemd-193 = make -f udev-lfs-188/Makefile.lfs keymap CC src/shared/log.c In file included from src/shared/log.c:34:0: src/shared/missing.h:87:6: warning: HAVE_DECL_PIVOT_ROOT is not defined [-Wundef] src/shared/missing.h:185:6: warning: HAVE_DECL_GETTID is not defined [-Wundef] src/shared/missing.h:222:8: error: redefinition of 'struct file_handle' In file included from /usr/include/fcntl.h:32:0, from src/shared/log.c:26: /usr/include/bits/fcntl.h:251:8: note: originally defined here In file included from src/shared/log.c:34:0: src/shared/missing.h:228:19: error: conflicting types for 'name_to_handle_at' In file included from /usr/include/fcntl.h:32:0, from src/shared/log.c:26: /usr/include/bits/fcntl.h:324:12: note: previous declaration of 'name_to_handle_at' was here In file included from src/shared/log.c:34:0: src/shared/missing.h:237:6: error: #error neither secure_getenv nor __secure_getenv are available end excerpt Here's my present situation: [1] I built LFS 7.2 and then a bunch of BLFS stuff, enough to get me a working LXDE and now I've just started on the path to LibreOffice [2] In LFS 7.2, I built udev from systemd-193, not -188. I don't have notes from that day's build activities. [3] Today, I downloaded udev-lfs-188-3.tar.bz2, unpacked, and put the whole tree into systemd-193 remaining from my LFS build. Now, supposing this is all wrong, what should I do to fix it? Redo the LFS 6.61 chapter with a different systemd? You can try using udev-lfs-193.tar.bz2 from http://anduin.linuxfromscratch.org/sources/other/ It's funny how things always break when you do something on your own. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] systemd - udev - bewilderment
On 1/6/2013 5:58 PM, Jim Michmerhuizen wrote: I'm in the same position as Ken Moffatt was on 2012.08.21. Problems with gudev in udev-lfs-188, and for the same reason: I'm trying to build gudev so I can build colord for cups. Well, I'm getting different error messages: [snip] I built LFS-SVN-20121208 using systemd-196. Later I used the same systemd package to build gudev during BLFS stuff. The build was fine. No issues. Here are the files that were installed: /usr/include/gudev-1.0 /usr/include/gudev-1.0/gudev /usr/include/gudev-1.0/gudev/gudev.h /usr/include/gudev-1.0/gudev/gudevclient.h /usr/include/gudev-1.0/gudev/gudevdevice.h /usr/include/gudev-1.0/gudev/gudevenumerator.h /usr/include/gudev-1.0/gudev/gudevenums.h /usr/include/gudev-1.0/gudev/gudevenumtypes.h /usr/include/gudev-1.0/gudev/gudevtypes.h /usr/lib/girepository-1.0/GUdev-1.0.typelib /usr/lib/libgudev-1.0.so /usr/lib/libgudev-1.0.so.0 /usr/lib/libgudev-1.0.so.0.1.2 /usr/lib/pkgconfig/gudev-1.0.pc /usr/share/gir-1.0/GUdev-1.0.gir /usr/share/gtk-doc/html/gudev /usr/share/gtk-doc/html/gudev/GUdevClient.html /usr/share/gtk-doc/html/gudev/GUdevDevice.html /usr/share/gtk-doc/html/gudev/GUdevEnumerator.html /usr/share/gtk-doc/html/gudev/annotation-glossary.html /usr/share/gtk-doc/html/gudev/api-index-deprecated.html /usr/share/gtk-doc/html/gudev/api-index-full.html /usr/share/gtk-doc/html/gudev/gudev-hierarchy.html /usr/share/gtk-doc/html/gudev/gudev.devhelp2 /usr/share/gtk-doc/html/gudev/home.png /usr/share/gtk-doc/html/gudev/index.html /usr/share/gtk-doc/html/gudev/index.sgml /usr/share/gtk-doc/html/gudev/ix02.html /usr/share/gtk-doc/html/gudev/left.png /usr/share/gtk-doc/html/gudev/ref-API.html /usr/share/gtk-doc/html/gudev/right.png /usr/share/gtk-doc/html/gudev/style.css /usr/share/gtk-doc/html/gudev/up.png I'm not sure this helps any, but just wanted to mention that my build of gudev was uneventful. Colord and Cups built fine. -- Randy -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] systemd - udev - bewilderment
On 01/06/2013 07:46 PM, Randy McMurchy wrote: I built LFS-SVN-20121208 using systemd-196. Later I used the same systemd package to build gudev during BLFS stuff. The build was fine. No issues. Yep, that's what I needed to hear. I'll get to it tomorrow then -- and report back to the list. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] systemd - udev - bewilderment
On Sun, Jan 06, 2013 at 06:58:12PM -0500, Jim Michmerhuizen wrote: I'm in the same position as Ken Moffatt was on 2012.08.21. Problems with gudev in udev-lfs-188, and for the same reason: I'm trying to build gudev so I can build colord for cups. The systemd/udev build appears to be sorted now - I think Armin has debugged all the various problems in the LFS Makefiles. The main thing is that there is no good reason to use a different version of systemd/udev in BLFS than what you used in LFS. And use the latest lfs tarball for that version. I'm using 188 with udev-lfs188-3 at the moment [ I haven't built a base LFS newer than 7.2 ] and it builds fine. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] systemd - udev - bewilderment
On Mon, Jan 07, 2013 at 01:15:33AM +, Ken Moffat wrote: The systemd/udev build appears to be sorted now - I think Armin has debugged all the various problems in the LFS Makefiles. The main thing is that there is no good reason to use a different version of systemd/udev in BLFS than what you used in LFS. And use the latest lfs tarball for that version. Ah, I failed to notice that for some reason you used a newer systemd. Use the latest *matching* lfs tarball - presumably, the one you used when building LFS. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] systemd - udev - bewilderment
Ken Moffat wrote: On Sun, Jan 06, 2013 at 06:58:12PM -0500, Jim Michmerhuizen wrote: I'm in the same position as Ken Moffatt was on 2012.08.21. Problems with gudev in udev-lfs-188, and for the same reason: I'm trying to build gudev so I can build colord for cups. The systemd/udev build appears to be sorted now - I think Armin has debugged all the various problems in the LFS Makefiles. The main thing is that there is no good reason to use a different version of systemd/udev in BLFS than what you used in LFS. And use the latest lfs tarball for that version. Correct. But, without trying it, I think udev can be updated in place. You just need to follow the LFS instructions for the base install and the BLFS instructions for keymap, gudev, and gogject files. The important part is not to mix versions. There is text in BLFS: --- Udev-Installed LFS Version: If you installed LFS from SVN-20120719, LFS-7.2, or later, use udev-extras (from systemd) instead of this page. Unlike any other package in the BLFS book, there is no set version of Udev specified to download. Several version updates to LFS and none to BLFS means there are probably many different versions of Udev on the platforms that BLFS is being built upon. Therefore, you should download and use the version of Udev your computer currently uses. Udev Extras (from systemd): ...you should download and use the version of systemd your computer currently uses. Udev Extras Dependencies Required http://anduin.linuxfromscratch.org/sources/other/ (match the udev-lfs-???.tar.bz2 tarball version to the systemd version used in LFS). What extra clarification is needed? -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-support] iptables
I couldn't access the archives, so I thought I would go ahead and ask. Why did the iptables bindir get changed from /sbin to /usr/bin? It sure seemed to add quite a bit to the install step. Also, I didn't need the LDFLAGS doing an upgrade. I suspect that was just because the libraries already existed. Although I did need to use a sed before doing 'make install'. sed -i 's/-dm0755/-d -m0755/' iptables/Makefile Looks like just a typo in the file. I wouldn't have caught it but one of my machines uses Benkmann's package user management. richard GET FREE SMILEYS FOR YOUR IM EMAIL - Learn more at http://www.inbox.com/smileys Works with AIM®, MSN® Messenger, Yahoo!® Messenger, ICQ®, Google Talk™ and most webmails -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page