Re: Xorg7.5/libs and PKG_CONFIG_PATH
The hacky solution is to dump/symlink all your pc files to the same
directory, but that'll break any package management solution you've
got and cause other problems and generally make installing anything a
PITA
This is how I've been setting my PKG_CONFIG_PATH
for pfix in /usr \
${GTK_PREFIX} \
${OTHER_PACKAGE_PREFIX} \
${XORG_PREFIX} \
; do
if [ -z `echo $PKG_CONFIG_PATH | grep $pfix` ]; then
[ -n ${PKG_CONFIG_PATH} ] PKG_CONFIG_PATH=${PKG_CONFIG_PATH}:
export PKG_CONFIG_PATH=${PKG_CONFIG_PATH}${pfix}/lib/pkgconfig
fi
done
But if that's too long and convoluted a recipe, you can just
export PKG_CONFIG_PATH=$XORG_PREFIX/lib/pkgconfig
If that doesn't work for you, can you copy/paste the error message
you're getting in, with the relevant lines before and after? This
package will help with that if you need it
http://www.linuxfromscratch.org/blfs/view/svn/general/gpm.html
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Session bus not starting on new LFS
Hi Maybe someone can help here, if i don't fix this I may as well junk the whole system. I have a new LFS 6.5 plus BLFS as required. Although I can start system dbus in the usual way, a session dbus fails to start as user or root with the following error: 'Failed to start message bus: Element servicedir is not allowed in this context EOF in dbus-launch reading address from bus daemon' I'm starting from ./xinitrc in the standard way: eval `dbus-launch --sh-syntax --exit-with-session` Google gives little, except a mail by me to the dbus mailing list where a gent suggested that 'your /etc/dbus-1/session.conf probably is invalid' But how? I've not touched it, this gets installed by Dbus. BTW just installed Dbus 1.3 - still the same. thanks MAC -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Xorg7.5/libs and PKG_CONFIG_PATH
Hops Error, Line 21, alcoholi.c wrote:
This is how I've been setting my PKG_CONFIG_PATH
for pfix in /usr \
${GTK_PREFIX} \
${OTHER_PACKAGE_PREFIX} \
${XORG_PREFIX} \
; do
if [ -z `echo $PKG_CONFIG_PATH | grep $pfix` ]; then
[ -n ${PKG_CONFIG_PATH} ] PKG_CONFIG_PATH=${PKG_CONFIG_PATH}:
export PKG_CONFIG_PATH=${PKG_CONFIG_PATH}${pfix}/lib/pkgconfig
fi
done
I'd recommend creating a file in /etc/profile.d/ as demonstrated in BLFS
The Bash Shell Startup Files. You could do something like:
cat /etc/profile.d/extrapaths.sh EOF
if [ -d /usr/local/lib/pkgconfig ] ; then
pathappend /usr/local/lib/pkgconfig PKG_CONFIG_PATH
fi
# add other paths as desired
EOF
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: Session bus not starting on new LFS
On 31/12/09 16:42, cliffhan...@gardener.com wrote: Hi Maybe someone can help here, if i don't fix this I may as well junk the whole system. I have a new LFS 6.5 plus BLFS as required. Although I can start system dbus in the usual way, a session dbus fails to start as user or root with the following error: Are you sure dbus-daemon is running? What does ps aux show? Andy -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Steps in BSD format and Linux format in BLFS
Bruce pointed out on the LFS list that tar xf is BSD format tar -xf is short Linux format. So is there any special reason for using the BSD format in the BLFS book? I have found in the most recent release and earlier releases, some possible errors blfs-book-svn-html-2009-12-31.tar.bz2 Linux-PAM tar xf Remove the configuration file created earlier by issuing the following command as the root user: rm -rfv /etc/pam.d This removes the pam.d directory and all the contents. If you don't do this step, you will overwrite the test file several steps later and still have all the config files that were created in between. Which way is correct? I did it both ways and both ways seemed to work. I have a lot more config files in pam.d now than I did the first time. Everything looks right now and works but it did not look right before but worked any way. FreeType2 tar xf On the OpenSSH client page one can see this Chapter 21 – OpenSSH-5.1p1 but the link goes to chapter 19 and not 21 which is the database chapter. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Steps in BSD format and Linux format in BLFS
stosss wrote: Bruce pointed out on the LFS list that tar xf is BSD format tar -xf is short Linux format. So is there any special reason for using the BSD format in the BLFS book? I have found in the most recent release and earlier releases, some possible errors blfs-book-svn-html-2009-12-31.tar.bz2 Linux-PAM tar xf I just fixed this. Note that the tar man file does not even mention BSD type options. The tar info page refers to long (mnemonic) form, short form, and old style. See http://www.gnu.org/software/automake/manual/tar/Old-Options.html Remove the configuration file created earlier by issuing the following command as the root user: rm -rfv /etc/pam.d This removes the pam.d directory and all the contents. If you don't do this step, you will overwrite the test file several steps later and still have all the config files that were created in between. Which way is correct? I did it both ways and both ways seemed to work. Yes the old style usually works, but one of the goals of LFS/BLFS is to teach. Here we want to teach the current methodology. I have a lot more config files in pam.d now than I did the first time. Everything looks right now and works but it did not look right before but worked any way. FreeType2 tar xf Also fixed. On the OpenSSH client page one can see this Chapter 21 – OpenSSH-5.1p1 but the link goes to chapter 19 and not 21 which is the database chapter. Yes, we moved some things around. Fixed. Thanks. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Session bus not starting on new LFS
On 12/31/09, cliffhan...@gardener.com cliffhan...@gardener.com wrote: Hi Maybe someone can help here, if i don't fix this I may as well junk the whole system. I have a new LFS 6.5 plus BLFS as required. Although I can start system dbus in the usual way, a session dbus fails to start as user or root with the following error: 'Failed to start message bus: Element servicedir is not allowed in this context I don't know about everyone else, but I do not do the step: cat /etc/dbus-1/session-local.conf EOF because I never think of a reason for me to create the dir: /usr/local/share/dbus-1/services and maybe that would be a problem. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Strace on recent LFS (dev) build
On 12/28/09, linux fan linuxscra...@gmail.com wrote: On 12/28/09, linux fan wrote: I compiled strace-4.5.18 on a very recent dev lfs build with 2.6.32.2 and no problem. DOH, but I used linux-headers 2.6.31.6. It was SVN-20091124 and then I upgraded kernel to 2.6.32.2. It seems the situation is known, and a regression was attempted but denied http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538372 A proposed patch was said to work http://www.mail-archive.com/debian-bugs-d...@lists.debian.org/msg713804.html -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Strace on recent LFS (dev) build
linux fan wrote: On 12/28/09, linux fan linuxscra...@gmail.com wrote: On 12/28/09, linux fan wrote: I compiled strace-4.5.18 on a very recent dev lfs build with 2.6.32.2 and no problem. DOH, but I used linux-headers 2.6.31.6. It was SVN-20091124 and then I upgraded kernel to 2.6.32.2. It seems the situation is known, and a regression was attempted but denied http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538372 A proposed patch was said to work http://www.mail-archive.com/debian-bugs-d...@lists.debian.org/msg713804.html I hope you don't update the headers when you replace the kernel. That is asking for trouble. Only replace the headers if you are rebuilding glibc -- and that probably means all of LFS. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
BLFS svn book Shadow-4.1.4.2 question about a page note
At the bottom of the page for shadow in the BLFS svn book latest and earlier versions. Is this note talking about a step that was done or needs to be done? Note ENV_SUPATH is no longer supported. You must create a valid /root/.bashrc file to provide a modified path for the super-user. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Linux-PAM step question BLFS svn latest
To test the results, a configuration file must be created. This file will be removed after the tests have completed. Ensure there are no errors produced by the tests before continuing the installation. First create the configuration file by issuing the following commands as the root user: My notes: above it says to create the test config file and after the test the file will be removed. Below you create the file and a directory that will be used later. (or not if you want to go the other way) install -v -m755 -d /etc/pam.d cat /etc/pam.d/other EOF auth required pam_deny.so account required pam_deny.so password required pam_deny.so session required pam_deny.so EOF Now run the tests by issuing make check. Remove the configuration file created earlier by issuing the following command as the root user: rm -rfv /etc/pam.d My notes: The step above removes the directory. My notes: now you get to the configuration after the install and have to put the directory and other file back. Configuring Linux-PAM Config Files /etc/security/* and /etc/pam.d/* or /etc/pam.conf Configuration Information why not just skip the entire rm step above and just overwrite the other file you created earlier. also later in the shadow config steps you over write the other file again. Step from shadow Other Currently, /etc/pam.d/other is configured to allow anyone with an account on the machine to use PAM-aware programs without a configuration file for that program. After testing Linux-PAM for proper configuration, install a more restrictive other file so that program-specific configuration files are required: cat /etc/pam.d/other EOF # Begin /etc/pam.d/other authrequiredpam_deny.so authrequiredpam_warn.so account requiredpam_deny.so account requiredpam_warn.so passwordrequiredpam_deny.so passwordrequiredpam_warn.so session requiredpam_deny.so session requiredpam_warn.so # End /etc/pam.d/other EOF -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
