headers
bv | 4 Mar 2011 16:45

ppl and cloog-ppl errors amd64

Greetings,

I am attempting to build  clfs current development   (amd64 64-bit).  I am at 
the  toolchain section and reached   the building of ppl-0.10.2.

The libraries built and installed then it reported  an error  for a binary.  
Being unsure if a binary was needed I  proceeded   with cloog-ppl-0.15.10  
only to run into more errors,  The error trails are shown below:-

 ppl-0.10.2  installation

test -z "/cross-tools/bin" || /bin/mkdir -p "/cross-tools/bin"
/bin/mkdir: cannot create directory `/cross-tools/bin': File exists
make[3]: *** [install-binPROGRAMS] Error 1
make[3]: Leaving directory `/mnt/clfs/sources-28810/ppl-0.10.2/src'
make[2]: *** [install-am] Error 2
make[2]: Leaving directory `/mnt/clfs/sources-28810/ppl-0.10.2/src'
make[1]: *** [install] Error 2
make[1]: Leaving directory `/mnt/clfs/sources-28810/ppl-0.10.2/src'
make: *** [install-recursive] Error 1

 cloog-ppl-0.15.10  compilation

It appears that your system is OK to start CLooG compilation. You need
now to type "make". After compilation, you should check CLooG by typing
"make check". If no problem occur, you can type "make uninstall" if
you are upgrading an old version. Lastly type "make install" to install
CLooG on your system (log as root if necessary).

########################################
(Continue reading)

Permalink | Reply | 1 comment |
headers
bv | 5 Mar 2011 22:52

Re: ppl and cloog-ppl errors amd64

On Friday 04 March 2011 15:45:00 bv wrote:

>  cloog-ppl-0.15.10  compilation
> 
> It appears that your system is OK to start CLooG compilation. You need
> now to type "make". After compilation, you should check CLooG by typing
> "make check". If no problem occur, you can type "make uninstall" if
> you are upgrading an old version. Lastly type "make install" to install
> CLooG on your system (log as root if necessary).
> 
> ########################################
>  running  make
> ########################################
> 
> make: *** No rule to make target `m4/libtool.m4', needed by `Makefile.in'.

found the error
the   the bin directory needs to be   created manually prior to  ncurses 
install.
Permalink | Reply | 0 comments |
headers
bv | 5 Mar 2011 22:50

patch-2.6.1 build failure toolchain amd64

Greetings,

I am having a go at the current SVN CLFS (amd64- pure 64 bit).  I reached as 
far as patch-2.6.1   with toolchain building then the following happens:-

x86_64-unknown-linux-gnu-gcc -m64 -std=gnu99 -o src/patch -g -O2  
gl/lib/argmatch.o gl/lib/backupfile.o gl/lib/basename.o gl/lib/dirname.o 
gl/lib/stripslash.o gl/lib/exitfail.o gl/lib/strnlen.o gl/lib/hash.o 
gl/lib/quote.o gl/lib/quotearg.o gl/lib/safe-write.o gl/lib/xmalloc.o 
gl/lib/xstrndup.o gl/lib/error.o gl/lib/full-write.o src/merge.o src/inp.o 
src/maketime.o src/partime.o src/patch.o src/pch.o src/quotesys.o src/util.o 
src/version.o 
x86_64-unknown-linux-gnu-gcc: gl/lib/strnlen.o: No such file or directory
make: *** [src/patch] Error 1

help would be appreciated

sincerely
bv
Permalink | Reply | 0 comments |
headers
code monkey | 20 Mar 2011 14:19
Picon

How to use jhalfs to build CLFS.

Hello

Maybe this is something that you guys already know...  If so, forgive me stating
the obvious...
     
You can use jhalfs to build CLFS and it can be a big help.   However, it does not work
(currently anyway) 'out of the box'.  There are a few extra steps that
you have to do.

First, jhalfs is not able to download the CLFS book for you.   You have to
do that manually and then point jhalfs at your downloaded copy.

Second, there are a couple of patches to jhalfs that you need to download and
apply.   I submitted these patches to the jhalfs mailing list a while back but
they haven't been added to it yet.   So, you have to get and apply them manually.

This is what you have to do.



1) ======= Get a local working copy of the CLFS book.


