On Sat, 2006-01-28 at 14:36 -0800, Dan Nicholson wrote:
> On 1/27/06, Jeremy Huntwork <[EMAIL PROTECTED]> wrote:
> >
> > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19353
> >
> > Our longtime Toolchain Maintainer, Ryan Oliver, still prefers to use
> > this method.
>
> Um, the decision might be mad
Chris Staub wrote:
I reinstalled ncurses over itself successfully. I'm not sure what you
want me to "verify" - should I have seen an error?
I wanted you to verify that libncursesw.so.5.5 is in /lib and has the
right size (several hundred kilobytes), that there is a symlink
/lib/libncursesw.s
On Sat, 2006-01-28 at 08:32 -0800, Dan Nicholson wrote:
> On 1/27/06, Greg Schafer <[EMAIL PROTECTED]> wrote:
> > Ever looked at a build log of GCC itself? Guess what? -B.
>
> /tools/src/build/gcc-build/gcc/xgcc -B/tools/src/build/gcc-build/gcc/
> -B/usr/i686-pc-linux-gnu/bin/ -B/usr/i686-pc-linux
Alexander E. Patrakov wrote:
Chris Staub wrote:
The Chapter 6 ncurses instructions in the LFS dev book have this
construction:
for lib in curses ncurses form panel menu ; do \
rm -vf /usr/lib/lib${lib}.so ; \
echo "INPUT(-l${lib}w)" >/usr/lib/lib${lib}.so ; \
ln -sfv l
Chris Staub wrote:
The Chapter 6 ncurses instructions in the LFS dev book have this
construction:
for lib in curses ncurses form panel menu ; do \
rm -vf /usr/lib/lib${lib}.so ; \
echo "INPUT(-l${lib}w)" >/usr/lib/lib${lib}.so ; \
ln -sfv lib${lib}w.a /usr/lib/lib${lib}
Chris Staub wrote:
Any particular reason why readline can't be told to link directly
against the ncursesw libs, as opposed to the "ncurses" libs which simply
point to ncursesw?
Oh, nevermind, it actually does find the ncursesw libs (was just looking
at the "make" line in the book and didn't b
The Chapter 6 ncurses instructions in the LFS dev book have this
construction:
for lib in curses ncurses form panel menu ; do \
rm -vf /usr/lib/lib${lib}.so ; \
echo "INPUT(-l${lib}w)" >/usr/lib/lib${lib}.so ; \
ln -sfv lib${lib}w.a /usr/lib/lib${lib}.a ; \
done
That "rm
Any particular reason why readline can't be told to link directly
against the ncursesw libs, as opposed to the "ncurses" libs which simply
point to ncursesw?
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information p
On Sat, 2006-01-28 at 13:07 +1100, Greg Schafer wrote:
> Jeremy Huntwork wrote:
>
> > Isn't using -B to find libraries an abuse as well?
>
> Huh? Using a documented switch for a documented purpose?
> RTFM :-)
>
The purpose of the -B flag is to override GCC_EXEC_PREFIX, the path the
gcc driver u
The Chapter 6 GCC instructions suggest running the sanity check in the
"Readjusting the toolchain" section after reinstalling GCC. However, if
you just follow the instructions as they are, it will "fail". Before you
install GCC into /usr, the check for "/usr/lib/crt.*" will work, but
after you
On 1/27/06, Jeremy Huntwork <[EMAIL PROTECTED]> wrote:
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19353
>
> Our longtime Toolchain Maintainer, Ryan Oliver, still prefers to use
> this method.
Um, the decision might be made for us:
http://gcc.gnu.org/ml/gcc-patches/2005-01/msg00507.html
Spec
[EMAIL PROTECTED] wrote:
Lionel Lagarde wrote:
Hi all.
I have just bought a new pc and I want to install Linux there by
following the lfs book.
Someone has already managed to compile lfs on a amd64 system ?
If so, from what os ?
I'm using a x86_64 fedora core 4 and I ca
On 1/27/06, Greg Schafer <[EMAIL PROTECTED]> wrote:
> Ever looked at a build log of GCC itself? Guess what? -B.
/tools/src/build/gcc-build/gcc/xgcc -B/tools/src/build/gcc-build/gcc/
-B/usr/i686-pc-linux-gnu/bin/ -B/usr/i686-pc-linux-gnu/lib/ ...
Seems gcc thinks it's OK to search for libraries wi
On 1/27/06, Ken Moffat <[EMAIL PROTECTED]> wrote:
>
> > I haven't been running the testsuites, but I'm doing that now to make
> > sure that their dependencies are met.
>
> Good man! As has already been seen with perl and db, and I think a
> locale for coreutils tests, ICA analysis is different f
Matthew Burgess wrote:
> In the interests of getting this issue off your/our plates I'd say we
> choose whatever method is most suited to LFS as it is now. That is,
> whichever works on x86 native compilations and is officially
> supported/documented upstream. Yes, I understand people's desires t
Greg Schafer wrote:
IMHO multilib is quite complicated. I cannot say anything authoritative
about it because I personally haven't had a need for it and therefore
haven't researched or tested it. That'll change if someone sends me an
AMD64 box :-)
Get a free (but slow) x86_64 box either from h
Jeremy Huntwork wrote:
Obviously '-B' works for you, and obviously, Ryan's methods work for
him. Is there a 'best for LFS' in all of that?
In the interests of getting this issue off your/our plates I'd say we
choose whatever method is most suited to LFS as it is now. That is,
whichever work
17 matches
Mail list logo
