headers
Joe Ciccone | 3 Jan 2010 17:06
Picon

Re: CLFS (SVN-20091027-PowerPC) - 5.12 GCC - Symlink problem

On 12/30/2009 03:19 PM, Dok Sander wrote:
> Hi,
>
> I'm on Chapter 5.12 (Cross GCC-4.4.1 - Static) of CLFS - SVN-20091027-PowerPC and because of deviating
from the guide run into this problem:
>
> I don't want symlink $CLFS/{tools,cross-tools} to / because I'm going to have multiple
cross-compilation environments on the same system. So, without the symlinks I change the paths
accordingly. I cant't get GCC to build however. This is the error the make fails to:
>
> gcc/include-fixed/limits.h:122:61: error: no include path in which to search for limits.h
> make[1]: *** [_fixunssfsi.o] Error 1
>   
> I have changed the paths in gcc-4.4.1-specs-1.patch, of CROSS_SYSTEM_HEADER_DIR in gcc/Makefile.in
and touched include/limits.h in my tools-dir. Also, the options passed to configure are correct. I have
double-checked and tried the compilation over and over again so can anyone think of anything that I'm
missing ignoring the possibility of typos?
>   
FYI, if you change /tools to /mnt/clfs/tools, after you boot into the
final system, you would have to actually put tools in
/mnt/clfs/mnt/clfs/tools after you chroot. The reason for the symlinks
is so that /tools keeps the same relative paths inside and outside of
the chroot.

I don't know exactly what your setup is, but you have 2 options really,
attempt to use sysroot to move /tools into your target only. I forget
exactly why the book doesn't have this, there is a reason, I think there
were problems building from OpenSolaris.

The easiest option, during your build, along the same lines, just rename
(Continue reading)

Permalink | Reply | 0 comments |
headers
Guillaume FORTAINE | 5 Jan 2010 16:25

Intel Rapid Boot Toolkit

Misters,

Happy New Year to you,

Let me introduce myself : Guillaume FORTAINE, Engineer in Computer
Science. I am currently working on a custom firmware.

As the industry is moving towards UEFI, I have chosen the
Intel Rapid Boot Toolkit as my BIOS Framework.

I would greatly appreciate to have your comments and more informations
about this Toolkit, if possible, please.

a) Presentation : Cluster Software and Technologies [1]

b) User Guide : Intel(R) Rapid Boot Toolkit User Guide [2]

c) Examples : Usage Model:Examples [3]

d) Prototype : Enabling the Autonomic DataCenter with a SmartBare-Metal
Server Platform [4]

I look forward to your answer,

Best Regards,

Guillaume FORTAINE

[1]
http://www.csm.ornl.gov/oscar07/proceedings/siadal-keynote-oscar07-slides.pdf
(Continue reading)

Permalink | Reply | 0 comments |
headers
John Bolton | 5 Jan 2010 18:01
Picon
Favicon

Clock problem GMT vs. local

I have configured the system so that the hardware clock uses local time by setting UTC=0 in the file /etc/sysconfig/clock. Unfortunately, during boot the system halts with a message stating that the file system cannot be mounted because the superblock last write time is in the future. It shows the last write time as (for example) 10:00 PM and the current time as 2:00 PM (I’m in PST so there is an 8 hour offset).

 

I then boot the system with a LFS live CD, verify the time is set to the local time using the date and hwclock commands, and force a check on all partitions. FSCK reports the errors as having been fixed. I then reboot, remove LFS live CD, and run into the same problem.

 

The only way to get around the problem is to boot with the LFS live CD, set both the local time and hardware clocks to a date and time a couple of days ago, and then force a disk check using FSCK on all partitions.

 

I checked the IRC channel and at least one other person is running into the same problem.

 

Any suggestions?

 

Thanks,

 

John Bolton

 

_______________________________________________
Clfs-support mailing list
Clfs-support <at> lists.cross-lfs.org
http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org
Permalink | Reply | 4 comments |
headers
appzer0 | 6 Jan 2010 08:00
Picon
Favicon

CLFS multilib (SVN20100103): cannot neither chroot nor boot Ch. 6

Hi,

I cannot chroot on my Slackware64 13.0 vanilla system:

