On Wed, Jun 06, 2007 at 08:10:51AM -0700, David Whitney wrote:
> Ken,
>
> Thank you for your reply. This is my first attempt at building CLFS. I am
> running an "ancient" Red Hat Linux OS, which I have no control to make
> changes because it is used to build the software running in medical
> devices. Here is some info:
>
> $ uname -a
> Linux englinux 2.4.21-15.EL #1 SMP Thu Apr 22 00:09:47 EDT 2004 x86_64
> x86_64 x86_64 GNU/Linux
>
> $ which gcc
> /usr/bin/gcc
>
> $ gcc --version
> gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-54)
>
I have no experience of RHEL, nor of trying to cross-compile from a
2.4 kernel. An old RHEL is unlikely to cause problems in itself,
but a 2.4 kernel could alter what glibc decides to build.
>
> As for the CLFS instruction guide, I have followed all of the instructions
> to the letter except one, and that is the section concerning creating a
> separate partition for the CLFS build area (I already have a separate
> area). One other deviation, which is actually an addition, it the
> installation of a newer version of Make. My system has version
> 3.79.1installed. This version cannot be used for uClibc. Therefore,
> I downloaded
> and installed Make 3.81 into the ${CLFS}/cross-tool/bin directory. I
> configured Make using a similar prefix, host, and target as for other
> packages called out in the CLFS book.
>
> Btw, here are my environment settings:
>
> $ env
> CLFS_HOST=x86_64-cross-linux-gnu
> TERM=xterm
> CLFS_TARGET=i686-pc-linux-gnu
> LC_ALL=POSIX
> CLFS=/nonraid-storage/clfs
> PATH=/nonraid-storage/clfs/cross-tools/bin:/bin:/usr/bin
Building without /cross-tools (and /tools) symlinks is untested and
could, perhaps, cause problems. If you are able to create the
symlinks, use them in the PATH.
> BUILD=-m32
I'm on my server at the moment (console, no nice X desktop) so I
can't easily check at the moment, but do we really call it $BUILD
rather than $BUILD32 ?
> PWD=/data/home/clfs
> PS1=\u:\w\$
> SHLVL=1
> HOME=/home/clfs
> _=/bin/env
>
> Anyhow what I can do is start all over again; this time I will capture the
> 1000's of lines of output generated by making each package. Maybe there is
> a relevant warning/error message that I may have missed. If there is
> though, I will be surprised. Like I said earlier, everything seemed to
> build just fine up until I came to gcc.
But really, you are still at a very early stage in the build. The
first time, it is a lot of work but in terms of compiling you have
hardly begun. For logging, don't forget the error messages (e.g.
make ... 2>&1 | tee foo.log ) and consider noting what gets
installed by each package - I touch a file before the install then
do something based on 'find -newer' which doesn't catch everything
(particularly headers with an old date) and needs some pruning for
unrelated changes, but is sometimes helpful.
>
> By the way, can you please confirm if I built Make correctly? I configured
> it as follows:
>
> $ cd make-3.81
> $ ./configure --prefix=${CLFS}/cross-tool --target=${CLFS_TARGET}
> --host=${CLFS_HOST}
>
> Perhaps it was not necessary for me to specify the target?
>
You seem to be cross-compiling make. When we do the initial
cross-compile, we only build a toolchain. If you need a newer
version of make, or anything else, to complete the cross-compiled
toolchain then it is fine to put it into /cross-tools ('plural' -
typo in your configure ?) but as a native tool to run on the host.
> Dave
>
> On 6/6/07, Ken Moffat <[EMAIL PROTECTED]> wrote:
> >
And for the future, please don't top post. Trim what you are
replying to, and put your replies underneath the relevant part.
Ken (hmm, I need to fix the keymap on my server so I can get the
letters and dead accents I'm accustomed to with AltGr - thanks for
reminding me).
--
das eine Mal als Tragödie, das andere Mal als Farce
_______________________________________________
Clfs-support mailing list
[email protected]
http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