# Get the CLFS git
git clone git://git.cross-lfs.org/cross-lfs.git
cd cross-lfs

# If you want to build the 1.1.0 release rather than the current work in
# progress version do the next two commands.  Otherwise, skip it.
git branch branchname clfs-1.1.0
git checkout clfs-1.1.0

# 'BOOK' is where you will need to point jhalfs.
cd BOOK
pwd


2) ======= Get the jhalfs source and patches.

Get the current jhalfs code (or instead download the jhalfs 2.3.2 tarball....)

svn co svn://svn.linuxfromscratch.org/ALFS/jhalfs/trunk jhalfs-trunk
cd jhalfs-trunk   (or jhalfs-2.3.2 if using 2.3.2 release)

2a) ==== The needed jhalfs CLFS patches can be found in this email thread:

http://linuxfromscratch.org/pipermail/alfs-discuss/2010-September/thread.html

    (Find the two emails regarding fixes for building CLFS with jhalfs and
     download the attached patches).

3) =================== Apply the jhalfs patches.

cat jhpatch1.txt |patch -Np1
cat jhpatch2.txt |patch -Np1



4) =================== It's ready to go.

Make your clfs dir and start up jhalfs.   In the jhalfs menu, you will need to
select "Working Copy" for the CLFS book location and specify the directory (from
above) where you have stored the CLFS book.

mkdir /mnt/clfs
make


jhalfs doesn't build CLFS as smoothly as it builds LFS.   You may have to nurse
it through a few spots.   But even so, it still reduces the time needed to
do a CLFS build.

_______________________________________________
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
Fred Liu | 25 Mar 2011 14:52

is it possible to build target OS in kernel 2.4 and glibc 2.3 in CLFS?

Hi,

 

I want build latest GNU tools running in  CentOS3.9(kernel 2.4,glibc 2.3) via CLFS.

Is it doable?

 

Thanks.

 

Fred

_______________________________________________
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 | 3 comments |
headers
Andrew Bradford | 25 Mar 2011 23:24
Picon

Re: is it possible to build target OS in kernel 2.4 and glibc 2.3 in CLFS?

> I want build latest GNU tools running in  CentOS3.9(kernel 2.4,glibc 2.3)
> via CLFS.
>
> Is it doable?

I'm assuming you want to build a regular CLFS system and not the
embedded or sysroot versions.
Chroot'ing will almost certainly give you trouble going from a 2.4 to
2.6 kernel.  I'd avoid that.  Use the boot method instead.

I don't know the answer to your question (I'd venture the answer is
"no"), but I'd recommend starting with the 1.1.0 book and see how far
you can get.  If you have a reasonably modern machine, it shouldn't
take too long (time wise) to get a working cross compiler or run into
issues.

Can you run the version-check.sh script and provide the output?

If there's any way you could use a slightly more recent Linux
distribution, it'll probably provide a better experience.  CentOS3 is
about 8 years old.  Any specific reason you're still using it?

-Andrew
Permalink | Reply | 2 comments |
headers
code monkey | 26 Mar 2011 14:46
Picon

Re: is it possible to build target OS in kernel 2.4 and glibc 2.3 in CLFS?




> I want build latest GNU tools running in  CentOS3.9(kernel 2.4,glibc 2.3)
> via CLFS.
>
> Is it doable?


Like Andrew said...   It's very unlikely that you will be able to chroot from a kernel 2.4 OS to do the CLFS build and the chroot method is not (likely) an option for your build.

Give it a try..   If you are able to successfully get to the end of the build of the cross compile tools, you have pretty good odds of getting it through the rest of the build.    And it won't take you too long to try it that far.


_______________________________________________
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 | 1 comment |
headers
Fred Liu | 28 Mar 2011 13:48

Re: is it possible to build target OS in kernel 2.4 and glibc 2.3 in CLFS?

Andrew and Code Monkey,

 

Thank you very much.

 

The reason why we still stick to CentOS3.9 is the some legacy software running on it are still needed by our business.

 

And just like what you said, I tried and got no luck today.

 

I also found a HINT -- http://www.linuxfromscratch.org/hints/downloads/files/kernel-2.4.txt.

But the passage is sort of old, and author did not mention the actual gcc,g libc, and linux kernel version.