# chroot "${CLFS}" /tools/bin/env -i \
HOME=/root TERM="${TERM}" PS1='CHROOT_CLFS\u:\w\$ ' \
PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \
/tools/bin/bash --login +h
chroot: cannot run command `/tools/bin/env': No such file or directory

though my CPU is a AMD Phenom X2 (64 bits). Kernel has IA32 emulation
compiled in.
I cross-compile for x86_64 target with multilib caabilities. Cross-tools
compiled fine.

Slackware64 has a multilib-capable design but is not able to compile
multilib (gcc and glibc are pure 64-bit), so it has a lib64 _by
default_. My guess is that other 64-bit distros may have their default
libpath in /lib instead of /lib64, for example. So what should I do to be able to chroot?

As a matter of fact, I wanted to boot following the Boot method but what I was expecting happened: no init found.

I strictly followed the clfs multilib book several times now - excepting software versions - and I realize
I'm just stuck each time at the Boot/Chroot step.

Below are the values I'm using and system host values while at the end of chap. 6. TIA

-------------------------
# env
AS=x86_64-frenchslack-linux-gnu-as
AR=x86_64-frenchslack-linux-gnu-ar
CLFS_TARGET32=i686-frenchslack-linux-gnu
CLFS_HOST=x86_64-cross-linux-gnu
TERM=xterm
CLFS_TARGET=x86_64-frenchslack-linux-gnu
LC_ALL=POSIX
BUILD64=-m64
CLFS=/frenchslack-prod
BUILD32=-m32
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/usr/sbin:/bin:/usr/bin
LD=x86_64-frenchslack-linux-gnu-ld
PWD=/frenchslack-prod/sources/util-linux-ng-2.16.2
STRIP=x86_64-frenchslack-linux-gnu-strip
PS1=CLFS:\u:\w\$
CXX=x86_64-frenchslack-linux-gnu-g++
HOME=/root
SHLVL=2
RANLIB=x86_64-frenchslack-linux-gnu-ranlib
CC=x86_64-frenchslack-linux-gnu-gcc
_=/bin/env

# uname -a
Linux Poopy 2.6.29.6 #2 SMP Mon Dec 7 14:40:49 CST 2009 x86_64 AMD
Phenom(tm) II X2 550 Processor AuthenticAMD GNU/Linux

# gcc -v
Reading specs from /usr/lib64/gcc/x86_64-slackware-linux/4.3.3/specs
Target: x86_64-slackware-linux
Configured with: ../gcc-4.3.3/configure --prefix=/usr
--libdir=/usr/lib64 --enable-shared --enable-bootstrap
--enable-languages=ada,c,c++,fortran,java,objc --enable-threads=posix
--enable-checking=release --with-system-zlib
--disable-libunwind-exceptions --enable-__cxa_atexit --enable-libssp
--with-gnu-ld --verbose --disable-multilib
--target=x86_64-slackware-linux --build=x86_64-slackware-linux
--host=x86_64-slackware-linux
Thread model: posix
gcc version 4.3.3 (GCC)

# /tools/bin/gcc -v
/tools/bin/gcc: /lib64/libc.so.6: version `GLIBC_2.11' not found
(required by /tools/bin/gcc)

$ readelf -l /frenchslack-prod/tools/lib/libc-2.11.90.so | grep interpreter
       [Requesting program interpreter: /tools/lib/ld-linux.so.2]
$ readelf -l /frenchslack-prod/tools/lib64/libc-2.11.90.so | grep interpreter
       [Requesting program interpreter: /tools/lib64/ld-linux-x86-64.so.2]
$ readelf -l /frenchslack-prod/tools/bin/bash | grep interpreter
       [Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]
-------------------

Any clue will be greatly appreciated.

appzer0
Permalink | Reply | 4 comments |
headers
Chris Staub | 6 Jan 2010 08:15

Re: CLFS multilib (SVN20100103): cannot neither chroot nor boot Ch. 6

