On Tuesday 25 April 2006 07:28, Matt Darcy wrote:
>
> lspci has nothing to do with the kernel, it simply maps device ID's to
> haardware information stored in the pci.id's file.
>
Does this mean it might be possible, with a minimal kernel and lspci to figure
out the proper kernel config settings f
Hi,
> I've been thinking about a construction some time now, and that's using the
> extended attributes to identify a package. This is a variant of the hint
> "more_control_and_pkg_man.txt" by Matthias Benkmann.
This sounds really good. I don't think about using these for primary
way of t
Yes in output of pkg-config --cflags gstreamer-0.8 is
-I/usr/include/gstreamer-0.8:
--
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -pthread
-I/usr/include/gstreamer-0.8 -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -I/usr/include
I found the error, I make mistake in instalation of package nss.
Filip Bartmann
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Filip Bartmann wrote:
I install Firefox, Thundenbird and Seamonkey with system nss.
But when I try to install others programs, which needs gecko(as yelp,
epiphany and galeon), then these programs can't find gecko. Where are
gecko in default installed?
When you say "these programs can't find gec
Filip Bartmann wrote:
I install Firefox, Thundenbird and Seamonkey with system nss.
But when I try to install others programs, which needs gecko(as yelp,
epiphany and galeon), then these programs can't find gecko. Where are
gecko in default installed?
When you say "these programs can't find gec
On Wednesday 26 April 2006 01:58, DJ Lucas wrote:
> linux23dragon wrote:
> > Dan, I've found out how to set up the user environment, which fixes the
> > library linking issue.
> >
> > export LIBRARY_PATH=/usr/lib:/usr/local/lib:/opt/lib
>
> No, not per user, it should be done globally, and not by t
On 4/26/06, David BOURIAUD <[EMAIL PROTECTED]> wrote:
> All went fine, but I still have the same errors when I try to install KDE.
Could you show those errors again? I can't recall what the problem was.
> Could it be possible that packages provided by BLFS6.1 are too old to compile
> KDE ?
Poss
On Tue, 2006-04-25 at 19:32 +0200, Stef Bon wrote:
> Hello,
> In short, by installing the acl-attr packages (there is a hint about that
> too), you should be able to add any information (metadata) to an file and
> directory. For example the packagename, buildtime, packageversion etcetera.
> It's p
