Re: [blfs-support] Time discrepency LFS 7.2 64bit/BLFS various
On Mon, 7 Oct 2013 09:50:10 +0100, Richard Melville wrote: > Slightly off topic: can anybody say how much of the post title has to > change before it's considered a different thread. I ask this because I > noticed right at the beginning that I had misspelt "discrepancy". I > didn't want to change it in case it messed up the thread; OK, call me a > pedant. A sensible MUA will ignore the Subject header and just look at things like the In-Reply-To and Message-ID headers. On a related note, that's why it's generally frowned upon to start a new thread by replying to an existing one, then deleting all the content and changing the subject line. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Usb error on boot/ or insert
On Wed, 13 Mar 2013 01:19:53 +, Ken Moffat wrote: > Try 3.8.3-rc, it has a patch for ehci which mentions a problem with > via hardware. If I've scrawled this correctly (no copy/paste in > console on this laptop) it's from Alan Stern, USB: EHCI: revert "ASS/PSS > polling timeout", upstream commit 221f8dfca89276d8 ... Well spotted, that man! The patch is available at http://lkml.indiana.edu/hypermail/linux/kernel/1303.1/02649.html in Greg's split-out patch-review thread. Ta, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Configure makes empty makefiles
On Thu, 3 Jan 2013 03:24:13 +, Ken Moffat wrote: > There were some interesting comments on (cheap) solid-state > (internal) drives on The Register in the last couple of weeks - > basically, many (used as system drives in windows, in most reports) > died suddenly with exotic failures. Other people had no problems, > so partly these failures involve bad luck (buying the equivalent of > what we used to call a "friday afternoon car" - one rushed through > without any attention - back in the 1970s when we had a car industry > in the UK). OT: The car industry (Nissan) in Sunderland appears to be doing fairly well. I know it's relatively close to Scotland, but it hasn't been devolved just yet :-) Cheers, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Configure makes empty makefiles
On Wed, 2 Jan 2013 03:22:14 -0500, Alexander Spitzer wrote: > The configure command runs with no errors. Running the make command > however, gives the error no targets stop. Examining the makefile reveals > that it is empty! I'd expect it to have given a slew of errors if this really was the problem, but the only thing I can think of that may cause this is a lack of disk space. Admittedly, that's a pretty unlikely scenario, to have just enough room to untar the package, but then not enough for it to write the Makefiles. Is there anything useful in config.log? Thanks, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Libre Office 3.5.3 with Gcc 4.7 on i686
On Wed, 6 Jun 2012 12:21:02 +0100, Andrew Benton wrote: > I have previously built Libre Office 3.5.3 on i686 with Gcc 4.7, what > was different this time was that I used a git pull of the Gcc 4.7 > branch. Ie, Gcc had changes that had been checked into the Gcc 4.7 > branch since gcc-4.7.0 was released. The ICE is definitely a bug in GCC, so should be reported upstream (I did a quick search at http://gcc.gnu.org/bugzilla/ for force_move_args_size_note and didn't get any hits). There's useful info at http://gcc.gnu.org/bugs/#detailed as to what they'd expect your report to contain. As you're using git, I'm sure they'd be more than happy if you could do a 'git bisect' to see which commit broke things, but given how long it takes to compile GCC, I'm not sure I'd have the patience for that. Good luck! Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] soprano and redland problem
On Wed, 18 Apr 2012 10:11:40 -0400, "david daugherty" wrote: Please stop sending this message, that's 4 that have gone to everyone on the list already. Thanks, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] what`s wrong here
On Mon, 23 Jan 2012 14:33:38 +0100, Matijn Woudt wrote: > On Mon, Jan 23, 2012 at 2:29 PM, Dmitry Blum wrote: >> LLVM 3.0 >> >> >> make[3]: Entering directory `/xc/llvm-3.0.src/lib/Target/X86' >> llvm[3]: Building X86.td register info implementation with tblgen >> /xc/llvm-3.0.src/Release/bin/llvm-tblgen: Unknown unexpected exception >> occurred. >> make[3]: *** >> [/xc/llvm-3.0.src/lib/Target/X86/Release/X86GenRegisterInfo.inc.tmp] > Ошибка >> 1 >> make[3]: Leaving directory `/xc/llvm-3.0.src/lib/Target/X86' >> make[2]: *** [X86/.makeall] Ошибка 2 >> make[2]: Leaving directory `/xc/llvm-3.0.src/lib/Target' >> make[1]: *** [Target/.makeall] Ошибка 2 >> make[1]: Leaving directory `/xc/llvm-3.0.src/lib' >> make: *** [all] Ошибка 1 >> >> >> What`s wrong? > > Dmitry, > > Please stop spamming this mailing list. Sending the same email five > times is not useful. In fact, you might even piss off people that were > going to help you, but they might feel not to anymore because of you > being very unpatient. Thanks Matijn. In addition, Dmitry, it's not very useful having such a generic Subject: header in your email. 'Please help' immediately set the spam alarm bells going in my head, especially when 3 such titled emails came in quick succession. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Linux-PAM-1.1.3 and LFS 7.0
On Fri, 18 Nov 2011 02:06:06 +1100, Wayne Blaszczyk wrote: > Hi, > I'm now having trouble with Linux-PAM. > I get the following error: > > pam_unix_passwd.c:57:21: fatal error: rpc/rpc.h: No such file or directory > compilation terminated. > make[3]: *** [pam_unix_passwd.lo] Error 1 > make[3]: Leaving directory `/sources/Linux-PAM-1.1.3/modules/pam_unix' > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory `/sources/Linux-PAM-1.1.3/modules' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/sources/Linux-PAM-1.1.3' > make: *** [all] Error 2 > > Not sure which package rpc.h belongs to. > Any help would be appreciated. This is the long(ish) debated issue concerning the fact that Glibc ripped rpc support out of version 2.14 (I think), and libtirpc which is its replacement, doesn't compile against that version of Glibc! Have fun figuring out how to fix it :-) Regards, Matt -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Openjade-1.3.2 with gcc-4.6.0
Andy,
Now that my 4.6.0 build completed, I was able to try this out for myself.
Please try the attached patch, which worked for me.
Regards,
Matt.Submitted By:Matt Burgess
Date:2011-03-30
Initial Package Version: 1.3.2
Upstream Status: Not submitted
Origin: Matt Burgess
Description: Fixes compilation issues with GCC-4.6.0.
diff -Naur openjade-1.3.2.orig/jade/TeXFOTBuilder.cxx openjade-1.3.2/jade/TeXFOTBuilder.cxx
--- openjade-1.3.2.orig/jade/TeXFOTBuilder.cxx 2002-01-15 10:35:37.0 +
+++ openjade-1.3.2/jade/TeXFOTBuilder.cxx 2011-03-30 09:39:46.0 +
@@ -75,6 +75,7 @@
virtual void end(TeXFOTBuilder &) const = 0;
};
class PageFloatFlowObj : public TeXCompoundExtensionFlowObj {
+ public:
void start(TeXFOTBuilder &fotb, const NodePtr &) const {
fotb.startPageFloat(nic_);
}
@@ -88,12 +89,14 @@
value.convertString(nic_.placement);
}
ExtensionFlowObj *copy() const { return new PageFloatFlowObj(*this); }
+PageFloatFlowObj() {}
private:
PageFloatNIC nic_;
StringC name_;
StringC placement;
};
class PageFootnoteFlowObj : public TeXCompoundExtensionFlowObj {
+ public:
void start(TeXFOTBuilder &fotb, const NodePtr &) const {
fotb.startPageFootnote();
}
@@ -101,6 +104,7 @@
fotb.endPageFootnote();
}
ExtensionFlowObj *copy() const { return new PageFootnoteFlowObj(*this); }
+PageFootnoteFlowObj() {}
private:
};
//
diff -Naur openjade-1.3.2.orig/jade/TransformFOTBuilder.cxx openjade-1.3.2/jade/TransformFOTBuilder.cxx
--- openjade-1.3.2.orig/jade/TransformFOTBuilder.cxx 2002-12-01 14:55:51.0 +
+++ openjade-1.3.2/jade/TransformFOTBuilder.cxx 2011-03-30 09:38:48.0 +
@@ -51,6 +51,7 @@
value.convertString(name_);
}
ExtensionFlowObj *copy() const { return new EntityRefFlowObj(*this); }
+EntityRefFlowObj() {}
private:
StringC name_;
};
@@ -66,10 +67,12 @@
value.convertString(data_);
}
ExtensionFlowObj *copy() const { return new ProcessingInstructionFlowObj(*this); }
+ProcessingInstructionFlowObj() {}
private:
StringC data_;
};
class EmptyElementFlowObj : public TransformExtensionFlowObj {
+ public:
void atomic(TransformFOTBuilder &fotb, const NodePtr &nd) const {
if (nic_.gi.size() > 0)
fotb.emptyElement(nic_);
@@ -98,10 +101,12 @@
}
}
ExtensionFlowObj *copy() const { return new EmptyElementFlowObj(*this); }
+EmptyElementFlowObj() {}
private:
ElementNIC nic_;
};
class ElementFlowObj : public TransformCompoundExtensionFlowObj {
+ public:
void start(TransformFOTBuilder &fotb, const NodePtr &nd) const {
if (nic_.gi.size() > 0)
fotb.startElement(nic_);
@@ -133,10 +138,12 @@
}
}
ExtensionFlowObj *copy() const { return new ElementFlowObj(*this); }
+ElementFlowObj() {}
private:
ElementNIC nic_;
};
class EntityFlowObj : public TransformCompoundExtensionFlowObj {
+ public:
void start(TransformFOTBuilder &fotb, const NodePtr &) const {
fotb.startEntity(systemId_);
}
@@ -150,10 +157,12 @@
value.convertString(systemId_);
}
ExtensionFlowObj *copy() const { return new EntityFlowObj(*this); }
+EntityFlowObj() {}
private:
StringC systemId_;
};
class DocumentTypeFlowObj : public TransformExtensionFlowObj {
+ public:
void atomic(TransformFOTBuilder &fotb, const NodePtr &nd) const {
fotb.documentType(nic_);
}
@@ -174,6 +183,7 @@
}
}
ExtensionFlowObj *copy() const { return new DocumentTypeFlowObj(*this); }
+DocumentTypeFlowObj() {}
private:
DocumentTypeNIC nic_;
};
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: Openjade-1.3.2 with gcc-4.6.0
On Tue, 29 Mar 2011 23:26:28 +0200, Or Goshen wrote:
> It is documented here:
> http://lists.fedoraproject.org/pipermail/devel/2011-February/148523.html
>
> under "uninitialized const".
>
> You're suppose to either supply an initializer or a default constructor.
>
> A default constructor can be a simple "A() {}"
Somewhat more concretely, what happens if you add the following at line 78
PageFloatFlowObj() {}
and the following at line 98
PageFootnoteFlowObj() {}
Regards,
Matt.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: 139-network
On Wed, 16 Mar 2011 14:23:59 +0200, Rodolfo Perez wrote:
> Hey again
>
>> > Looking at my bash-output I was asked to enter my password. That time
> I
>> > was sleeping :-) Is it possible that there is a time limit to
> enter
>> > the password?
>>
>> I think that's the problem, as it's caught me out a couple of times too.
>>
>> I wouldn't worry too much though; just run 'make' again from within
> jhalfs
>> and it'll pick up where it left off.
>
> Thanks that worked! Apparently there is a time limit.
>
> But now I got stacked again on 139-network, just before the end, and
> again couldn't find help :-( Is the problem realy the
> missing /dev/.udev/rules.d?
> When I run "make" it tells it changes to chroot, but I'm not ...? Could
> that be the problem?
>
> Would appreciate any hints.
Are you on a CentOS host by any chance? I see similar errors on CentOS-5.5
which I think are because of the old versions of the kernel + udev on that host.
I ended up just commenting out the following from my working copy of
chapter07/network.xml:
for NIC in /sys/class/net/* ; do
INTERFACE=${NIC##*/} udevadm test --action=add $NIC
done
I only have 1 NIC so this wasn't necessary on my particular build.
If you're building from a released version of the book, I'm not sure if there's
a way of
running jhalfs so that it picks up from where it left off without reparsing the
book
to regenerate the commands. If you need to do something like that, you may
want to
ask on the alfs-discuss list or take a look through jhalfs' makefile to see if
there's
a suitable target.
Regards,
Matt.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: jhalfs mk_BOOT
On Wed, 16 Mar 2011 09:30:36 +0200, Rodolfo Perez wrote: > Hey all > > I was trying to build lfs with jhalfs. Everyting went well until > Building target 125-strippingagain. > > Looking at my bash-output I was asked to enter my password. That time I > was sleeping :-) Is it possible that there is a time limit to enter > the password? I think that's the problem, as it's caught me out a couple of times too. I wouldn't worry too much though; just run 'make' again from within jhalfs and it'll pick up where it left off. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: how to automate lfs
On Mon, 21 Feb 2011 21:53:10 +, Andrew Benton wrote: > For what it's worth, I write my own custom scripts based on the > commands in the book but with my own special ingredients. I'm sure > jhalfs works as other people on the lists use it, but I don't know if > it works for BLFS. I too started off writing my own scripts for both LFS and BLFS. However, when it comes to testing the instructions in the LFS book, as required by any good editor, there's nothing like a computer to make sure that the commands being run are those that are in the book, and not what I think are in the book (i.e. it avoids typos, or changes being missed as they can be when having to keep the book and separate scripts in sync). > It occurred to me that I could simply copy and > paste the commands into a shell script and then run that with one > command. However the problems with that are making sure it stops when > an error occurs and that it logs everything into a file so that I can > look back at what went wrong and Google for a solution. Working around > those and other problems (eg how to automatically generate a new fstab for > the new system?) became my way of learning to write scripts. It's a > useful skill. I definitely agree with you there, Andy. I still use my own scripts for BLFS as, whereas there is some support for BLFS in jhalfs, I tend to customise my BLFS package builds much more than the LFS packages. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: how to automate lfs
On Mon, 21 Feb 2011 11:57:20 +0200, Rodolfo Perez wrote: > Hi all > > Well I'm not sure if this forum is the right one ... > > I've build lfs 2 times successfully and now I'm trying to use jhalfs. I > did not succeed so far, but before i spend hours and hours I would like > to ask the experts some few questions. > > 1. How do you generally install the new lfs's? Are you using jhalfs? Yes. > 2. Will the actually jhalfs-2.3.2 work for the forthcoming lfs-6.8 ? I don't know, but I suspect not. I use a trunk checkout of jhalfs, and that works fine. > 3. I tried jhalfs-2.3.2 with lfs-6.5 and I got the following message and > error executing the make: > > -- > > Are you happy with these settings? yes/no (no): yes > > -- > > This feature requires Subversion. Just install a subversion client on your host system; it's required in order to checkout the sources of the book which it will parse to get the commands required. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: udev in blfs
On Sat, 19 Feb 2011 16:48:38 +, John Burrell wrote: > > Current version of udev in lfs-development is 166. > > In blfs, if gobject-introspection installed, then udev-164 compiles okay, > but versions 165 and 166 do not. FWIW, Udev-166 builds fine here with gobject-introspection-0.10.2. I'm not far enough into my BLFS to be able to say whether that version of gobject-introspection breaks anything else though. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
LFS-6.8-rc1 release
Hi all, The Linux From Scratch community is pleased to announce the release of LFS Version 6.8-rc1. This is the first release candidate on the road to LFS-6.8. It includes numerous changes to LFS-6.7 (including updates to Linux-2.6.37, GCC-4.5.2, Glibc-2.13 and security fixes). It also includes editorial work on the explanatory material throughout the book, improving both the clarity and accuracy of the text. We encourage all users to read through this release of the book and test the instructions so that we can make the final release as good as possible. You can read the book online [0], or download to read locally [1]. Please direct any comments about this release to the LFS development team at lfs-...@linuxfromscratch.org. Please note that registration for the lfs-dev mailing list is required to avoid junk email. Regards, Matt. [0] http://www.linuxfromscratch.org/lfs/view/6.8-rc1/ [1] http://www.linuxfromscratch.org/lfs/downloads/6.8-rc1/ -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: XKB Failed to compile keymap
On Wed, 9 Feb 2011 22:43:50 +, Ken Moffat wrote: > If building lots of drivers doesn't help, how about > xkeyboard-config as suggested in > http://linuxfromscratch.org/pipermail/blfs-dev/2011-January/020953.html Thanks, Ken. It turns out that recompiling all of X up to and including the Xorg-fonts was enough to get this working again. I think what happened was that at least one of the wget files had some entries commented out when one of my previous builds had partially completed (so instead of recompiling all of that section, just the bits that hadn't been built were attempted). I noticed this because something complained about xls-atoms not being present and I thought I'd gone back and recompiled everything, but obviously not! So, it wasn't a lack of drivers or a xkeyboard-config problem at all. I now suspect that part of xorg-apps hadn't been built against a required dependency. Thanks, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: XKB Failed to compile keymap
On Wed, 09 Feb 2011 13:31:22 -0600, Bruce Dubbs wrote: > I guess the obvious question is does it start for user root? If so, > then it's a permissions problem. What are the permissions of /var/lib/xkb/? Yeah, should have mentioned that. I get the same error trying to start it as root. /var/lib/xkb permissions are 0777. Another question I've got is does anyone know how xkbcomp is invoked by the X server? i.e. can I invoke xkbcomp on the command-line to simulate what the X server is doing so I can see if there are any more warnings/errors? Also, in the interests of full disclosure, I only normally compile the evdev and vesa drivers. I'm doing a much fuller driver build now, just in case I need something else here. Thanks, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
XKB Failed to compile keymap
Hi, On my latest build of Xorg-7.6, the server refuses to startup issuing the following error: (EE) Couldn't open compiled keymap /tmp/server-0.xkm XKB: Failed to compile keymap That immediately struck me as odd as the following option is passed to Xorg-Server's configure command: --with-xkb-output=/var/lib/xkb It turns out that if you want to start X as non-root, then permissions on /var/lib/xkb need to be such that a non-root user can write to it. Changing perms to 0777 were enough to get the following error instead: (EE) Couldn't open compiled keymap /var/lib/xkb/server-0.xkm XKB: Failed to compile keymap Not much of an improvement, but at least it's pointing at the correct directory now. So, any ideas how to fix this? I've recompiled xkeyboard-config, checking that xkbcomp is in /usr/bin, etc. all of which is mentioned at http://www.mail-archive.com/xorg@lists.freedesktop.org/msg09029.html. Other google hits suggest disk space could be a culprit, but I've got plenty left here. Thanks for any help! Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Flash Player on 64 bit linux - Firefox
On Wed, 5 Jan 2011 13:58:33 -0500, Mike Hollis wrote: > On Wed, Jan 05, 2011 at 06:47:55PM +0100, Lars Bamberger wrote: >> >> I'm using Shockwave-Flash-10.1r10 with firefox-3.6.13 (with GNOME). That >> works perfectly here. libcurl does not seem to be a dependency for >> libflashplayer.so. (See output of 'ldd libflashplayer.so') >> > ldd indeed does not show it as a dependency, but I renamed all the > libcurls.* in /usr/lib and I have the symptoms the poster is reporting. > Rename them correctly and it works. Sounds like it's doing a dlopen() on those libraries then. strace would probably prove it if anyone can be bothered :-) Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: make problem with kdelibs-4.5.3
On Mon, 15 Nov 2010 12:33:46 +0100, "Dr.-Ing. Edgar Alwers" wrote: > -- Found shared-mime-info version: /usr/bin/update-mime-database: > /usr/lib/libxml2.so.2: no version information available (required by > /usr/bin/update-mime-database) It turns out I shouldn't have recommended libxml2-2.7.8 after all, or at least not without also mentioning the patch at http://git.gnome.org/browse/libxml2/commit/?id=00819877651b87842ed878898ba17dba489820f0 I haven't had a chance to turn that into a sed yet, but making the change manually in vim should be easier than downloading and applying the patch for now :) Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: make problem with kdelibs-4.5.3
On Sun, 14 Nov 2010 21:24:29 +0100, "Dr.-Ing. Edgar Alwers" wrote: > Hi, > > could somebody help with a hint, how to come through the last 4% of the > compilation of kdelibs-4.5.3 ? I get ( on two boxes ) the error > quote > - > Scanning dependencies of target data-handbook > [ 96%] Generating index.cache.bz2 > sh: line 1: 22205 Segmentation fault /usr/bin/xmllint --valid --noout > index.docbook 2>&1 What versions of zlib and libxml2 are you using? libxml2 <= 2.7.6 is known to misuse the zlib API which was exposed with zlib >= 1.2.4. Upgrading to libxml2-2.7.8 would be my recommendation. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Jhalfs and LFS6.7
On Sun, 19 Sep 2010 09:26:07 -0400, cliffhan...@gardener.com wrote: > Hi > > I think I might be ready to use or try Jhalfs. Can anyone comment on > its use with LFS 6.7 or would I need to use an earlier version? I've just completed a build of LFS-6.7 with the latest jhalfs-trunk on a Lubuntu-10.04 host and had no issues at all. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Config-less Xorg & xkb config
On Mon, 29 Mar 2010 22:58:09 +0100, Matthew Burgess wrote: > Hi all, > > I'm running Xorg in a config-less setup. Everything seems to be working > fine, apart from it's using the 'us' keyboard layout as its default. > I'd prefer to remain config-less, if at all possible as, so far, this > would be the only option that I'd need to cusomise. Just in case anyone else runs into this, I've finally gotten around to fixing it properly: mkdir /etc/X11/xorg.conf.d cat > /etc/X11/xorg.conf.d/keyboard.conf << EOF Section "InputClass" Identifier "Keyboard Defaults" MatchIsKeyboard "true" Option "XkbLayout" "gb" EndSection EOF Thanks to the guys at ArchLinux for documenting this at http://wiki.archlinux.org/index.php/Xorg#Example:_Keyboard_layout_and_model_on_Acer_5920G_Laptop. I now have a config-less X server (well, no xorg.conf, just the override above), using Udev for its device detection, and no HAL in sight! The only drivers I built were evdev & vesa. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: ls: unrecognized prefix: hl
On Sun, 23 May 2010 20:07:00 +0200, Lars Bamberger wrote: > hermes~> type ls > ls is aliased to `ls -F --color=auto --show-control-chars' > > Nope. It won't tell me about the executable /bin/ls. What about `type -a ls'? Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: What works for me (LFS-6.6, x86_64)
On Thu, 06 May 2010 13:51:20 +1200, Simon Geard wrote: > On Wed, 2010-05-05 at 17:25 +0100, Ken Moffat wrote: >> OK, I've dug out my notes from last october, but all those say is that >> the new version didn't seem to be properly released and was only in >> fedora (fc12). Looking at fedora cvs, it was a git pull from 20090913 >> and according to them depended on pam, eggdbus, >> gobject-introspection, console-kit. I've already expressed my >> reluctance to touch pam, with the old policykit that isn't necessary >> (there is a patch!). > > That makes sense, if polkit was still pre-release at the time. Fedora do > tend to be ahead of everyone else on these sorts of things, since > they're largely developed by Redhat engineers. > > As to PAM, I've never tried building polkit without it - didn't even > think of it as a dependency, since I just build it during LFS. But > looking at current polkit, it *appears* to support Shadow as an > alternative to PAM. *Appears* is the right intonation! The build fails without PAM and I think I reported it a while ago, and upstream pretty much said most/all distros use PAM so they weren't interested in fixing it. I was going to reply with a tongue-in-cheek patch that completely removed Shadow support, to make PAM a hard dependency but never did get around to it. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Config-less Xorg & xkb config
On 30/03/2010 15:04, Ken Moffat wrote: > On 30 March 2010 02:12, Ken Moffat wrote: >> I haven't tried to do without xorg.conf because I don't think it will >> default to anything approaching my default settings. > > Just gave this a test - no keyboard or mouse (I only build the evdev > driver these days). Don't expect me to test conf-less xorg any time > soon :( Interstingly (potentially!), I've just rebuilt xorg-server against HAL and now my keyboard and mouse have stopped working too under a configless setup! I just rebuilt with '--disable-config-hal' and things started working again. That's so counter-intuitive (given that HAL is supposed to aid auto-detection) that I now suspect I've made a mistake somewhere! Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Config-less Xorg & xkb config
On 30/03/2010 02:12, Ken Moffat wrote: > On 30 March 2010 00:49, David Jensen wrote: >> On Mon, 29 Mar 2010 23:35:28 +0100 >> Matthew Burgess wrote: >> > >> I do not use an xorg.conf, but do use 'Openbox, lxpanel and lxmenu'. >> I'm just USA, American. For the definitive .xinitrc, I'm hoping 'ken' >> will chime in. Damn, we so much miss those with 'I18n' experience! >> > I haven't tried to do without xorg.conf because I don't think it will > default to anything approaching my default settings. I don't follow > xorg closely enough to know what is automatic, but I assumed > keyboard types were (from the user's locale, probably). After all, > fedora do it like this, don't they ? > > Matt: is this vmware, and/or do you use hal ? Apparently, both of > those can affect the keyboard setting (according to google). Ah, I do use VirtualBox, which may be getting in the way, I guess. I was hoping it would just pick up on the fact that I'm using the en_GB.UTF-8 locale and therefore default to a 'gb' keyboard layout. I'm not using HAL currently, but may resign myself to doing so as some parts of LXSession apparently want it to be around. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Config-less Xorg & xkb config
On 29/03/2010 23:10, David Jensen wrote: > On Mon, 29 Mar 2010 22:58:09 +0100 > Matthew Burgess wrote: > >> Hi all, >> >> I'm running Xorg in a config-less setup. Everything seems to be >> working fine, apart from it's using the 'us' keyboard layout as its >> default. I'd prefer to remain config-less, if at all possible as, so >> far, this would be the only option that I'd need to cusomise. >> >> `setxkbmap -rules base -model pc105 -layout gb -option""` appears to >> do what I want. Now I just need to get this triggered each time I >> start my X11 session. I'm using lxdm& openbox, in case this >> matters. Any advice greatly appreciated! >> >> Thanks, >> >> Matt. > Well, surely you tried this, but, can't that be added to ~/xinitrc? > Excuse me if this is useless. Not useless at all. I gave it a try (using ~/.xinitrc), but it didn't appear to have any effect (not in the lxterminal at least). I wonder whether lxde/lxdm is doing something quirky resulting in it not running through the normal xinit stuff? Maybe Xorg would auto-detect my desired layout if I was using HAL? I'm trying to avoid that as it's looking like it's being phased out. Can anyone else confirm if their keyboard layout is automatically detected with no Xorg config file please, or whether you know if such a feature is/isn't present upstream? Ta, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Config-less Xorg & xkb config
Hi all, I'm running Xorg in a config-less setup. Everything seems to be working fine, apart from it's using the 'us' keyboard layout as its default. I'd prefer to remain config-less, if at all possible as, so far, this would be the only option that I'd need to cusomise. `setxkbmap -rules base -model pc105 -layout gb -option""` appears to do what I want. Now I just need to get this triggered each time I start my X11 session. I'm using lxdm & openbox, in case this matters. Any advice greatly appreciated! Thanks, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: OHCI vs UHCI
On Tue, 16 Mar 2010 14:02:56 -0600, Mike McCarty wrote: > Is one just to "know" by some means that all USB 2.0 conform to > one or the other of UHCI or OHCI? The kernel's menuconfig help text for EHCI says: "If you configure EHCI, you should probably configure the OHCI (for NEC and some other vendors) USB Host Controller Driver or UHCI (for Via motherboards) Host Controller Driver too." For OHCI it states: "On most non-x86 systems, and on x86 hardware that's not using a USB controller from Intel or VIA, this is probably appropriate." It even suggests that 'lspci -v' will provide the interface type (EHCI, OHCI or UHCI) for your USB controllers. That output was accurate on a quick check of my system. UHCI's help text mentions some specific Intel & Via chipsets that are supported. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Building KDE-4.4.1
James Richard Tyrer wrote: > Matthew Burgess wrote: >> Hi all, >> >> I know a couple of folks here have built KDE recently. I think I >> already know the answer to this, but I think I have to grab kdesupport >> out of SVN in order to build KDELibs, right? My conclusion was arrived >> at because kdelibs wants 'automoc4' from kdesupport but there is no >> kdesupport tarball available from KDE's download site. >> >> If that's the case, how do I stop things like oxygen-icons being built >> that already have their own tarballs available? Preferably I don't even >> want to check out the oxygen-icons area of svn but I'm not sure that's >> possible...an 'svn update' on such a checkout would pull oxygen-icons >> next time around anyway, I would have thought. >> >> Why can't developers release a bloody tarball of their stuff? >> > Good question to which I have no answer except to say that they seem to > expect that you will get the dependencies from your distro. I don't see that as a very valid argument at all. How many distros are out there? And all of them now need to duplicate this dependency hunting and preparation game? I'm firmly in the mindset that part of being a good upstream software project is to make it easy for downstream users to make use of and integrate your software. And why is it up to people like you, James, to document this? Surely if the KDE deps are so complex to locate (relatively speaking), then the least the KDE devs could do is write down what the dependencies are, why they are required, and which locations/branches/tags are compatible with KDE-? Like I've already said though, this is probably the worst place to be raising concerns over this, and I've already decided to move to LXDE anyway so in an entirely selfish manner, I don't care about KDE's dependency hell anymore. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: LXDM & PAM
Matthew Burgess wrote: > Has anyone got lxde working with lxdm and would be able to offer any > hints please? It turns out this wasn't PAM's fault at all. I was missing some core lxde packages, namely lxde-common. I'll see if I can get this stuff written up; lxde looks to be just what I'm after! Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
LXDM & PAM
Hi, Has anyone got lxde running with lxdm as the graphical login manager by any chance? I think things are getting hung up with PAM; lxdm starts up OK, but after trying to log in as a valid user, it just seems to result in lxdm restarting. I see this in /var/log/auth.log: Mar 8 21:21:09 kyoto lxdm-binary: pam_unix(lxdm:session): session opened for user lfs by (uid=0) Mar 8 21:21:09 kyoto lxdm-binary: pam_unix(lxdm:session): session closed for user lfs An strace on it shows it correctly opens /etc/pam.d/lxdm which I copied from BLFS' /etc/pam.d/gdm: authrequiredpam_unix.so authrequisite pam_nologin.so account requiredpam_unix.so passwordrequiredpam_unix.so session requiredpam_unix.so So far, I've installed: lxdm-0.1.0, lxpanel-0.5.5, lxmenu-data-0.1.1, lxsession-0.4.2, iso-codes-3.14, menu-cache-0.3.2. Has anyone got lxde working with lxdm and would be able to offer any hints please? Thanks, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Building KDE-4.4.1
Ken Moffat wrote: > On 7 March 2010 11:37, Matthew Burgess wrote: >> Hi all, >> >> I know a couple of folks here have built KDE recently. I think I >> already know the answer to this, but I think I have to grab kdesupport >> out of SVN in order to build KDELibs, right? My conclusion was arrived >> at because kdelibs wants 'automoc4' from kdesupport but there is no >> kdesupport tarball available from KDE's download site. >> > > Not recent, but when I was building kde4 I used to grab source tarballs > from e.g. Arch. A quick google suggests Slackware have > automoc-0.9.88.tar.bz2 (failing tarballs, there's always rpm2cpio). > At that time, I grabbed phonon from debian, looks as if qimageblitz > maybe had a proper release. Looked as if a version gets tagged in > svn from time to time, but tarballs aren't prepared. > >> If that's the case, how do I stop things like oxygen-icons being built >> that already have their own tarballs available? Preferably I don't even >> want to check out the oxygen-icons area of svn but I'm not sure that's >> possible...an 'svn update' on such a checkout would pull oxygen-icons >> next time around anyway, I would have thought. > > Don't know, and I'm afraid I don't care - building software became > a lot easier when I gave up kde4 and cmake. I'm seriously considering giving up on it too, to be honest. The cmake output clearly stated that I needed to use automoc from kdesupport, but now folks are pointing me at old automoc tarballs. If the dev's can't even be bothered to update their dependency documentation then it doesn't bode well for the rest of what I might encounter. Various howtos I've found on the net also point at pulling phonon from git, and various other bits from their respective SCM repositories. That's not for me, I'm afraid. How on earth upstream devs cope with bug reports when they've no way of controlling/repeating what their users might be linking against I've no idea. Following on from the earlier thread discussing lightweight window managers/desktop environments, I'm currently trying to get lxde put together. lxdm requires consolekit which requires polkit which requires PAM. Despite polkit accepting '--with-authfw=shadow' it bails as there are assumptions all over the code on PAM being present. What was it I said above about developers accurately detailing their dependencies :-). Aside from that though, I think lxde might be just what I'm after! Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Building KDE-4.4.1
Hi all, I know a couple of folks here have built KDE recently. I think I already know the answer to this, but I think I have to grab kdesupport out of SVN in order to build KDELibs, right? My conclusion was arrived at because kdelibs wants 'automoc4' from kdesupport but there is no kdesupport tarball available from KDE's download site. If that's the case, how do I stop things like oxygen-icons being built that already have their own tarballs available? Preferably I don't even want to check out the oxygen-icons area of svn but I'm not sure that's possible...an 'svn update' on such a checkout would pull oxygen-icons next time around anyway, I would have thought. Why can't developers release a bloody tarball of their stuff? Thanks, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: libdrm-2.4.14 overwrites some drm linux-api-headers
On Wed, 3 Mar 2010 14:19:25 +, Ken Moffat wrote: > On 3 March 2010 13:49, Aleksandar Kuktin wrote: >> Then should libdrm be built as soon as possible when bootstrap building >> BLFS so as to minimise the chance that some other package will build >> against Linux drm headers? And try to prevent interface incompatibility >> in that way? > > If by "as soon as possible" you mean "after the xorg libs, > before Mesa / xorg-server / xorg video drivers" the answer > is yes. Why "after xorg libs"? I generally build libdrm very early on, largely due to its minimal dependency tree. I did notice that it now checks for Cairo, so there's another circular dependency there, but it doesn't seem to mind building before any of the xorg bits, including the libraries. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: libdrm-2.4.14 overwrites some drm linux-api-headers
John Burrell wrote: > If installed as root, libdrm will overwrite these linux-api-headers from > /usr/include/drm: On a very new system (linux-2.6.33 + libdrm-2.4.18) I see the same thing. Looking at the README in the tarball for libdrm: "New functionality in the kernel DRM drivers typically requires a new libdrm, but a new libdrm will always work with an older kernel." As such, I think the right thing to do in this scenario is to just let libdrm overwrite the headers it wants to install. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
LFS-6.6 is released
Hi, I'm pleased to announce the release of LFS Version 6.6. This release includes numerous changes to LFS-6.5 (including updates to Linux-2.6.32.8, GCC-4.4.3, Glibc-2.11.1) and security fixes. It also includes editorial work on the explanatory material throughout the book, improving both the clarity and accuracy of the text. You can read the book online[0], or download[1] to read locally. Please direct any comments about this release to the LFS development team at lfs-...@linuxfromscratch.org. Please note that registration for the lfs-dev mailing list is required to avoid junk email. Regards, Matt. [0] http://www.linuxfromscratch.org/lfs/view/6.6/ [1] http://www.linuxfromscratch.org/lfs/downloads/6.6/ -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: help tetex-src-3.0 error
Dale Stein wrote:
> I was wondering if anyone knew how to fix this problem
> I am trying to build teTeX-3.0 and it is coming back with a ulgy error.
> This was built with LFS 6.6 and BLFS svn.
>
> make[3]: Leaving directory `/sources/blfs/tetex-src-3.0/texk/web2c/lib'
> gcc -DHAVE_CONFIG_H -I. -I. -I.. -I./.. -g -O2 -c tangleboot.c -o
> tangleboot.o
> In file included from tangleboot.c:94:
> tangleboot.h:34: error: conflicting types for 'getline'
> /usr/include/stdio.h:651: note: previous declaration of 'getline' was here
> tangleboot.c:2175: error: conflicting types for 'getline'
> /usr/include/stdio.h:651: note: previous declaration of 'getline' was here
> make[2]: *** [tangleboot.o] Error 1
> make[2]: Leaving directory `/sources/blfs/tetex-src-3.0/texk/web2c'
> make[1]: *** [all] Error 1
> make[1]: Leaving directory `/sources/blfs/tetex-src-3.0/texk'
> make: *** [all] Error 1
Yep, that's a pretty common error with older source packages and newer
Glibc which provides its own copy of getline() now. The easiest way
around this is something like:
sed -i -e 's/getline/get_line/g' texk/web2c/lib/tangleboot.{c,h}
i.e. just rename tetex's internal copy of getline to get_line.
Regards,
Matt.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: BLFS-6.4RC1 or any
On Tue, 16 Feb 2010 08:38:51 -0600, Randy McMurchy wrote: > Mike McCarty wrote these words on 02/16/10 01:32 CST: >> To put it another way, my time is my life. > > But you have the time to write 9 paragraphs about why you don't like > distros and use BLFS! Pot-Kettle-Black. :-) > > BTW, you may never again see a released version of BLFS, I'd take the > wise advise you were given and use the development version of BLFS for > all that you do concerning BLFS. > > And I'm saying this as the lead Editor of the book. And as a non-contributory member of the editing team ( :-) ) I would whole-heartedly agree with this! I think that BLFS has simply grown far too big to ever be in a completely stable *and* useful state. Things move so quickly in the open source arena that as soon as you freeze something as big as BLFS, by the time it's stabilised then the kernel, toolchain, etc. have moved on, offering new features that would be useful for at least one of the BLFS packages. I think the LFS book is stable enough that folks can use either the latest release or the development version of that to build whatever is in BLFS with very few problems. I've certainly seen little in the way of breakage for the last few months and the majority of the package updates in LFS have only involved the trivial updates to md5sum's and version entitites! As a side-note, I generally use BLFS as a *guide* now, for build-order decisions and the like, rather than using the exact instructions . I'll usually drop the latest version of the package in place without too much trouble. I keep promising to submit my updates to the book; maybe next time :-) Mike certainly seems more than competent enough to do the same thing. Mike, my recommendation would be to use the BLFS book in a guide-like manner too. Keep your build scripts and/or built packages in some kind of version control system then just build & integrate what works for you. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: blfs-book-svn-html
stosss wrote: > Why is it that you and other developers are so touchy about the book > and its condition and people pointing out things that could be done > different, better or whatever? Why do you and the others insist on > thinking there is nothing wrong with the book and so unwilling to > improve it? I think that's a little unfair. Please remember that both the LFS and BLFS projects are based on *volunteer* effort and therefore noone should *expect* to have their particular pet-peeve fixed in any particular amount of time (or at all in fact). Whilst we do endeavour to address all suggestions, lack of time or a particular urge to 'scratch an itch' that a particular developer may not be feeling is more than reasonable behaviour in such projects. Why is the fact that we regenerate the book every day such a problem for you? If the date of the book hasn't been incremented then it's fairly safe to say that no changes have been made. I don't think it would take too much to change our nightly jobs to not render a new copy of the book if no changes have been made, but again, nobody apart from you seems to care at the moment. Given the long list of defects in BLFS' Trac system I'd wager that most of the devs would rather spend time tackling them than preventing regeneration of a book on a server that has plenty of capacity to do so. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Xorg desktop viewed through fog - Sorted
On Mon, 11 Jan 2010 11:27:18 -0600, Bruce Dubbs wrote: > Matthew Burgess wrote: >> Actually, I believe that upstream are moving toward a config-less X. I > find this >> much easier but the book currently doesn't support it out of the box due > to some >> incompatible configure switches used between the server, fonts and > driver bits. >> >> I'll post my suggestions to -dev when I'm back from work tonight. But, > using this >> I can successfully start an X server within a VirtualBox environment and > it correctly >> picks up my monitor, video chip, keyboard and mouse without the need for > an Xorg.conf! > > I haven't looked at it, but it still allows a config file, right? If I > choose to use a proprietary driver that is not in xorg by default, I > still should be able to use it. Yes, that's my understanding. Without a config file, it will try to figure out what the settings should be, but if a config file is present it will use that. Whether or not you can mix and match, i.e. put just the video driver bits in and have it automatically set up things like your input devices I'm not sure. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Xorg desktop viewed through fog - Sorted
On Mon, 11 Jan 2010 01:06:29 +, Ken Moffat wrote: > 2010/1/11 Bruce Dubbs : >> >> Xorg -configure >> >> will tell you what kind of video card X finds. Look at ~/xorg.conf.new Actually, I believe that upstream are moving toward a config-less X. I find this much easier but the book currently doesn't support it out of the box due to some incompatible configure switches used between the server, fonts and driver bits. I'll post my suggestions to -dev when I'm back from work tonight. But, using this I can successfully start an X server within a VirtualBox environment and it correctly picks up my monitor, video chip, keyboard and mouse without the need for an Xorg.conf! Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: fop-0.95 compile problems//minimal Xorg for Xvfb??// fop with GCJ
On Thu, 7 Jan 2010 16:23:56 +, lux-integ wrote: > On Tuesday 22 December 2009 06:24:27 pm Hops Error, Line 21, alcoholi.c > wrote: > >> I don't recall which environment variable ant uses to pass flags to >> java off the top of my head, though. It couldn't be anything simple >> like JFLAGS :p > > compiling FOP with GCJ may be of interest to some on list here (link > below > might be useful) > http://wiki.apache.org/xmlgraphics/GnuClasspathCompatibility Hmm, admittedly at least 18 months ago now, last time I tried this I couldn't even get ANT to compile with GCJ as it relies on something called a 'greedy' compiler, which GCJ isn't. Regards, Matt. -- 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
Matthew Burgess wrote: > Any ideas as to what's gone awry here would be much appreciated. Doing a bit more hunting around, I think http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=9c501935a3cdcf6b1d35aaee3aa11c7a7051a305 may be related. Changing the linux/socket.h include to sys/socket.h in linux/netlink.h is enough to get strace to compile. I'll send this upstream, and see what they say. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Strace on recent LFS (dev) build
Hi all, Trying to compile strace under a very recent LFS build (2.6.32.2 kernel) results in: net.c:976: error: field 'nl' has incomplete type 'nl' in this case is of type sockaddr_nl, which should be defined in /usr/include/linux/netlink.h. config.log has this to say: configure:5882: gcc -c -g -O2 conftest.c >&5 In file included from conftest.c:75: /usr/include/linux/netlink.h:34: error: expected specifier-qualifier-list before 'sa_family_t' Now, netlink.h has this on line 4: #include /* for sa_family_t */ But, linux/socket.h has no definition for sa_family_t. That appears to be defined in bits/sockaddr.h. Any ideas as to what's gone awry here would be much appreciated. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: MySQL test error
Mykal Funk wrote: > 091224 8:16:01 [ERROR] Fatal error: Please read "Security" section of > the manual to find out how to run mysqld as root! Are you building/testing MySQL as root, hence getting this warning? Have you tried building/testing as a non-root user? Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: man-db-2.5.5 never installed
On Tue, 15 Dec 2009 03:22:00 -0500, stosss wrote: > I have complete log files of > the entire step process of the unpack, configure, make and make check > steps. I can show you as much of the logged process for each step as > you want to see. The error is directly related to man.o. I have > checked /usr/bin and none of the commands from man-db are there. Please send the logs with about 20 lines of context either side of the man.o failure. We may also need config.log, but for now just the build log should do. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: LFS book 6.52.3 problem (passwd root)
On Sat, 28 Nov 2009 10:54:37 -0200, Cristiano Cortezia wrote: > > I've got a problem in the mentioned step (6.52.3 - Shadow configuration). > If I run the command 'passwd root', I get the following output, before > being able to provide any input: > > root:/# passwd root > Changing password for root > Enter the new password (minimum of 5 characters) > Please use a combination of upper and lower case letters and numbers. > Bad password: too short. > Warning: weak password (enter it again to use it anyway). > passwd: password changed. > > Can anyone point what type of problem do I have here ? Hi Cristiano, I've seen this problem before, particularly after using jhalfs. It's caused by not having all of the LFS filesystems mounted (in particular /dev). If you remount all of the filesystems under /mnt/lfs (see sections 6.2.2 and 6.2.3) then you should be able to set the password successfully. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: LFS is at 6.5 BLFS is at 6.3 Why?
On Tue, 24 Nov 2009 05:23:03 -0500, stosss wrote: > Why does LFS stay so far ahead of BLFS? What is the point of building > the newest LFS if the BLFS files are older and probably won't work or > would be replacing newer versions of apps with older versions? BLFS, like all of the LFS projects is provided by volunteers. As such, the production of a stable version of the book is dependent on the amount of time that the editors and release manager have available. Due to the massive difference in size in the respective projects, it is much easier to stabilize and release the LFS book than it is for BLFS, hence why LFS tends to have much shorter life-cycle than BLFS. > Use SVN if you are using LFS 6.4 what about LFS 6.5? The same goes for any version of LFS with a later version number than BLFS. Despite it not having a 'stable' release, I find that the instructions in BLFS work far more often than they don't, and any issues I highlight are dealt with very quickly. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: autofs-5.0.3 Compile error BLFS svn-20090901
On Sun, 6 Sep 2009 15:25:37 -0600, Jim McConville wrote: > There still remains the question: "Should it be noted in the BLFS > document that these bindings will not exist if the computer is rebooted > into the host system followed by an entry made into the "chroot" > environment?" I don't know whether BLFS will want to add the note, as it already exists in LFS at http://www.linuxfromscratch.org/lfs/view/development/chapter06/revisedchroot.html. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
LFS-6.5 Released
Hi, The Linux From Scratch community is pleased to announce the release of LFS Version 6.5. This release includes numerous changes from LFS-6.4 (including updates to Linux-2.6.30.2, GCC-4.4.1, and Glibc-2.10.1) and security fixes. It also includes editorial work on the explanatory material throughout the book, improving both the clarity and accuracy of the text. You can read the book online[0], or download to read locally [1]. Please direct any comments about this release to the LFS development team at lfs-...@linuxfromscratch.org. Please note that registration for the lfs-dev mailing list is required to avoid junk email. Regards, Matt. [0] http://www.linuxfromscratch.org/lfs/view/6.5/ [1] http://www.linuxfromscratch.org/lfs/downloads/6.5/ -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Dash fails to build with the LFS 6.5 toolchain
On Sat, 15 Aug 2009 7:52:48 -0600, Matthew Burgess wrote: > Now to track down which of those tools called out to from mkbuiltins is > causing the > issue! And the culprit is `sort'. Building coreutils without LFS' i18n patch is enough to get things working again. I'll pop this issue over to lfs-dev now, and we'll sort it out one way or the other over there! Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Dash fails to build with the LFS 6.5 toolchain
On Sat, 15 Aug 2009 14:33:56 +0100, Guy Dalziel wrote: > On Sat, Aug 15, 2009 at 07:15:13AM -0600, Matthew Burgess wrote: >> Yes, I can reproduce it at will here. Stock LFS-6.5-rc2 and no compiler >> flags set in my environment: > > It's odd that I'm not experiencing the same problems that everyone else > seems to be. Do you think that there could be a problem with > non-bootstrapped GCC? Nope, it's not that. It looks like it was my LANG setting. If I change from my default of LANG=en_GB.UTF-8 to LANG=en_GB I don't have any compilation issues at all! Now to track down which of those tools called out to from mkbuiltins is causing the issue! Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Dash fails to build with the LFS 6.5 toolchain
On Sat, 15 Aug 2009 14:10:00 +0100, Guy Dalziel wrote: > On Sat, Aug 15, 2009 at 06:57:50AM -0600, Matthew Burgess wrote: >> That missing [0] reference is: >> >> http://www.mail-archive.com/d...@vger.kernel.org/ > > Ah, I've already looked through that, a project mailing list is usually > the first place I look. Since it compiles for me, there doesn't appear to > be a report on the list, and Gentoo marked it as invalid then I'm not > entirely convinced that this is a problem with either BLFS or dash. Is > there anyone who can reproduce this? Yes, I can reproduce it at will here. Stock LFS-6.5-rc2 and no compiler flags set in my environment: f gcc -DHAVE_CONFIG_H -I. -I. -I.. -include ../config.h -DBSD=1 -DSHELL -DIFS_BROKEN -Wall -g -O2 -MT eval.o -MD -MP -MF ".deps/eval.Tpo" -c -o eval.o eval.c; \ then mv -f ".deps/eval.Tpo" ".deps/eval.Po"; else rm -f ".deps/eval.Tpo"; exit 1; fi eval.c: In function ‘evalcommand’: eval.c:810: error: ‘EXECCMD’ undeclared (first use in this function) eval.c:810: error: (Each undeclared identifier is reported only once eval.c:810: error: for each function it appears in.) eval.c:812: error: ‘COMMANDCMD’ undeclared (first use in this function) Could you put your src/builtins.h file online somewhere for me to have a look at please (assuming 'grep -R EXECCMD *' from the top of the dash source tree shows it being defined there)? Thanks, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Dash fails to build with the LFS 6.5 toolchain
On Sat, 15 Aug 2009 6:56:26 -0600, Matthew Burgess wrote: > I had a look at their mailing list archives [0] and couldn't see a similar > report > (and google couldn't either). That missing [0] reference is: http://www.mail-archive.com/d...@vger.kernel.org/ Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Dash fails to build with the LFS 6.5 toolchain
On Sat, 15 Aug 2009 13:51:31 +0100, Guy Dalziel wrote: > On Sat, Aug 15, 2009 at 06:45:38AM -0600, Matthew Burgess wrote: >> This is an upstream bug, and as such should be reported there. > > Do you have a URL for the ticket? No, I was suggesting that William report this upstream as I don't think we can figure out what values those defines should have. I had a look at their mailing list archives [0] and couldn't see a similar report (and google couldn't either). The bug would appear to be somewhere around the src/mkbuiltins stuff, but I don't have the desire to go debugging that amount of sed/awk/tr stuff for a package I don't use :-) Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: CDRTools fails to compile
On Sat, 15 Aug 2009 13:23:01 +0100, Guy Dalziel wrote: > See the attached patch, does this fix the issue? Yes, it does! Thanks very much Guy. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Dash fails to build with the LFS 6.5 toolchain
On Sat, 15 Aug 2009 07:41:01 -0400, William Immendorf wrote: > When I was trying to build Dash, I got these messages: > > if gcc -DHAVE_CONFIG_H -I. -I. -I.. -include ../config.h -DBSD=1 > -DSHELL -DIFS_BROKEN -Wall -g -O2 -MT eval.o -MD -MP -MF > ".deps/eval.Tpo" -c -o eval.o eval.c; \ > then mv -f ".deps/eval.Tpo" ".deps/eval.Po"; else rm -f > ".deps/eval.Tpo"; exit 1; fi > eval.c: In function ‘evalcommand’: > eval.c:810: error: ‘EXECCMD’ undeclared (first use in this function) > eval.c:810: error: (Each undeclared identifier is reported only once > eval.c:810: error: for each function it appears in.) > eval.c:812: error: ‘COMMANDCMD’ undeclared (first use in this > function) This is an upstream bug, and as such should be reported there. I think it should go in src/builtins.h, but that's generated from src/mkbuiltins, which in turn, reads src/builtins.def. Regards, Matt -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: CDRTools fails to compile
On Thu, 13 Aug 2009 19:40:24 -0700, Nathan Coulson wrote:
> I am having the following problems when compiling cdrtools with the latest
> book
> make[1]: Entering directory
> `/mnt/raid5/book/blfs/38/cdrtools-2.01/libschily'
> ==> COMPILING "OBJ/x86_64-linux-cc/fexec.o"
> In file included from ../include/unixstd.h:37,
> from fexec.c:33:
> /usr/include/unistd.h:524: error: conflicting types for 'fexecve_'
> ../include/schily.h:114: note: previous declaration of 'fexecve_' was here
> fexec.c: In function 'fexecle':
I can reproduce this on a clean LFS-6.5-rc2 build. It looks as it the
patch isn't enough to handle the getline, getdelim and fexecve functions in
newer Glibc's. The attached patch lets things build for me.
Regards,
Matt.Submitted By: Matt Burgess (matthew at linuxfromscratch dot org)
Date: 2009-08-14
Initial Package Version: 2.01
Origin: Matt Burgess
Upstream Status: Not submitted.
Description: Fixes several function conflicts that occur between Cdrtools and
Glibc 2.10.1.
diff -Naur cdrtools-2.01.orig/cdrecord/cue.c cdrtools-2.01/cdrecord/cue.c
--- cdrtools-2.01.orig/cdrecord/cue.c 2004-03-02 20:00:53.0 +
+++ cdrtools-2.01/cdrecord/cue.c 2009-08-15 11:39:28.0 +
@@ -249,7 +249,7 @@
LOCAL char *peekword __PR((void));
LOCAL char *lineend __PR((void));
LOCAL char *markword __PR((char *delim));
-LOCAL char getdelim __PR((void));
+LOCAL char getdelim_ __PR((void));
LOCAL char *getnextitem __PR((char *delim));
LOCAL char *neednextitem __PR((char *delim));
LOCAL char *nextword __PR((void));
@@ -772,7 +772,7 @@
if (kp == NULL)
cueabort("Unknown filetype '%s'", word);
- if (getdelim() == '/') {
+ if (getdelim_() == '/') {
word = needitem();
if (*astol(++word, &secsize) != '\0')
cueabort("Not a number '%s'", word);
@@ -1163,7 +1163,7 @@
}
LOCAL char
-getdelim()
+getdelim_()
{
return (wordendc);
}
diff -Naur cdrtools-2.01.orig/include/schily.h cdrtools-2.01/include/schily.h
--- cdrtools-2.01.orig/include/schily.h 2004-03-05 00:30:40.0 +
+++ cdrtools-2.01/include/schily.h 2009-08-15 11:40:34.0 +
@@ -108,7 +108,7 @@
/* 6th arg not const, fexecv forces av[ac] = NULL */
extern int fexecv __PR((const char *, FILE *, FILE *, FILE *, int,
char **));
-extern int fexecve __PR((const char *, FILE *, FILE *, FILE *,
+extern int fexecve_ __PR((const char *, FILE *, FILE *, FILE *,
char * const *, char * const *));
extern int fspawnv __PR((FILE *, FILE *, FILE *, int, char * const *));
extern int fspawnl __PR((FILE *, FILE *, FILE *,
@@ -187,7 +187,7 @@
extern char *findbytes __PR((const void *, int, char));
extern int findline __PR((const char *, char, const char *,
int, char **, int));
-extern int getline __PR((char *, int));
+extern int getline_ __PR((char *, int));
extern int getstr __PR((char *, int));
extern int breakline __PR((char *, char, char **, int));
extern int getallargs __PR((int *, char * const**, const char *, ...));
diff -Naur cdrtools-2.01.orig/libscg/scsitransp.c cdrtools-2.01/libscg/scsitransp.c
--- cdrtools-2.01.orig/libscg/scsitransp.c 2004-06-17 20:20:27.0 +
+++ cdrtools-2.01/libscg/scsitransp.c 2009-08-15 11:35:48.0 +
@@ -323,7 +323,7 @@
js_printf("%s", msg);
flush();
- if (getline(okbuf, sizeof (okbuf)) == EOF)
+ if (getline_(okbuf, sizeof (okbuf)) == EOF)
exit(EX_BAD);
if (streql(okbuf, "y") || streql(okbuf, "yes") ||
streql(okbuf, "Y") || streql(okbuf, "YES"))
diff -Naur cdrtools-2.01.orig/libschily/fexec.c cdrtools-2.01/libschily/fexec.c
--- cdrtools-2.01.orig/libschily/fexec.c 2004-06-06 11:50:24.0 +
+++ cdrtools-2.01/libschily/fexec.c 2009-08-15 11:40:59.0 +
@@ -159,7 +159,7 @@
} while (p != NULL);
va_end(args);
- ret = fexecve(name, in, out, err, av, env);
+ ret = fexecve_(name, in, out, err, av, env);
if (av != xav)
free(av);
return (ret);
@@ -173,11 +173,11 @@
char *av[];
{
av[ac] = NULL; /* force list to be null terminated */
- return (fexecve(name, in, out, err, av, environ));
+ return (fexecve_(name, in, out, err, av, environ));
}
EXPORT int
-fexecve(name, in, out, err, av, env)
+fexecve_(name, in, out, err, av, env)
const char *name;
FILE *in, *out, *err;
char * const av[], * const env[];
diff -Naur cdrtools-2.01.orig/readcd/io.c cdrtools-2.01/readcd/io.c
--- cdrtools-2.01.orig/readcd/io.c 2002-12-25 14:13:28.0 +
+++ cdrtools-2.01/readcd/io.c 2009-08-15 11:36:06.0 +
@@ -138,7 +138,7 @@
(*prt)(s, *lp, mini, maxi, dp);
flush();
line[0] = '\0';
- if (getline(line, 80) == EOF)
+ if (getline_(line, 80) == EOF)
exit(EX_BAD);
linep = skipwhite(line);
@@ -205,7 +205,7 @@
printf("%r", form, args);
va_end(args);
flush();
- if (getline(okbuf, sizeof(okbuf)) == EOF)
+ if (getline_(okbuf, sizeof(okbuf)) == EOF)
exit(EX_BAD);
if (okbuf[0] == '?') {
printf("Enter 'y', 'Y', 'yes' or 'YES' if you a
Re: Issue with signal.h
On Thu, 6 Aug 2009 13:49:28 +, William Immendorf wrote: > Hey, > > After installing acl/attr, when I compile coreutils/libcap, this happens: > > CC ls.o > In file included from /usr/include/bits/sigcontext.h:28, > from /usr/include/signal.h:339, > from ../lib/signal.h:34, > from ls.c:66: > /usr/include/asm/sigcontext.h:28: error: expected > specifier-qualifier-list before '__u64' > /usr/include/asm/sigcontext.h:191: error: expected > specifier-qualifier-list before '__u64' > > and make errors out. Can anyone please help me? The patch at http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-libs/libcap/files/libcap-2.16-drop-linux-workarounds.patch?rev=1.1 works for me, or at least enables me to get libcap compiled. I found this by simply googling for 'libcap sigcontext.h'. Coreutils-7.4 successfully detected libcap and has completed without any build errors. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
LFS-6.5-RC2 released
Hi, The Linux From Scratch community is pleased to announce the release of LFS Version 6.5 Release Candidate 2. This release includes numerous changes from LFS-6.4 (including updates to Linux-2.6.30.2, GCC-4.4.1, and Glibc-2.10.1) and security fixes. It also includes editorial work on the explanatory material throughout the book, improving both the clarity and accuracy of the text. You can read the book online[0], or download to read locally [1]. It is our intention to release LFS-6.5 final within 1 week. Please direct any comments about this release to the LFS development team at lfs-...@linuxfromscratch.org. Please note that registration for the lfs-dev mailing list is required to avoid junk email. [0] http://www.linuxfromscratch.org/lfs/view/6.5-rc2/ [1] http://www.linuxfromscratch.org/lfs/downloads/6.5-rc2/ Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
LFS-6.5-RC1 released
Hi, The Linux From Scratch community is pleased to announce the release of LFS Version 6.5 Release Candidate 1. This release includes numerous changes from LFS-6.4 (including updates to Linux-2.6.30.1, GCC-4.4.0, Glibc-2.10.1) and security fixes. It also includes editorial work on the explanatory material throughout the book, improving both the clarity and accuracy of the text. You can read the book online[0], or download to read locally [1]. It is our intention to release LFS-6.5 final within 2 weeks. Please direct any comments about this release to the LFS development team at lfs-...@linuxfromscratch.org. Please note that registration for the lfs-dev mailing list is required to avoid junk email. [0] http://www.linuxfromscratch.org/lfs/view/6.5-rc1/ [1] http://www.linuxfromscratch.org/lfs/downloads/6.5-rc1/ Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
RE: modules for different machines
On Sat, 11 Jul 2009 23:42:54 -0400, "Dave" wrote: > Hi, > Thanks. What i don't think i made clear is i currently have a > monolithic kernel running on lfs 6.4. If i made that kernel in to a > modular > kernel and compiled all the sound drivers as modules, then took that disk > and dropped it in to another box, how would the kernel autodetect the new > hardware, the audio cards wouldn't be the same, and load appropriate > modules? Please re-read http://www.linuxfromscratch.org/lfs/view/development/chapter07/udev.html and if anything there isn't clear, please forward any suggestions so that we can improve the book. Thanks, Matt PS: Please also re-read http://www.linuxfromscratch.org/faq/#netiquette - it's considered poor-form to top-post (i.e. write your reply above what it is you're replying to. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: HAL doesn't detect my cdrom(s)
On Sat, 16 May 2009 16:54:50 +1200, Simon Geard wrote: > On Thu, 2009-05-14 at 13:12 -0500, DJ Lucas wrote: >> Hehe...should've sent this Sunday as I had intended to do. The >> util-linux requirement kills the new release...have to wait till >> LFS-6.5/7.0. 0.5.11 seems to be stable with the udevadm patch, but I'll > >> review what the distros are doing too. > > Oh, and even better - util-linux 2.15 adds a hard dependency on > pkg-config, which it uses to find some of the libraries provided by > udev. Does that mean LFS will need to accept pkg-config into the core > book, in order to get the util-linux upgrade? Yes it does currently, as mentioned in http://wiki.linuxfromscratch.org/lfs/ticket/2391. However, there have been some autotools changes upstream since 2.15, so it may not be a requirement come 2.15.1. That said, it was already planned to migrate pkg-config across to LFS as so many packages are adopting it, it makes sense to have it part of a base system. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Help with Xlib and Xorg-apps
On Tue, 31 Mar 2009 15:05:52 -0500, William Immendorf wrote: > On Tue, Mar 31, 2009 at 10:53 AM, lux-integ > wrote: >> this is how I did it a while back (if it is of any help - my host > was >> amd64 -64BITonly kernel-2.6.27.7)):- Apologies for the obvious troll-feeding here everyone, but I just cannot let this slide: > This thing you sent me is NOT useful, send some REAL help next time. William, you obviously haven't learned have you? The above was incredibly rude and completely inappropriate for the LFS community mailing lists. You do not have the right to demand help from anyone (nor does anyone else on these lists). Help is provided on a voluntary basis, based on the time and knowledge of the list readers, and therefore no assumption should ever be made that you will have your problem solved (or even answered!). Obviously, we do have a lot of knowledgable folks who are willing to spend their time answering queries, and for that we are fortunate and should be grateful. If someone does provide assistance, but that doesn't rectify the issue you're seeing, common courtesy would be to thank them for their assistance, then explain to them what part of their advice didn't work for you and why not (e.g. I ran command x but it gave me error message y). Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: problems compiling pyKDE4//kde-workspace-4.2.0/yippiee!
On Sun, 1 Mar 2009 12:33:21 +, lux-integ wrote: > So before you make you small-minded remarks, read the postings of > someone > that engenders respect (KenMoffat) a generous and knowledgable person > with a long track record on BLFS and who has found my comments with the > building of KDE4 helpful -and I too his. Ha, maybe you should so some research before calling into question someone's knowledge/experience? (Bruce happens to be release manager for LFS, and a long-standing member of the LFS & BLFS editorial teams). All he was trying to do was provide a hint that maybe you should learn some 'netiquette'. There's no need to quote entire emails when you reply - just quote the relevant parts to your response. For example, see http://www.linuxfromscratch.org/pipermail/blfs-support/2009-February/065277.html which contains your original email. Ken replies, and then we all got http://www.linuxfromscratch.org/pipermail/blfs-support/2009-February/065281.html, which contains the entirety of your original email, plus Ken's response, plus your response to him, even though your response only pertained to one specific part of Ken's reply. As far as sharing his knowledge, the netiquette rules are already available at http://www.linuxfromscratch.org/faq/#netiquette and are linked to from http://www.linuxfromscratch.org/mail.html, which is in turn linked to from the BLFS book. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: when does sudo and sudoers get created?
On Sat, 20 Dec 2008 15:51:31 -0600, "Ralph Porter" wrote: > I must have missed a step. I do not have /usr/bin/sudo or /etc/sudoers > > What step has this install? http://www.linuxfromscratch.org/blfs/view/svn/postlfs/sudo.html (found using the index at http://www.linuxfromscratch.org/blfs/view/svn/longindex.html) Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Fwd: Xorg7.4-installation-xcursor-themes-1.0.1 compile problems
On Tue, 9 Dec 2008 10:56:59 +, b-vol <[EMAIL PROTECTED]> wrote: > ### after configure and make is executed:- ## > /usr/X11R7.4/bin/xcursorgen -p ../redglass ./X_cursor.cfg X_cursor > /usr/X11R7.4/bin/xcursorgen: error while loading shared libraries: > libX11.so.6: cannot open shared object file: No such file or director > > > but ls returns libX11.so.6 in /usr/X11R7.4/lib:- # Is /usr/X11R7.4/lib/ in LD_LIBRARY_PATH, and have you run 'ldconfig'? Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: GCC - 4.2.1 fails to build on LFS 6.1
On Thu, 14 Aug 2008 15:37:20 +, "Cliff McDiarmid" <[EMAIL PROTECTED]> wrote: > I usually just Google the error message but >> it's finding nothing useful with this one. Any progress? > > I did the same and found very little. There was a suggestion it might be > a bug, but that's out because gcc-4.3 also fails at his point. It may be a bug, but one in the LFS-6.1 version of gcc (3.4.3), which is very old. You may have to do incremental upgrades to get up to a version of gcc that is able to compile 4.2.1. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: sed question
On Wed, 30 Jan 2008 21:51:56 +0100, Olaf Grüttner <[EMAIL PROTECTED]> wrote: > Hi everyone, > > I have a question about working with sed. > I have an xml file containing > 1 > > I want to change this to > 2 > > I have problems with the "<" and ">" signs. Is there a was to mask them > in the sed command? > > sed s/"1"/"2"/g' test.xml > > does not work You can either change the field separator from '/' to any other character, e.g. '@': [EMAIL PROTECTED]:~$ cat test.xml 1 [EMAIL PROTECTED]:~$ sed -e 's@1@2@g' test.xml Or you can escape that field separator using '\': [EMAIL PROTECTED]:~$ cat test.xml 1 [EMAIL PROTECTED]:~$ sed -e 's/1<\/them>/2<\/theme>/g' test.xml 1 Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Fw: How to read BLFS in LFS
On Tue, 9 Oct 2007 21:11:03 -0700 (PDT), Walter Barnes <[EMAIL PROTECTED]> wrote: >>From: Dan Nicholson <[EMAIL PROTECTED]> > >>On 10/9/07, Walter Barnes <[EMAIL PROTECTED]> wrote: >>> >>> Providing BLFS in info format does not require dumbing down *LFS or > making any other major changes to its content. All that's required is to > put aside what one likes or dislikes and consider that Texinfo is a part of > LFS so why not provide BLFS in info format? >> >>Do you really know that? Do you know how the LFS books are produced? >>It's not just personal taste that dictates these things. > > No, I do not know how the LFS books are produced. If selecting a > particular format for presentation would require changes to the content > material (as in added/removed/edited sections, paragraphs, etc.) then I > stand corrected. The books are written in XML (actually, a particular XML dialect called DocBook). These sources can then be processed to produce a number of different output formats, HTML & PDF being two of them. The stylesheet package we use can also produce man pages, but by default, there's no texinfo conversion stylesheets available. That said, I think the man page output requires particular markup which is unsuitable for the other output formats. I'm not sure quite how helpful having BLFS available in an "LFS-native" format would be. You said you'd need dhcpcd installed in order to bring your network interface up. Although, if we were to produce texinfo/man page versions of the book, you'd obviously be able to read the instructions for compiling it, but how are you going to obtain the source package? If, as I suspect, you're going to have to rely on your host system in order to download it, why can't you also rely on your host system to browse the LFS book until such time as you have a HTML/PDF reader available? We used to also produce plain text output for at least LFS. That might also be an option here and such a stylesheet would *probably* be trivial as there's only certain amounts of formatting one can apply. The resultant .txt file would be pretty unwieldy to navigate for something the size of BLFS though. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: What values do I give the X11_CFLAGS X11_LIBS variables?
On Saturday 30 June 2007 16:00:56 Georgina Joyce wrote: > In working through 28 June 2007 blfs, I'm attempting to build the Xorg > libraries. However, I'm getting the error below: I observed the > PKG_CONFIG_PATH and set that to /usr/lib/pkgconfig as that appeared to be > the correct path but it hasn't changed the error, which suggests that it is > not a path error but I guess it is a path error. What values should I > export to cflags and libs? > > checking if /usr/bin/cpp requires -undef... yes > checking if /usr/bin/cpp requires -traditional... yes > checking whether to use XCB... (cached) yes > checking for pkg-config... /usr/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking for XPROTO... yes > checking for X11... configure: error: Package requirements (xextproto > xtrans xcb-xlib >= 0.9.92) were not met: > > No package 'xcb-xlib' found I got exactly this error just yesterday. See http://linuxfromscratch.org/pipermail/blfs-dev/2007-June/017326.html. The easiest solution to this is to pass "--without-xcb" to ./configure, as documented in the Command Explanations section of the XOrg Libraries page in BLFS. Alternatively, you might want to consider installing libpthread-stubs and libxcb, but note Alexander's response to my message linked to above where XCB isn't recommended at this point in time. Regards, -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: php and sql [slightly OT]
On Monday 12 March 2007 20:47, Alan Lord wrote: > Yes there are quite a few differences between Postgresql and MySQL in > syntax, SQL implementation (PGSQL is fully ACID compliant whereas MySQL > is apparently not) MySQL is actually ACID compliant, but only if you use the InnoDB storage engine. InnoDB is *not* the default storage engine - for some strange reason upstream provide a default (MyISAM) that has non-ACID transactions on tables that don't support referential integrity via foreign key constraints. Quite how that equates to a relational database I have no idea! Personally, I use PostgreSQL wherever possible. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Building software as an unprivileged user
On Friday 02 March 2007 11:49, TheOldFellow wrote: > The only difficulty with JHALFS is if you want to build ALMOST what's in > the book. Like, for instance, I don't want the old sysvinit or Berk's > DB or Man-db or Syslog, but all the rest please. Now JHALFS isn't so good. I'd probably handle this as a locally maintained set of patches on top of the LFS book, then run jhalfs against that working copy. I don't think you're going to hit too many merge conflicts with those kind of changes as your replacement package XML files will obviously be entire files, and chapter06/chapter06.xml changes very infrequently. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: KDE - error reeports at start and stop
Shawn wrote: Jerzy: You compiled ipv6 support into X but you are not running ipv6. To get rid of this you need to rebuild X without ipv6 ( maybe somebody knows a runtime switch??? ). '-nolisten inet6' should do it. (see http://www.xfree86.org/4.4.0/RELNOTES2.html) Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Opera 9.02
[EMAIL PROTECTED] wrote: It's a great web browser, but only available as a binary. Which, IMO, makes it not great at all. Free software is not about its initial cost (in monetary terms) it's about Freedom (see http://www.gnu.org/philosophy/free-sw.html). Then, since I don't have internet access on my LFS laptop, does anyone know the dependencies of Opera? If it's binary only, running `nm' or `ldd' on the main opera binary should show its runtime dependencies. Obviously, its build time dependencies are not important, as the source code isn't available to build from. And finally, I think Opera would be a great add to BLFS. I think it's Way better than Firefox. But, BLFS is only interested in building from source. If the source code to Opera isn't available I don't see how instructions for building it can possibly be added. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: reiserfs-3.6.19 - Missing asm header?
Alan Lord wrote: Just a quick note; not sure if this is LFS or BLFS... It's a BLFS problem, caused by LFS :-) (yes, I love sitting on the fence!). On building the above tools, the make barfed because it couldn't find /usr/include/asm/unaligned.h Maybe this is something to do with the new header-install malarkey??? Yes, it is. http://comments.gmane.org/gmane.linux.kernel/458284 discusses the issue and points to the correct fix at http://cvs.fedora.redhat.com/viewcvs/rpms/reiserfs-utils/devel/header-fix.patch?view=markup Hope this helps, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: changes with new video card
Simon Geard wrote: On Tue, 2006-10-17 at 16:03 -0700, Arden wrote: Help! I need some advice. I have just gotten into the blfs-book, so far I have X running, and a friend gave me a video card, EVGA GeForceMX 4000. Can I get this working? without much trouble? [snip] Shouldn't be a problem if you're happy to use the binary-only drivers from nVidia. No kernel or Xorg recompiling needed - just get run the installer and edit Xorg.conf to use the right driver (nvidia, not nv). Note, though, that the binary only driver is not *required* it just happens to be useful if you want decent performance in 3D games and the like. Myself, I just use the 'nv' driver in Xorg. If you do use the NVidia driver make sure to get the latest version as it apparently fixes a security vulnerability in previous versions (being binary only, noone but NVidia knows for sure whether it's fixed or not, or whether any similar vulnerabilities still remain) - http://lists.freedesktop.org/archives/xorg/2006-October/018833.html Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: MesaLib-6.5.1
Dan Nicholson wrote:
You could probably use this diff or something
close to it. There's been one more commit since then to expand the
*.{c,h}. It could be _way_ better, but I erred on the conservative side
for maximum shell compatibility.
Thanks, Dan. Unfortunately, I still can't get xorg-server-1.1.0 to
compile against MesaLib-6.5.1. Here's the latest error which is proving
elusive in tracking down (several other errors follow it, but they're
all pretty similar so getting this one should fix the others):
../../GL/mesa/.libs/libGLcore.a(driverfuncs.o): In function
`_mesa_init_driver_functions':
drivers/common/driverfuncs.c:225: undefined reference to
`_mesa_new_array_object'
The command line is ridiculously long, but it's when it's trying to
compile the stuff in hw/vfb.
Now, driverfuncs.o shouldn't have an undefined reference to
_mesa_new_array_object as it #includes arrayobj.h. The only thing I can
think of is that the command line that compiles driverfuncs.o doesn't -L
libMain.la. Even if that would fix it, I can't find the relevant
Makefile bit to change! I think I'm just going to give up and revert to
MesaLib-6.5. At this rate, by the time I've fixed all this up, Xorg-7.2
will be out which will either work out of the box or bring with it a
whole lot more pain.
Regards,
Matt.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: MesaLib-6.5.1
Matthew Burgess wrote: Sure enough, there's no slang_version_syn.h in that directory. There is a slang_pp_version.h though. Looks like they renamed it as mentioned in http://lists.freedesktop.org/archives/xorg/2006-August/017735.html. Our very own Dan Nicholson adds his thoughts in that thread as well...nice of you to warn me I was gonna hit this, mate :-) Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: MesaLib-6.5.1
Matthew Burgess wrote: Dan Nicholson wrote: On 10/5/06, Matthew Burgess <[EMAIL PROTECTED]> wrote: doc/install.html just mentions 'make install'. Having never touched Mesa before, I've no idea why one would want to use 'bin/installmesa' as opposed to 'make install'. The developer just added the `make install' target a couple months ago. http://gitweb.freedesktop.org/?p=users/krh/mesa.git;a=commit;h=37d6682b5536d170f4ae8dbf947fe31b7632157b You can pass INSTALL_DIR and DRI_DRIVER_INSTALL_DIR if you want to do a DESTDIR style install. See configs/default like Luca said. Thanks, that's good to know. When I tried 'make install' I couldn't get it to install anywhere other than /usr/local so I simply reverted to Mesa-6.5. Now that I'm rebuilding again anyway I'll give 6.5.1 another shot. Well, I got it to install thanks to those 2 variables. Now xorg-server doesn't like it: Creating destination directories for glx module ... DONE Checking that the source files exist for mesa module ... error: /sources/blfs/Mesa-6.5.1/src/mesa/shader/slang/library/slang_version_syn.h not found configure: error: Failed to link Mesa source tree. Please specify a proper path to Mesa sources, or disable GLX. make: *** [xorg-server] Error 1 Sure enough, there's no slang_version_syn.h in that directory. There is a slang_pp_version.h though. Was this another thing that temporarily went AWOL in this release? I see it at http://gitweb.freedesktop.org/?p=users/krh/mesa.git;a=tree;h=69d0dc43d295a151c933f4149fe1db93e9e3bf3f;hb=80e4964754a0348c10a09e359f119b633f4f658d;f=src/mesa/shader/slang/library (uggh, I hate gitweb URLs!) but I don't know enough about git to determine what branches/tags it was included in. Thanks, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: MesaLib-6.5.1
Dan Nicholson wrote: On 10/5/06, Matthew Burgess <[EMAIL PROTECTED]> wrote: doc/install.html just mentions 'make install'. Having never touched Mesa before, I've no idea why one would want to use 'bin/installmesa' as opposed to 'make install'. The developer just added the `make install' target a couple months ago. http://gitweb.freedesktop.org/?p=users/krh/mesa.git;a=commit;h=37d6682b5536d170f4ae8dbf947fe31b7632157b You can pass INSTALL_DIR and DRI_DRIVER_INSTALL_DIR if you want to do a DESTDIR style install. See configs/default like Luca said. Thanks, that's good to know. When I tried 'make install' I couldn't get it to install anywhere other than /usr/local so I simply reverted to Mesa-6.5. Now that I'm rebuilding again anyway I'll give 6.5.1 another shot. Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: kdebase vs. linux headers
Rainer Peter Feller wrote: Just a wilde guess but may be /usr/include/linux/joystick.h should not inclde asm/types.h but linux/types.h ... I thought the same thing at first, but linux/types.h has the same guards around it! Anyway, this has now been reported upstream and the linux-headers guys are trying to fathom out what the best approach is. Thanks, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
kdebase vs. linux headers
Hi folks, I'm trying to compile kdebase-3.5.4 against the headers installed via 'make headers_install' from linux-2.6.18. Unfortunately, I get this error: error: '__s64' does not name a type /usr/include/linux/joystick.h:132: error: '__s64' does not name a type Now, obviously that's not good, but I don't think it's kdebase's fault (linux/joystick.h is installed afterall, so they're using a permitted API). The problem seems to be that linux/joystick.h is #including asm/types.h which only typedefs __s64 if __GNUC__ is defined and __STRICT_ANSI__ isn't defined: #if defined(__GNUC__) && !defined(__STRICT_ANSI__) typedef __signed__ long long __s64; typedef unsigned long long __u64; #endif I can only presume, because of the error above, that those conditions aren't being met, but a cursory glance of the logfile doesn't appear to help me ascertain which one of them is triggering the problem above. Any ideas, folks? Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
MesaLib-6.5.1
Hi folks, The file bin/installmesa appears to be missing from the latest version of MesaLib. Does anyone know whether this is just a packaging error on their part or whether there's a different mechanism for installing the package? The release notes didn't mention it. doc/install.html just mentions 'make install'. Having never touched Mesa before, I've no idea why one would want to use 'bin/installmesa' as opposed to 'make install'. Thanks, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: cdrkit, yet another cdrecord fork
Jörg W Mittag wrote: Matthew Burgess wrote: So, another case of NIH syndrome. Rather than report bugs/offer patches to existing projects (tar vs. star, make vs. smake, etc.) he goes and reinvents the wheel. Oh well, I guess it's his time to waste :-) So, yes there *is* a case of NIH syndrome and reinventing the wheel, but the other way round. Wow, thanks for the history lesson! Looks like I need to improve my research skills! However, please note that reinventing the wheel is not necessarily a bad thing thing if the owner of said wheel is a sociopath ... Quite. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: xine-lib fails to compile video_out_xmmc.c
> The configure check looks bogus. As a workaround, try adding > "ac_have_xxmc=no" to your configure line. Actually, passing "--without-xxmc-path --without-xxmc-lib" disables the plugin! It's now compiled and installed without a problem. Whether I can get Kaffeine to link and work against it is a job for tomorrow though. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: xine-lib fails to compile video_out_xmmc.c
> On Tue, May 30, 2006 at 07:04:53PM -0400, Chris Staub wrote: >> >> I've gotten the same kind of errors, and I have Xorg 7.0. > > I have xorg 7.0 and xine built and runs fine. :/ Does config.log say that the 'xxmc' plugin is going to be enabled? I get: checking whether to enable the xxmc plugin with vld extensions... checking for XvMCPutSlice in -lXvMCW... yes checking X11/extensions/vldXvMC.h usability... yes checking X11/extensions/vldXvMC.h presence... yes checking for X11/extensions/vldXvMC.h... yes checking X11/extensions/XvMC.h usability... yes checking X11/extensions/XvMC.h presence... yes checking for X11/extensions/XvMC.h... yes *** Enabling xxmc plugin with vld extensions. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
xine-lib fails to compile video_out_xmmc.c
Hi folks, I've probably forgotten to do something really simple again, but would appreciate a cluebat here. I'm trying to compile xine-lib-1.1.1 with Xorg 7.1 installed but am running into: gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../.. -I../../include -I../../include -I../../src -I../../src/xine-engine -I../../src/xine-engine -I../../src/xine-utils -I../../src/input -I../../src/input -I../../lib -DXINE_COMPILE -I../../src/video_out/vidix -I../../src/video_out/vidix -mtune=athlon -O3 -pipe -fomit-frame-pointer -falign-functions=4 -falign-loops=4 -falign-jumps=4 -mpreferred-stack-boundary=2 -fexpensive-optimizations -fschedule-insns2 -fno-strict-aliasing -ffast-math -finline-functions -Wall -Wnested-externs -Wcast-align -Wchar-subscripts -Wmissing-declarations -Wmissing-prototypes -DNDEBUG -D_REENTRANT -D_FILE_OFFSET_BITS=64 -DXINE_COMPILE -MT video_out_xxmc.lo -MD -MP -MF .deps/video_out_xxmc.Tpo -c video_out_xxmc.c -fPIC -DPIC -o .libs/video_out_xxmc.o video_out_xxmc.c:46: error: syntax error before '*' token video_out_xxmc.c:48: error: syntax error before '*' token [snip really long list of similar looking errors] Has anyone seen this before? I'd really just like to disable the xxmc library as it requires binary drivers, IIUC, but --without-xmmc-path, --with-xmmc-path="", etc. all still result in xine-lib finding the magic headers and libs in /usr/X11. The relevant lines of video_out_xxmc.c are: static void xxmc_frame_updates(xxmc_driver_t *driver, xxmc_frame_t *frame, int init_macroblocks); static void dispose_ximage (xxmc_driver_t *this, XShmSegmentInfo *shminfo, XvImage *myimage); Now, 'xxmc_driver_t' looks the likely culprit here, but its definition is in 'xmmc.h' which gets #included from video_out_xmmc.c, so I'm now at a loss :-( Thanks, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: KDM displaying squares instead of text
Dan Nicholson wrote:
On 5/29/06, Matthew Burgess <[EMAIL PROTECTED]> wrote:
On a fresh build of LFS-SVN and BLFS-SVN I've just gotten kdebase
installed. On trying to login via KDM all I see is squares in place of
every single character of text that should be on that screen.
>
I'm sure KDM is using fontconfig to render the fonts. In that case,
do you have any output from the command fc-list?
Nope, nada...see below!
> Note that there are now instructions at the
end of all the X installations to symlink from
/usr/share/fonts/X11-{TTF,OTF} -> /usr/lib/X11/fonts/{TTF,OTF}. This
should give you at least a few fonts to work with under Fontconfig if
you don't plan to install any more.
Yep, thanks Dan. That's exactly what I'd missed doing. Well, my
scripts missed doing it, it's never my fault, you have to understand! :-)
Now having launched KDM it's pretty obvious I'm going to have to install
some more fonts as the default ones just look ugly.
Thanks again,
Matt.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
KDM displaying squares instead of text
Hi folks, On a fresh build of LFS-SVN and BLFS-SVN I've just gotten kdebase installed. On trying to login via KDM all I see is squares in place of every single character of text that should be on that screen. I'm assuming it's some kind of font/utf-8 issue but haven't the foggiest what it might be. Any ideas? Or is there any more information I can provide that might nail this one on its head? The only thing that shows up in /var/log/kdm.log is: FreeFontPath: FPE "/usr/lib/X11/fonts/misc/" refcount is 2, should be 1; fixing. I've not installed any fonts yet and my FontPath section of /var/log/X11/xorg.conf looks like: FontPath "/usr/lib/X11/fonts/misc/" FontPath "/usr/lib/X11/fonts/TTF/" FontPath "/usr/lib/X11/fonts/OTF" FontPath "/usr/lib/X11/fonts/Type1/" #FontPath "/usr/lib/X11/fonts/CID/" FontPath "/usr/lib/X11/fonts/100dpi/" FontPath "/usr/lib/X11/fonts/75dpi/" #FontPath "/usr/lib/X11/fonts/local/" FontPath "/usr/lib/X11/fonts/Speedo/" #FontPath "/usr/lib/X11/fonts/TrueType/" #FontPath "/usr/lib/X11/fonts/freefont/" Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
LFS-6.1.1 released
The Linux From Scratch community is pleased to announce the release of LFS 6.1.1. This release includes fixes for all known errata since LFS-6.1 was released 4 months ago. You can read the book online at http://www.linuxfromscratch.org/lfs/view/6.1.1/ or download it from http://www.linuxfromscratch.org/lfs/downloads/6.1.1/ to read locally. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
LFS-6.1.1-pre2 Released
The Linux From Scratch community is pleased to announce the second pre-release of LFS 6.1.1. In addition to the fixes already made in LFS-6.1.1-pre1, this release addresses a bug in Glibc that prevents some programs (including OpenOffice.org) from running. You can read the book online at http://www.linuxfromscratch.org/lfs/view/6.1.1-pre2/ or download it from http://www.linuxfromscratch.org/lfs/downloads/6.1.1-pre2/ to read locally. This being a test release, we would appreciate you taking the time to try it out and report any bugs you find in it to the LFS development team at [EMAIL PROTECTED] The final release is planned for Wednesday 30th November. Best regards, Matthew Burgess -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
LFS-6.1.1-pre1 Released
The Linux From Scratch community is pleased to announce the first pre-release of LFS 6.1.1. This release includes fixes for all known errata since LFS-6.1 was released 4 months ago. You can read the book online at http://www.linuxfromscratch.org/lfs/view/6.1.1-pre1/ or download to read locally from http://www.linuxfromscratch.org/lfs/downloads/6.1.1-pre1/ This being a test release, we would appreciate you taking the time to try it out and report any bugs you find in it to the LFS development team at [EMAIL PROTECTED] The final release is planned for Saturday 26th November. A special note of thanks to Archaic for his assistance with all the behind the scenes activities that went into this release. His release scripts and notes as have been a massive time saver! Archaic, you're a star! Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: openssh closes connection after username is sent
Archaic wrote: On Thu, Oct 27, 2005 at 02:57:34PM -0700, Dan Nicholson wrote: Um, I just realized I have no idea how the website is generated. What's the proper way to pull the html for website? Plus 's/lfs-book/website/' above. svn export svn://svn.linuxfromscratch.org/www2 I think you meant `svn checkout' there, not `svn export'. Without the '.svn' directories, I don't think 'svn diff > website.patch' will work. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: openssh closes connection after username is sent
Dan Nicholson wrote: I understand that. That's what the Errata is for. Until 6.1.1 is released (if it is), this patch should probably appear there so people don't continue to run into this problem. Not everybody builds SVN. We (in this instance "we = website project") accept patches :-) Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: openssh closes connection after username is sent
Steve Prior wrote: This is actually one of the reasons that a LFS 6.1.1 release was agreed to, though I haven't seen much progress in getting that out the door. Err, have you been following lfs-book at all? If so you'll have seen there's been a reasonable amount of work done on the 6.1.1 branch (a.k.a. 'testing'). Obviously this stuff takes time, sorry if it isn't fast enough for you but this is a voluntary project you know :/ Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: running *.ogg files ith alsa
mess-mate wrote: Hi, after installing alsa (card detected:cmpci) can't run any *.ogg file on kde. I've installed vorbis and the ogg-lib but nothing helps. Any hint ?? Does ogg123 play them without any problems? -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