On 01/06/2010 02:00 AM, appzer0 wrote:
> Hi,
>
> I cannot chroot on my Slackware64 13.0 vanilla system:
>
> # chroot "${CLFS}" /tools/bin/env -i \
> HOME=/root TERM="${TERM}" PS1='CHROOT_CLFS\u:\w\$ ' \
> PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \
> /tools/bin/bash --login +h
> chroot: cannot run command `/tools/bin/env': No such file or directory

This usually indicates /tools/bin/env is linked incorrectly.

> though my CPU is a AMD Phenom X2 (64 bits). Kernel has IA32 emulation
> compiled in.
> I cross-compile for x86_64 target with multilib caabilities. Cross-tools
> compiled fine.
>
> Slackware64 has a multilib-capable design but is not able to compile
> multilib (gcc and glibc are pure 64-bit), so it has a lib64 _by
> default_. My guess is that other 64-bit distros may have their default
> libpath in /lib instead of /lib64, for example. So what should I do to
> be able to chroot?
>
> As a matter of fact, I wanted to boot following the Boot method but what
> I was expecting happened: no init found.

I'd bet this is due to the same problems mentioned below...

> I strictly followed the clfs multilib book several times now - excepting
> software versions - and I realize I'm just stuck each time at the
> Boot/Chroot step.

No you didn't, as your variables below clearly indicate. For example, 
you apparently added "frenchslack" to the CLFS_TARGET vars...and a 
number of other changes.
>
> Below are the values I'm using and system host values while at the end
> of chap. 6. TIA
>
> -------------------------
> # env
> AS=x86_64-frenchslack-linux-gnu-as
> AR=x86_64-frenchslack-linux-gnu-ar
> CLFS_TARGET32=i686-frenchslack-linux-gnu
> CLFS_HOST=x86_64-cross-linux-gnu
> TERM=xterm
> CLFS_TARGET=x86_64-frenchslack-linux-gnu
> LC_ALL=POSIX
> BUILD64=-m64
> CLFS=/frenchslack-prod
> BUILD32=-m32
> PATH=/usr/local/sbin:/usr/local/bin:/sbin:/usr/sbin:/bin:/usr/bin

If this is the env for the clfs user (as the indicated by the existence 
of AS, LD, CC, etc...vars), the PATH is incorrect, main problem being 
that /cross-tools/bin isn't anywhere to be found, which is likely the 
main source of all your problems.

> LD=x86_64-frenchslack-linux-gnu-ld
> PWD=/frenchslack-prod/sources/util-linux-ng-2.16.2
> STRIP=x86_64-frenchslack-linux-gnu-strip
> PS1=CLFS:\u:\w\$
> CXX=x86_64-frenchslack-linux-gnu-g++
> HOME=/root

Never mind the previous comment about clfs user, as apparently you 
aren't using it, despite your previous claim to be following the book.

> SHLVL=2
> RANLIB=x86_64-frenchslack-linux-gnu-ranlib
> CC=x86_64-frenchslack-linux-gnu-gcc
> _=/bin/env
>
> $ readelf -l /frenchslack-prod/tools/bin/bash | grep interpreter
> [Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]
> -------------------
>
There's one problem right there - Bash in /tools is linked to the host, 
and I bet so is everything else (such as Coreutils, which would explain 
the /tools/bin/env issue above). My guess your messing with various env. 
vars (and/or not bothering to set the right PATH) has messed things 
up...either that or it is due to even more deviations from the book that 
you haven't mentioned. All I can suggest is to rm -rf /{cross-,}tools/*, 
go back to the beginning and *actually* follow the book's 
instructions...all of them...
Permalink | Reply | 3 comments |
headers
appzer0 | 6 Jan 2010 08:42
Picon
Favicon

Re: CLFS multilib (SVN20100103): cannot neither chroot nor boot Ch. 6

Hi,

Thanks for your reply.
>
>> I strictly followed the clfs multilib book several times now - excepting
>> software versions - and I realize I'm just stuck each time at the
>> Boot/Chroot step.
>
> No you didn't, as your variables below clearly indicate. For example, 
> you apparently added "frenchslack" to the CLFS_TARGET vars...and a 
> number of other changes.
My bad. It seems that I pasted env variables for wrong sessions :( 
Anyway you are right concerning the "vendor" strings, sorry it's not 
that strict following indeed (and sorry for my english).
>
> There's one problem right there - Bash in /tools is linked to the 
> host, and I bet so is everything else (such as Coreutils, which would 
> explain the /tools/bin/env issue above). My guess your messing with 
> various env. vars (and/or not bothering to set the right PATH) has 
> messed things up...either that or it is due to even more deviations 
> from the book that you haven't mentioned. All I can suggest is to rm 
> -rf /{cross-,}tools/*, go back to the beginning and *actually* follow 
> the book's instructions...all of them...
You're perfectly right. cross-tools are compiled via a Bash script I 
wrote and I probably I mixed variables from that script along with 
variables from my env, so it may be have messed the PATH up.

Thank you very much for your time and directions. I'll drop a line if 
everything went OK rebuilding from the beginning. Have a nice day.

appzer0
Permalink | Reply | 2 comments |
headers
Chris Staub | 6 Jan 2010 08:53

Re: CLFS multilib (SVN20100103): cannot neither chroot nor boot Ch. 6

On 01/06/2010 02:42 AM, appzer0 wrote:
> My bad. It seems that I pasted env variables for wrong sessions :(
> Anyway you are right concerning the "vendor" strings, sorry it's not
> that strict following indeed (and sorry for my english).
>>
>> There's one problem right there - Bash in /tools is linked to the
>> host, and I bet so is everything else (such as Coreutils, which would
>> explain the /tools/bin/env issue above). My guess your messing with
>> various env. vars (and/or not bothering to set the right PATH) has
>> messed things up...either that or it is due to even more deviations
>> from the book that you haven't mentioned. All I can suggest is to rm
>> -rf /{cross-,}tools/*, go back to the beginning and *actually* follow
>> the book's instructions...all of them...
> You're perfectly right. cross-tools are compiled via a Bash script I
> wrote and I probably I mixed variables from that script along with
> variables from my env, so it may be have messed the PATH up.

Ah ok, sorry I was harsh - I was making false assumptions. Hopefully 
it'll work this time.

> Thank you very much for your time and directions. I'll drop a line if
> everything went OK rebuilding from the beginning. Have a nice day.
>
> appzer0
Permalink | Reply | 1 comment |
headers
appzer0 | 6 Jan 2010 12:22
Picon
Favicon

Re: CLFS multilib (SVN20100103): cannot neither chroot nor boot Ch. 6

On 06/01/2010 08:53, Chris Staub wrote:
>
>> Thank you very much for your time and directions. I'll drop a line if
>> everything went OK rebuilding from the beginning. Have a nice day.
>>
>> appzer0
>
Everything went just OK.

-----------
CLFS:clfs:/frenchslack-prod/sources$ readelf -l /tools/bin/bash | grep 
interpreter
       [Requesting program interpreter: /tools/lib64/ld-linux-x86-64.so.2]
-----------

The problem was actually in $PATH. I executed my big build script in 
clfs environment and everything compiles just fine. I can chroot now. 
Showtime! :)

Thanks again.

appzer0
Permalink | Reply | 0 comments |
headers
Tom Armistead | 12 Jan 2010 04:12
Picon

packages: parted-1.9.0.tar.bz2 should be parted-1.9.0.gz


Hello,

     Just reporting a minor nit...

     I pulled a view of the current CLFS book (to build a PowerPC target) and could not find parted-1.9.0.tar.bz2.   The book should reference parted-1.9.0.tar.gz instead.

    
 
David
_______________________________________________
Clfs-support mailing list
Clfs-support <at> lists.cross-lfs.org
http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org
Permalink | Reply | 0 comments |
headers
jaca | 12 Jan 2010 12:39
Picon
Favicon

Silo-1.4.14

Hello Clfs-support,

  I've found the following problem during system build procedure
following: Version SVN-20100103-Sparc64-Multilib

1. The silo package pointed by:
http://cross-lfs.org/files/packages/svn//silo-1.4.14.tar.bz2 is not
available for download

2. The GIT version obtained from silo.org does not compile becouse of
errors.

I there some alternative location for silo sources that are available
and compiles correctly.

I may attach the errors if needed.

Best regards
Jacek

--

-- 
Best regards,
 jaca                          mailto:jherold <at> interia.pl

----------------------------------------------------------------------
Co Ci sie dzisiaj snilo? Czy wiesz, co oznacza Twoj sen?
Sprawdz w senniku >> http://link.interia.pl/f2532
Permalink | Reply | 2 comments |

Gmane