Hello
I'm about to create LFS system from cross-lfs for sparc64 multilib.
The base system works well. But i think some hints for how to make
multilib lfs from cross-compiled system would be great thing. Are
there any?
Jacek Herold
--
Paul Lewis wrote:
Hi,
I'm using LFS 6.1, and have come across a problem when I try to compile TCL
(version 8.4.9, as recommended by the book).
...
\".so\" ./../compat/strstr.c
./../compat/strstr.c: In function 'strstr':
./../compat/strstr.c:67: error: 'NULL' undeclared (first use in this
fun
On 10/29/05, Paul Lewis <[EMAIL PROTECTED]> wrote:
> I'm using LFS 6.1, and have come across a problem when I try to compile TCL
> (version 8.4.9, as recommended by the book). I have been following the
> instructions in the book exactly, with no deviations. I have booted from the
> LiveCD to create
Jasper Leemans wrote:
Should I be worried or just ignore the error, sda is it scsi or sata?
...anyway I don't have any of those, but I just don't like errors :-D
You can safely ignore the error. It's actually caused by us moving
coreutils' `test' binary from /usr/bin to /bin. The udev test
Hi,
I'm using LFS 6.1, and have come across a problem when I try to compile TCL
(version 8.4.9, as recommended by the book). I have been following the
instructions in the book exactly, with no deviations. I have booted from the
LiveCD to create my own LFS environment. The only anomaly might be tha
On Sat, 29 Oct 2005, Andreas ?berg wrote:
As far as I can telle there is no problem with the linking... but you
are right perheps someone else can spot something?
ldd /sbin/init
libintl.so.3 => /lib/libintl.so.3 (0xb7fec000)
libc.so.0 => /lib/libc.so.0 (0xb7f55000)
ld-uC
Ken Moffat skrev:
> On Sat, 29 Oct 2005, Andreas Åberg wrote:
>
1. Yes they exist.
2. Yes i can run /bin/bash, and everything else to.
>>>
>>> Odd. In that case, the primary suspect has to be a linking problem.
>>> I'm no expert on how programs linked with uClibc ought to look,
On Sat, 29 Oct 2005, Andreas Åberg wrote:
1. Yes they exist.
2. Yes i can run /bin/bash, and everything else to.
Odd. In that case, the primary suspect has to be a linking problem.
I'm no expert on how programs linked with uClibc ought to look, but
what does 'ldd /bin/bash' show when you ar
