On Die, 2006-03-14 at 21:49 -0600, DJ Lucas wrote:
> Jürg. I haven't really looked into it, other than a grep through glibc
> source, but would it be acceptable to replace these headers with
> something like the following (example taken from llh linux/socket.h):
>
>
Dan Nicholson wrote:
my plan is:
* Add --libdir=/usr/share to the Fonts section of xorg7.xml with note that
the fonts will end up in /usr/share/X11/fonts with the switch.
Won't installing the fonts in /usr/share recreate the bug Alexander is
complaining about?
* Add #define FontDir /usr/
On 3/13/06, Chris Staub <[EMAIL PROTECTED]> wrote:
> OK, I've got the dependency list done -
> http://linuxfromscratch.org/~chris/dependencies.txt. Probably still not
> complete, but it's about as close as I'll ever get.
Chris, here's what's in my (pathetic compared to yours) dependency notes:
ht
Dan Nicholson wrote:
Now I'm confused. So, the effect you were after *really* was:
1. Configure fontconfig with --without-add-fonts
2. Let X install its fonts in the default location ($XORG_PREFIX/lib/X11/fonts)
3. Symlink /usr/share/fonts/X11-{OTF,TTF} ->
$XORG_PREFIX/lib/X11/fonts/{OTF,TTF}
Dan Nicholson wrote:
Chris, here's what's in my (pathetic compared to yours) dependency notes:
http://www.linuxfromscratch.org/~dnicholson/dn-dependencies.txt
What I have that's not in yours.
* Man-DB: depends on flex
* Kbd: depends on gettext
* Tar: depends on bison and inetutils
All have b
Hi all,
GNOME-2 installation is accomplished by setting a GNOME_PREFIX,
installing the first GNOME package (ORBit2) and then every other
package is installed using the $prefix of the ORBit2 installation
as the prefix for everything else. The $prefix of the ORBit
installation discovered using pkg-c
Hi all,
Hopefully the name of the two different threads is not so similar that
it looks to all as one thread. :-)
I'm adding K3b to the book. Some preliminary testing has shown that
it will work when installed in a prefix other than $KDE_PREFIX. Note
that this is limited testing and most of my ex
Randy McMurchy wrote:
> Hi all,
>
> Hopefully the name of the two different threads is not so similar that
> it looks to all as one thread. :-)
>
> I'm adding K3b to the book. Some preliminary testing has shown that
> it will work when installed in a prefix other than $KDE_PREFIX. Note
> that thi
Randy McMurchy wrote:
> Hi all,
>
> ./configure --prefix=$(kde-config --prefix)
>
> Thoughts?
>
Neat. I like it.
R.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
On 3/15/06, Chris Staub <[EMAIL PROTECTED]> wrote:
> >
> > * Bison must be installed before...tar
> > * Flex must be installed before...Iproute2 Man-DB
> > * E2fsprogs must be installed before...Util-linux
You didn't mention these. Are they OK to go in, or do you want me to
dig up the rationale?
>Having done some research on this, Jim's script (with all the help he's
>been getting on the lists and IRC) looks like the best bet. It's also
>the 'Right Way Forward' (tm), as it will deal with the increasing
>complexity of the Linux kernel. The trick will be making it work for
>all the arches
Dan Nicholson wrote:
On 3/15/06, Chris Staub <[EMAIL PROTECTED]> wrote:
* Bison must be installed before...tar
* Flex must be installed before...Iproute2 Man-DB
* E2fsprogs must be installed before...Util-linux
You didn't mention these. Are they OK to go in, or do you want me to
dig up the ra
On Wednesday 15 March 2006 19:36, Roger Blake wrote:
> >Having done some research on this, Jim's script (with all the help he's
> >been getting on the lists and IRC) looks like the best bet. It's also
> >the 'Right Way Forward' (tm), as it will deal with the increasing
> >complexity of the Lin
Thomas Reitelbach wrote:
My thought of the logic:
content of mykernelheader.h:
<...>
/* BEGIN USERSPACE HEADER */
...
...some header important for userspace...
...
/* END USERSPACE HEADER */
<...>
If think that's essentially what the #ifdef __KERNEL__ guards do in
Hi,
> > ./configure --prefix=$(kde-config --prefix)
> >
> > This way, you are essentially assured that the entire KDE
> > installation will be in the correct prefix, even if someone later
> > resumes installing KDE and forgets to set the $KDE_PREFIX.
> Hmm, here you may assume that the install is
Alexander E. Patrakov wrote:
I treat the ticket 1720 as presumably-closed if the bootscript changes
below are implemented, and the udev_update branch can be merged then.
I made the necessary changes to the bootscripts in r7433. I'll wait
until a snapshot tarball is available before making th
On Wed, 15 Mar 2006, Roger Blake wrote:
Although the script might be a good *short term* plan I think an adequate
long term solution requires a complete evaluation of *each* header -
identifying what code to delete or include. From what I can see the majority
of these headers are NOT required
Some type of userspace setup is planned for 2.7, just no details at this
time.
--
--
[EMAIL PROTECTED]
[EMAIL PROTECTED]
LFS User # 2577
Registered Linux User # 299986
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the abo
On Mit, 2006-03-15 at 20:02 +, Matthew Burgess wrote:
> Unfortunately, as Jurg points out earlier in this thread, there are
> plenty of headers that are missing those guards and I'm not entirely
> sure that such guards are a complete solution (if they were I don't
> think all the hairy looki
On Wed, 15 Mar 2006 19:11:22 +0100, Marc St-Jacques wrote:
> The SSL FAQ on the gaim web site doesn't mention compiling libtasn1
> before gnuTLS. So when compiling gnuTLS, one gets the following message:
>
> *** LibtASN1 0.2.x was not found. Will use the included one.
>
> The compiling of gnuTL
On Mit, 2006-03-15 at 21:06 +, Ken Moffat wrote:
> On Wed, 15 Mar 2006, Roger Blake wrote:
>
> > Although the script might be a good *short term* plan I think an adequate
> > long term solution requires a complete evaluation of *each* header -
> > identifying what code to delete or include.
On 3/2/06, Gerard Beekmans <[EMAIL PROTECTED]> wrote:
>
> Ag, I noticed you submitted a patch for 'su.' Thanks for your work but
> it seems we may not be using the patch if the new shadow package is
> released after the weekend as indicated by shadow's developer(s). Thanks
> for the contribution, t
On Wed, 15 Mar 2006, J�rg Billeter wrote:
I've now built about 550 packages on x86 and on x86_64 with my generated
header set and besides the few problems already mentioned before I've
got only two additional problems in the last 300 packages (one needed
header was missing and I had to add --wit
On Wed, 15 Mar 2006, Dan Nicholson wrote:
Shadow-4.0.15 hasn't been "officially" released, but there is a tarball in
ftp://ftp.pld.org.pl/software/shadow/snapshot/shadow-4.0.15.tar.bz2
coinciding with this post the other day:
http://mail.pld.org.pl/mailman/pipermail/shadow/2006-March/000262.
On 3/15/06, Ken Moffat <[EMAIL PROTECTED]> wrote:
>
> One reason it isn't in the book is that snapshots aren't the same as
> releases, despite the vagueness in the name of the tarball ;) I agree
> it compiles ok and su -c seems to work, but I haven't got as far as
> trying to use it in my curren
Jim Gifford wrote:
> Some type of userspace setup is planned for 2.7, just no details at this
> time.
Could you give some more specifics on that? I, too, remeber that
there was indeed something planned for 2.7, but that was waaay back
when there was gonna *be* a 2.7. Now we know that there won'
Dan Nicholson wrote:
> On 3/15/06, Alexander E. Patrakov <[EMAIL PROTECTED]> wrote:
>> Dan Nicholson wrote:
>>> Now I'm confused. So, the effect you were after *really* was:
>>>
>>> 1. Configure fontconfig with --without-add-fonts
>>> 2. Let X install its fonts in the default location
>>> ($XORG_
Randy McMurchy wrote:
> Where should K3b be installed, /usr or $KDE_PREFIX?
Judging from the other comments, $KDE_PREFIX.
I also note that the web page says:
K3b 0.12 Requirements
* KDE >= 3.2 - KDE is the great window manager, the powerful
desktop, the very powerful c++ library K3b is ba
Chris Staub wrote:
Dan Nicholson wrote:
Sorry...those look valid to me...I've updated my own list to reflect
them. The E2fsprogs -> Util-Linux dep. was already there. :)
On another note: I've removed the notes about Bzip2 and Gzip needing to
be installed before tar. It seems tar will build
Tim van der Molen wrote:
The --prefix="" argument to configure causes dhcpcd's manual page to be
installed in /man instead of /usr/share/man. I suggest adding
--mandir=/usr/share/man to configure's arguments.
Tim
Sorry bout that. I completely missed it:
[EMAIL PROTECTED] BOOK]# ls -l /dhcpcd
For automation LFS, I've writtten the script
accordnig to instruction from chapter 5:
http://www.dzti.edu.lv/isp-serv/a7/lfs-toolkit.txt
For building I use LiveCD:
http://ftp.osuosl.org/pub/lfs-livecd/lfslivecd-x86-6.2-pre3.iso
I've mounted /dev/sda4, then setup network and sshd,
copied needed
Andrejs Spunitis wrote:
For automation LFS, I've writtten the script
accordnig to instruction from chapter 5:
http://www.dzti.edu.lv/isp-serv/a7/lfs-toolkit.txt
For building I use LiveCD:
http://ftp.osuosl.org/pub/lfs-livecd/lfslivecd-x86-6.2-pre3.iso
I've mounted /dev/sda4, then setup network
BTW, why did you install e2fsprogs into /tools? If you issues with the
mount program not finding blkid and/or uuid, then it's only because you
haven't followed the book's instructions.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe:
On 3/18/07, Andrejs Spunitis <[EMAIL PROTECTED]> wrote:
>
> For automation LFS, I've writtten the script
> accordnig to instruction from chapter 5:
> http://www.dzti.edu.lv/isp-serv/a7/lfs-toolkit.txt
> # nohup ./lfs-toolkit.sh &
I see a few bad ideas about how you decide to script this. Mostly
On Don, 2006-03-16 at 00:41 +0100, Jörg W Mittag wrote:
> Jim Gifford wrote:
> > Some type of userspace setup is planned for 2.7, just no details at this
> > time.
>
> Could you give some more specifics on that? I, too, remeber that
> there was indeed something planned for 2.7, but that was waaa
35 matches
Mail list logo