I cannot reply it either.

 

The idea is simple ¨C try to running latest gnu binary in linux 2.4. The host OS could be any latest linux distro.

 

But it seems waste of time to do it.

 

Many thanks.

 

Fred

 

From: clfs-support-bounces <at> lists.cross-lfs.org [mailto:clfs-support-bounces <at> lists.cross-lfs.org] On Behalf Of code monkey
Sent: ÐÇÆÚÁù, ÈýÔÂ 26, 2011 21:46
To: CLFS Support
Subject: Re: [Clfs-support] is it possible to build target OS in kernel 2.4 and glibc 2.3 in CLFS?

 

 

 

> I want build latest GNU tools running in  CentOS3.9(kernel 2.4,glibc 2.3)
> via CLFS.
>
> Is it doable?


Like Andrew said...   It's very unlikely that you will be able to chroot from a kernel 2.4 OS to do the CLFS build and the chroot method is not (likely) an option for your build.

Give it a try..   If you are able to successfully get to the end of the build of the cross compile tools, you have pretty good odds of getting it through the rest of the build.    And it won't take you too long to try it that far.

_______________________________________________
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
Randolph D Dach | 28 Mar 2011 21:03

xorg 7 script problem


Hi 

I am trying to rebuild CFLS and I have run into a problem with the script for helping build the xorg7 proto 
section of the CBLFS

when I run the script 
 top=$PWD
 cat ../Proto-20101205.wget | while read package; do   packagedir=$(sed -e "s/\.tar\.bz2//" <<<
$package);    cd $top || break; 
grep ^$packagedir$ done && continue;  
 echo $package && 
echo $packagedir && 
tar xvf $package; 
done

I get the output of  

grep: done: No such file or directory
applewmproto-1.4.1.tar.bz2
applewmproto-1.4.1
tar: applewmproto-1.4.1.tar.bz2\r: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now

etc for all the rest of the tar.bz2 files

I copied this directly from the website??? and of course only added the echo parts to see if the package and
packagedir were correctly shown  

why does tar put in the \r at the end of the package name????

tks
--

-- 
Randolph D Dach <rdach <at> telus.net>
Permalink | Reply | 10 comments |
headers
Grail Dane | 29 Mar 2011 02:45
Picon
Favicon

Re: xorg 7 script problem

Well the grep error is due to you not having the complete script, ie the following line:

echo "$packagedir" >> done || break

Is what populates the done file, bad name in my opinion as it is confusing, however, have you also performed the prior
step of:

wget -B http://xorg.freedesktop.org/releases/individual/proto/ -i ../Proto-20101205.wget

As this will download the files you require which seems to be the complaint about no file?
The \r may be a remnant if you performed any of this under Windows?

Let us know how you go?

cheers
grail

> Date: Mon, 28 Mar 2011 13:03:38 -0600
> From: rdach <at> telus.net
> To: clfs-support <at> lists.cross-lfs.org
> Subject: [Clfs-support] xorg 7 script problem
>
>
> Hi
>
> I am trying to rebuild CFLS and I have run into a problem with the script for helping build the xorg7 proto section of the CBLFS
>
> when I run the script
> top=$PWD
> cat ../Proto-20101205.wget | while read package; do packagedir=$(sed -e "s/\.tar\.bz2//" <<< $package); cd $top || break;
> grep ^$packagedir$ done && continue;
> echo $package &&
> echo $packagedir &&
> tar xvf $package;
> done
>
> I get the output of
>
> grep: done: No such file or directory
> applewmproto-1.4.1.tar.bz2
> applewmproto-1.4.1
> tar: applewmproto-1.4.1.tar.bz2\r: Cannot open: No such file or directory
> tar: Error is not recoverable: exiting now
>
> etc for all the rest of the tar.bz2 files
>
> I copied this directly from the website??? and of course only added the echo parts to see if the package and packagedir were correctly shown
>
> why does tar put in the \r at the end of the package name????
>
> tks
> --
> Randolph D Dach <rdach <at> telus.net>
> _______________________________________________
> Clfs-support mailing list
> Clfs-support <at> lists.cross-lfs.org
> http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org
_______________________________________________
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 | 2 comments |

Gmane