On Thursday 31 December 2009 05:02:37 pm Bruce Dubbs wrote:
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` ];
On 1/1/10, lux-integ wrote:
I dont seem to have the pathappend utility I keep hetting
'pathappend command not found' on login,
Please refer to BLFS book Chapter 3. After LFS Configuration Issues
The Bash Shell Startup Files where you need to set all that up.
--
-- Forwarded message --
From: linux fan linuxscra...@gmail.com
Date: Fri, 1 Jan 2010 10:49:20 -0500
Subject: Re: Session bus not starting on new LFS
To: cliffhan...@gardener.com
On 12/31/09, cliffhan...@gardener.com cliffhan...@gardener.com wrote:
Remarkable. I've spent some
lux-integ wrote:
On Thursday 31 December 2009 05:02:37 pm Bruce Dubbs wrote:
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
On Friday 01 January 2010 10:40:13 am lux-integ wrote:
I dont seem to have the pathappend utility I keep hetting
'pathappend command not found' on login,
pathappend problem fixed
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ:
2009/12/31 linux fan linuxscra...@gmail.com:
On 12/31/09, Bruce Dubbs wrote:
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.
Right!
But, anyone
Ken Moffat wrote:
http://strace.git.sourceforge.net/git/gitweb.cgip=strace/strace;a=commitdiff_plain;h=f0df31e
The link didn't work for me.
Is this it?
projects / strace/strace / blobdiff
--- a/configure.ac
+++ b/configure.ac
@@ -258,7 +258,7 @@ AC_CHECK_HEADERS([ \
], [], [])
On Thu, 2009-12-31 at 11:42 -0500, cliffhan...@gardener.com wrote:
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
