<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.linux.lfs.clfs.support">
    <title>gmane.linux.lfs.clfs.support</title>
    <link>http://blog.gmane.org/gmane.linux.lfs.clfs.support</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2603"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2601"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2597"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2594"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2590"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2587"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2584"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2580"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2578"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2571"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2569"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2565"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2561"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2550"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2545"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2539"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2536"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2533"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2532"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2531"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2603">
    <title>Build error</title>
    <link>http://comments.gmane.org/gmane.linux.lfs.clfs.support/2603</link>
    <description>&lt;pre&gt;Hello there,
I am getting compilation error while compiling Texinfo-4.13a.

terminal.c:272: more undefined reference to 'tputs' follow
collect2: ld returned 1 exit status
make[3]: *** [ginfo] Error 1
make[3]: Leaving directory '/mnt/clfs/sources/texinfo-4.13/tools/info'
make[2]: *** [all] Error 2
make[2]: Leaving directory '/mnt/clfs/sources/texinfo-4.13/tools/info'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/mnt/clfs/sources/texinfo-4.13/tools'
make: *** [all] Error 2
make: Leaving directory '/mnt/clfs/sources/texinfo-4.13/tools'

I have successfully installed Ncurses-5.9 as per instructions given in 6.11
of CLFS 1.2

Any suggestion regarding the compilation error?

I am trying to build CLFS for x86_x64 system using Ubuntu 12.04 (64-bit).

Thanks in advance.

&lt;/pre&gt;</description>
    <dc:creator>Nazmul Alam</dc:creator>
    <dc:date>2013-04-24T10:15:53</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2601">
    <title>CLFS 2.0.0 Release Announcement</title>
    <link>http://comments.gmane.org/gmane.linux.lfs.clfs.support/2601</link>
    <description>&lt;pre&gt;We are please to announce Cross Linux From Scratch 2.0.0.

http://trac.cross-lfs.org/wiki/news#AnnouncingCLFS2.0.0Release
http://trac.cross-lfs.org/wiki/download#CurrentStable
http://trac.cross-lfs.org/wiki/read#CurrentStable2.xSeries
http://trac.cross-lfs.org/wiki/errata/CLFS-2.0.0

Thanks to everyone who's helped us. Please report any bugs or issues  
you find on the mailing list or create a ticket. If you need a trac  
account please contact us in #cross-lfs on Freenode.

Kind Regards,

William Harrington

and

Cosmo Hill (Jonathan Norman)
CLFS Release Manager
&lt;/pre&gt;</description>
    <dc:creator>William Harrington</dc:creator>
    <dc:date>2013-04-20T15:16:14</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2597">
    <title>gcc-4.8.0 clfs</title>
    <link>http://comments.gmane.org/gmane.linux.lfs.clfs.support/2597</link>
    <description>&lt;pre&gt;Hello clfs'ers

The clfs-dev book has not been updated for a while and I was limbering up to 
attempt  a clfs-pure64-bit-build (AMD64-cpu ) with gcc-4.7.2  when 
gcc-4.7.3 and gcc-4.8.0  were released.  I noticed also there is a recent  lfs 
build with gcc-4.8.0.  The questios are:-
--a)  Is it worth upgrading the build to gcc-4.8.0 ?  and if so
--b)  does anyone know of patches* for gcc-4.8.0-pure-64-bit-build* as per 
clfs?

Thanks in advance.

sincerely
bv
* the same applies to gcc-4.7.3
&lt;/pre&gt;</description>
    <dc:creator>bvl</dc:creator>
    <dc:date>2013-04-17T17:32:23</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2594">
    <title>CLFS Imminent Release</title>
    <link>http://comments.gmane.org/gmane.linux.lfs.clfs.support/2594</link>
    <description>&lt;pre&gt;Greetings everybody,

So far, not much input from the CLFS 2.0.0 RC-1 release. All seems  
well it looks. CLFS 2.0.0 release is imminent. Hopefully we hear from  
our server's admin so we can get this on a roll.

I guess until that happens, maybe we can all look into the xml scripts  
and make sure all is fine. I know for two things that need fixing and  
I haven't had time to get into it, yet and that's the pkg-config and  
udev pages, maybe. I do know for sure, pkg-config. It as traces of  
autoconf in it. It needs to be rectified. If it wasn't udev, than  
maybe kmod was the other. When I get time off, lots of overtime at  
work, I'll look into it.

I guess one good look over the book's text and that all links are  
working would be good. I have the errata pages at the clfs wiki ironed  
out and the book should be pointing to them, both the RC1, and git  
book, and previous released books. Check them and make sure. If not,  
I'll need to fix them.

RIght now we are waiting to get access to the server again.

Sincerely,

William Harrington
&lt;/pre&gt;</description>
    <dc:creator>William Harrington</dc:creator>
    <dc:date>2013-03-27T00:19:43</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2590">
    <title>clfs-sysroot for arm/raspberrypi</title>
    <link>http://comments.gmane.org/gmane.linux.lfs.clfs.support/2590</link>
    <description>&lt;pre&gt;Greetings,

I have been looking clfs for a raspberrypi project.  I came across the PiLFS 
site  ( http://www.intestinate.com/pilfs/ ) but this appears to be based on a 
prebuild binary rather than traditional (C)LFS instructions of how to do it.
I also browsed clfs-embedded/arm (
 http://cross-lfs.org/view/clfs-embedded/arm/  ) and   for a raspberrypi 
project  and I stumbled on this:- (  
http://www.jayway.com/2013/01/20/linux-from-scratch-on-raspberry-pi/ )

BUT my instinct it with the  sysroot clfs ( 
http://cross-lfs.org/view/clfs-sysroot/arm/ ).  It seem more substantial (it 
uses eglibc for a start), with 
more milage for long-rerm development and  usage as  more-powerful  raspbis 
are rolled out .  Now I take  'sysroot' to mean the whole shebang is built on 
a foreign-host  (in this case an 'x86-cpu-based-computer  and the resultant 
image is ransferred to some device which is then implanted into a raspberrypi 
board).  Am I correct in this interpretation?

Eitherway the current cblfs sysroot looks a little aged (it is dated about 
2009 and appears to be  based on kernel2.6.30 ,gcc-4.4.1, eglibc2.10. 

--Question1:  Has anyone tried the current CLFS-sysroot for a raspberrypi and 
if so what were the results?
--Question2:  Could the current CLFS-sysroot  be updated to mirror packages in  
current clfs development  ( http://cross-lfs.org/view/svn/  
 (  i.e to be based on   gcc-4.6.3, kernel-3.4.17,eglibc-2.15  and if so does 
anyone know of  the relevant arm-CPU//raspberrypi patches for 
eglibc-2.15,gcc-4.6.3,binutils-2.23  and others in the distribution?


thanks in advance
sincerely
bv
&lt;/pre&gt;</description>
    <dc:creator>bvl</dc:creator>
    <dc:date>2013-03-19T15:33:22</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2587">
    <title>build error '/bin/sh: -g: invalid option' when builduClibc in clfs</title>
    <link>http://comments.gmane.org/gmane.linux.lfs.clfs.support/2587</link>
    <description>&lt;pre&gt;
My env:

 

clfs&amp;lt; at &amp;gt;ryang-desktop:/mnt/clfs/source/embedded-0.0.1/uClibc-0.9.31$
env                

CLFS_CPU=i686

CLFS_HOST=i486-cross-linux-gnu

TERM=xterm

CLFS_TARGET=i686-pc-linux-uclibc

OLDPWD=/mnt/clfs/source/embedded-0.0.1

LC_ALL=POSIX

CLFS=/mnt/clfs

PATH=/mnt/clfs/cross-tools/bin:/bin:/usr/bin

PWD=/mnt/clfs/source/embedded-0.0.1/uClibc-0.9.31

CLFS_ARCH=i386

PS1=${debian_chroot:+($debian_chroot)}\u&amp;lt; at &amp;gt;\h:\w\$


SHLVL=1

HOME=/home/clfs

CLFS_ENDIAN=little

_=/usr/bin/env

clfs&amp;lt; at &amp;gt;ryang-desktop:/mnt/clfs/source/embedded-0.0.1/uClibc-0.9.31$

 

 

before I try to build ‘uClibc-0.9.31’,
I patched ‘uClibc-0.9.31-configs-2.patch’and copy ‘config.i386.little’ in clfs dictionary
to ‘uClibc-0.9.31’ as .config, the call ‘make’, error show below:

 

clfs&amp;lt; at &amp;gt;ryang-desktop:/mnt/clfs/source/embedded-0.0.1/uClibc-0.9.31$
sudo make

/bin/sh: -g: invalid
option

Usage:      /bin/sh [GNU long option] [option] ...

      /bin/sh [GNU long option] [option] script-file ...

GNU long options:

      --debug

      --debugger

      --dump-po-strings

      --dump-strings

      --help

      --init-file

      --login

      --noediting

      --noprofile

      --norc

      --posix

      --protected

      --rcfile

      --restricted

      --verbose

      --version

Shell options:

      -irsD or -c command or -O shopt_option          (invocation only)

      -abefhkmnptuvxBCHP or -o option

/bin/sh: -d: invalid option

Usage:      /bin/sh [GNU long option] [option] ...

      /bin/sh [GNU long option] [option] script-file ...

GNU long options:

      --debug

      --debugger

      --dump-po-strings

      --dump-strings

      --help

      --init-file

      --login

      --noediting

      --noprofile

      --norc

      --posix

      --protected

      --rcfile

      --restricted

      --verbose

      --version

Shell options:

      -irsD or -c command or -O shopt_option          (invocation only)

      -abefhkmnptuvxBCHP or -o option

/bin/sh: -d: invalid option

Usage:      /bin/sh [GNU long option] [option] ...

      /bin/sh [GNU long option] [option] script-file ...

GNU long options:

      --debug

      --debugger

      --dump-po-strings

      --dump-strings

      --help

      --init-file

      --login

      --noediting

      --noprofile

      --norc

      --posix

      --protected

      --rcfile

      --restricted

      --verbose

      --version

Shell options:

      -irsD or -c command or -O shopt_option          (invocation only)

      -abefhkmnptuvxBCHP or -o option

/bin/sh: -d: invalid option

Usage:      /bin/sh [GNU long option] [option] ...

      /bin/sh [GNU long option] [option] script-file ...

GNU long options:

      --debug

      --debugger

      --dump-po-strings

      --dump-strings

      --help

      --init-file

      --login

      --noediting

      --noprofile

      --norc

      --posix

      --protected

      --rcfile

      --restricted

      --verbose

      --version

Shell options:

      -irsD or -c command or -O shopt_option          (invocation only)

      -abefhkmnptuvxBCHP or -o option

make: -gcc: Command not found

make: -gcc: Command not found

  MKDIR include/bits

  GEN include/bits/sysnum.h

extra/scripts/gen_bits_syscall_h.sh:
line 31: -gcc: command not found

extra/scripts/gen_bits_syscall_h.sh:
line 27: -gcc: command not found

ERROR: Could not generate
syscalls.

Make sure that you have proper
kernel headers.

Your .config in
KERNEL_HEADERS="" was set to:

/usr/include/

make: *** [include/bits/sysnum.h]
Error 1

clfs&amp;lt; at &amp;gt;ryang-desktop:/mnt/clfs/source/embedded-0.0.1/uClibc-0.9.31$

 

 

 

 

how to solve?       _______________________________________________
Clfs-support mailing list
Clfs-support&amp;lt; at &amp;gt;lists.cross-lfs.org
http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org
&lt;/pre&gt;</description>
    <dc:creator>湘雪秋</dc:creator>
    <dc:date>2013-03-07T02:36:27</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2584">
    <title>CLFS 2.0.0 RC1 Announcement</title>
    <link>http://comments.gmane.org/gmane.linux.lfs.clfs.support/2584</link>
    <description>&lt;pre&gt;We are please to announce Cross Linux From Scratch 2.0.0 RC1.

Read Online: http://cross-lfs.org/view/CLFS-2.0.0-RC1/
Test Logs: http://cross-lfs.org/testsuite-logs/CLFS-2.0.0-RC1/

Thanks to everyone who's helped us. Please report any bugs or issues  
you find on the mailing list or create a ticket. If you need a trac  
account please contact us in #cross-lfs on Freenode.

Kind Regards,
Cosmo Hill (Jonathan Norman)
CLFS Release Manager_______________________________________________
Clfs-support mailing list
Clfs-support&amp;lt; at &amp;gt;lists.cross-lfs.org
http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org
&lt;/pre&gt;</description>
    <dc:creator>Jonathan Norman</dc:creator>
    <dc:date>2013-03-02T01:01:42</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2580">
    <title>Python2.7 problem</title>
    <link>http://comments.gmane.org/gmane.linux.lfs.clfs.support/2580</link>
    <description>&lt;pre&gt;I have been trying to get Python 2.7.3 working for the last few days.  I followed the directions exactly as shown in the CBLFS page.  everything compiled properly however when I try to use python it keeps giving me ELFCLAss wrong.
example 
$python-32 -c 'import struct;print(8 * struct.clacsize("p")' 
returns
32
$python-64 -c 'import struct;print(8 * struct.clacsize("p")' 
returns 
Traceback (most recent call last):
File "&amp;lt;string&amp;gt;", lin 1, in &amp;lt;module&amp;gt;
File "/usr/lib/python2.7/struct.py", line 1, in &amp;lt;module&amp;gt;
   from _struct import *
ImportError: /usr/lib/python2.7/lib-dynload/_struct.so: wrong ELF class: ELFCLASS32

It seems the python-64 is going to the wrong set of libraries, should be going after the /usr/lib64/python2.7 libraries.  
If I use ldd -v /usr/lib/python2.7/lib-dynload/_struct.so  it returns showing /usr/lib and /lib libraries
if I use ldd -v /usr/lib64/python2.7/lib-dynload/_struct.so it returns /usr/lib64 and /lib64 libraries.


&lt;/pre&gt;</description>
    <dc:creator>Randolph D Dach</dc:creator>
    <dc:date>2013-02-20T04:43:12</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2578">
    <title>(no subject)</title>
    <link>http://comments.gmane.org/gmane.linux.lfs.clfs.support/2578</link>
    <description>&lt;pre&gt;Hello,


          i am following cross-linux from scratch book for buliding linux
for arm.

          i have created all the images how to make it work in QEMU.
_______________________________________________
Clfs-support mailing list
Clfs-support&amp;lt; at &amp;gt;lists.cross-lfs.org
http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org
&lt;/pre&gt;</description>
    <dc:creator>Hardik Gohil</dc:creator>
    <dc:date>2013-02-06T08:45:16</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2571">
    <title>gcc -Os regression?</title>
    <link>http://comments.gmane.org/gmane.linux.lfs.clfs.support/2571</link>
    <description>&lt;pre&gt; Okay, sorry to hit you guys up with this,  but has anyone else
noticed the 25% increase in stripped executable size in gcc-post-4.2.4 vs
4.2.4? I cant find *ANYTHING* in bugtraq
thank you.
-david
PS, if anyone would like to see some output of a sample package with the
differences, I'd be happy to provide it.
_______________________________________________
Clfs-support mailing list
Clfs-support&amp;lt; at &amp;gt;lists.cross-lfs.org
http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org
&lt;/pre&gt;</description>
    <dc:creator>david vann</dc:creator>
    <dc:date>2013-02-03T21:21:02</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2569">
    <title>Section 10.24 multiarch_wrapper.c compile error</title>
    <link>http://comments.gmane.org/gmane.linux.lfs.clfs.support/2569</link>
    <description>&lt;pre&gt;Sent from my android device.

I'm getting an error compiling the multiarch_wrapper.c file at line 45 :8: 'filename' undeclared (first use in this function). I see it's being used on line 23 as '&amp;amp;filename'. My questions is, is the apmerstand needed in this if statement? I'm no C programmer so if anyone  knows of how I can fix this error I would be grateful. 

_______________________________________________
Clfs-support mailing list
Clfs-support&amp;lt; at &amp;gt;lists.cross-lfs.org
http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org
&lt;/pre&gt;</description>
    <dc:creator>dsreyes1014&lt; at &gt;gmail.com</dc:creator>
    <dc:date>2013-01-31T23:46:16</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2565">
    <title>Booting into temporary environment???</title>
    <link>http://comments.gmane.org/gmane.linux.lfs.clfs.support/2565</link>
    <description>&lt;pre&gt;Ok finished the boot method but not sure how to boot into it now. I know 
noobie. I updated grub on the host computer but it doesn't pick up the 
temporary environment. Not sure if it's supposed to. I'm lost here after 
creating the tar file of ${CLFS} in section 7.19. Don't know where to 
continue. Any guidance???
&lt;/pre&gt;</description>
    <dc:creator>Andrew Reyes</dc:creator>
    <dc:date>2013-01-30T22:51:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2561">
    <title>Flex not found config error on CLFS 7.12 boot method</title>
    <link>http://comments.gmane.org/gmane.linux.lfs.clfs.support/2561</link>
    <description>&lt;pre&gt;Hello again guys trying again the multilib build and got passed the 
e2fsprog section on the boot method. I'm now hung up at the grub install 
of the CLFS multilib build section 7.12. It's giving me a config error: 
flex not found. Am I missing a symlink somewhere?
&lt;/pre&gt;</description>
    <dc:creator>Andrew Reyes</dc:creator>
    <dc:date>2013-01-30T07:12:43</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2550">
    <title>CLFS 7.6 E2fsprogs-1.42.6 configuration error....</title>
    <link>http://comments.gmane.org/gmane.linux.lfs.clfs.support/2550</link>
    <description>&lt;pre&gt;I'm getting stuck at 7.6 of the book and the error is telling me 'external
blkid library not found' and stops. I was getting a 'external uuid library
not found' but I copied libuuid.so.1.3.0 from tools/lib64/libuuid.so.1.3.0
into cross-tools/x86_64-unknown-linux-gnu/lib64/libuuid.so and that led me
to the 'external blkid library not found'. I tried copying the libblkid.so
file in tools/lib64 into cross-tools/x86_64-unknown-linux-gnu and I still
get the same error. Any guidance on this would truly be appreciated.
_______________________________________________
Clfs-support mailing list
Clfs-support&amp;lt; at &amp;gt;lists.cross-lfs.org
http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org
&lt;/pre&gt;</description>
    <dc:creator>Andrew Reyes</dc:creator>
    <dc:date>2013-01-23T14:57:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2545">
    <title>gmp check</title>
    <link>http://comments.gmane.org/gmane.linux.lfs.clfs.support/2545</link>
    <description>&lt;pre&gt;CLFS-TRUNK-GIT-20130113/x86

Everything smooth until 10.9. GMP-5.0.5, make check.
Google shows similar messages, not necessarily clfs related, but no
solution whatsoever. The book gives no hint about what to do when the
critical test suite fails. Anyone managed to pass this stage?

Jorge Almeida

(...)
Making check in cxx
make[3]: Entering directory `/sources/gmp-5.0.5/tests/cxx'
make  t-assign t-binary t-cast t-constr t-headers t-istream t-locale
t-misc t-ops t-ostream t-prec t-rand t-ternary t-unary
make[4]: Entering directory `/sources/gmp-5.0.5/tests/cxx'
make[4]: `t-assign' is up to date.
make[4]: `t-binary' is up to date.
make[4]: `t-cast' is up to date.
make[4]: `t-constr' is up to date.
make[4]: `t-headers' is up to date.
make[4]: `t-istream' is up to date.
make[4]: `t-locale' is up to date.
make[4]: `t-misc' is up to date.
make[4]: `t-ops' is up to date.
make[4]: `t-ostream' is up to date.
make[4]: `t-prec' is up to date.
make[4]: `t-rand' is up to date.
make[4]: `t-ternary' is up to date.
make[4]: `t-unary' is up to date.
make[4]: Leaving directory `/sources/gmp-5.0.5/tests/cxx'
make  check-TESTS
make[4]: Entering directory `/sources/gmp-5.0.5/tests/cxx'
/bin/sh: line 5:  8833 Segmentation fault      (core dumped) ${dir}$tst
FAIL: t-assign
PASS: t-binary
PASS: t-cast
/bin/sh: line 5:  8887 Segmentation fault      (core dumped) ${dir}$tst
FAIL: t-constr
PASS: t-headers
PASS: t-istream
PASS: t-locale
PASS: t-misc
PASS: t-ops
PASS: t-ostream
PASS: t-prec
/bin/sh: line 5:  9026 Segmentation fault      (core dumped) ${dir}$tst
FAIL: t-rand
PASS: t-ternary
PASS: t-unary
======================================================================================
3 of 14 tests failed
&lt;/pre&gt;</description>
    <dc:creator>Jorge Almeida</dc:creator>
    <dc:date>2013-01-19T12:35:10</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2539">
    <title>Problem with EGLIBC in 10.7 on x86_64-Pure64</title>
    <link>http://comments.gmane.org/gmane.linux.lfs.clfs.support/2539</link>
    <description>&lt;pre&gt;Frankly, I'm surprised to be getting any errors in Chapter 10. I figured 
things would be smooth sailing from here on out, since I'm booted into 
the target environment.

I'm using the current development snapshot of the CLFS book, version 
20121227-x86_64-Pure64.

Anyway, when linking libresolv.so, I get the following errors:

/native/eglibc/build/resolv/libresolv_pic.a(gethnamaddr.os): In function 
`getanswer':
/native/eglibc/eglibc-2.15/resolv/gethnamaddr.c:180: undefined reference 
to `__stack_chk_guard'
/native/eglibc/eglibc-2.15/resolv/gethnamaddr.c:483: undefined reference 
to `__stack_chk_guard'
/native/eglibc/build/resolv/libresolv_pic.a(gethnamaddr.os): In function 
`res_gethostbyaddr':
/native/eglibc/eglibc-2.15/resolv/gethnamaddr.c:644: undefined reference 
to `__stack_chk_guard'
/native/eglibc/eglibc-2.15/resolv/gethnamaddr.c:783: undefined reference 
to `__stack_chk_guard'
/native/eglibc/build/resolv/libresolv_pic.a(gethnamaddr.os): In function 
`__GI_res_gethostbyname2':
/native/eglibc/eglibc-2.15/resolv/gethnamaddr.c:510: undefined reference 
to `__stack_chk_guard'
/native/eglibc/build/resolv/libresolv_pic.a(res_debug.os):/native/eglibc/eglibc-2.15/resolv/res_debug.c:287: 
more undefined references to `__stack_chk_guard' follow

The command being used to link is:
gcc   -shared -static-libgcc -Wl,-O1  -Wl,-z,defs 
-Wl,-dynamic-linker=/lib64/ld-linux-x86-64.so.2 
-B/native/eglibc/build/csu/ 
-Wl,--version-script=/native/eglibc/build/libresolv.map 
-Wl,-soname=libresolv.so.2 -Wl,-z,combreloc -Wl,-z,relro 
-Wl,--hash-style=both  -L/native/eglibc/build 
-L/native/eglibc/build/math -L/native/eglibc/build/elf 
-L/native/eglibc/build/dlfcn -L/native/eglibc/build/nss 
-L/native/eglibc/build/nis -L/native/eglibc/build/rt 
-L/native/eglibc/build/resolv -L/native/eglibc/build/crypt 
-L/native/eglibc/build/nptl 
-Wl,-rpath-link=/native/eglibc/build:/native/eglibc/build/math:/native/eglibc/build/elf:/native/eglibc/build/dlfcn:/native/eglibc/build/nss:/native/eglibc/build/nis:/native/eglibc/build/rt:/native/eglibc/build/resolv:/native/eglibc/build/crypt:/native/eglibc/build/nptl 
-o /native/eglibc/build/resolv/libresolv.so -T 
/native/eglibc/build/shlib.lds /native/eglibc/build/csu/abi-note.o 
-Wl,--whole-archive /native/eglibc/build/resolv/libresolv_pic.a 
-Wl,--no-whole-archive /native/eglibc/build/elf/interp.os 
/native/eglibc/build/libc.so /native/eglibc/build/libc_nonshared.a 
-Wl,--as-needed /native/eglibc/build/elf/ld.so -Wl,--no-as-needed

This appears to be because the files in eglibc-2.15/resolv have been 
compiled with the '-fstack-protector' switch, but neither that switch 
nor '-lssp' is supplied to the linker.

In fact, if I add "-v, -Wl,--verbose" to the command, I see that the 
linker doesn't even attempt to bring in libssp.

I could add '-lssp' to the link statement, but I wonder if that's 
correct. libssp.so is in /tools, and I was under the impression that we 
don't want that brought in.

It seems to me that either I should tell configure that I don't want to 
use stack protection, or that I should have configured GCC that way all 
the way back in 5.17. Pretty sure that either of those would work. And 
while I'd rather just fix it now, rather than essentially starting over, 
I'm wondering if the whole thing is a symptom of my doing something else 
wrong.

I found a thread in the LFS archives from two years ago where a person 
had the exact same problem. From reading the thread, it doesn't appear 
that a resolution was ever discovered.

http://www.mail-archive.com/lfs-support&amp;lt; at &amp;gt;linuxfromscratch.org/msg13219.html

Any thoughts, or should I plan on starting over from scratch?

&lt;/pre&gt;</description>
    <dc:creator>Chris J. Breisch</dc:creator>
    <dc:date>2013-01-16T12:47:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2536">
    <title>Gcc 4.7.x and eglibc 2.16</title>
    <link>http://comments.gmane.org/gmane.linux.lfs.clfs.support/2536</link>
    <description>&lt;pre&gt;Hi


Yes i have some patches for pure x64 for gcc 4.7.x, seems to work ok,

i can post to list, or pastebin them if u want them

4.7.2, seems better than 4.7.1.
used --disable-build-with-cxx --disable-build-poststage1-with-cxx 
--with-native-system-header-dir=/tools --disable-ppl-version-check 
--disable-cloog-version-check --enable-checking=release


Eglibc 2.16 has --enable-obsolete-rpc option to bring back headers, i 
used r21796, probably has been updated since then.


martin
&lt;/pre&gt;</description>
    <dc:creator>Martin Ward</dc:creator>
    <dc:date>2012-12-21T12:12:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2533">
    <title>clfs, eglibc and gcc question</title>
    <link>http://comments.gmane.org/gmane.linux.lfs.clfs.support/2533</link>
    <description>&lt;pre&gt;Greetings,

I have been using clfs (amd64 CPU's pure64 bit)  for 5/6 years now.  I need 
nfs4  with gssd /rpcbind and  in my last build  (currentl clfs development)    
this failed to work.  I tentatively tracked this down to eglibc-2.15  as  
rpcbind /nfs4/glibc  currently have some 'development issues'   I urgently 
need to upgrade to eglibc-2.16  if only to prove that nfs4 now works  or not 
work.  I also think it migh well be worth while upgrading from gcc-4.6.3  to 
gcc-4.7.2.  Therefore these are my questions:-

a) are pure 64bit (amd64 cpu) clfs patches available for gcc-4.7.2 ?
b) are appropriate clfs patches available for eglibc-2.16 and if not can clfs 
be built  with eglibc-2.15 without patches.?

Thanks in advance

sincerelyluxInteg
&lt;/pre&gt;</description>
    <dc:creator>bvl</dc:creator>
    <dc:date>2012-12-17T12:13:05</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2532">
    <title>GCC-4.6.3 - Static</title>
    <link>http://comments.gmane.org/gmane.linux.lfs.clfs.support/2532</link>
    <description>&lt;pre&gt;I'm trying to build CLFS Version GIT-20121124-x86. I extracted the fs
from
http://cross-lfs.org/~kb0iic/livecdupd/x86/lfslivecd-x86-6.3-r2160-updated-nosrc.iso
to
use as host, via chroot. Compilation is failing at 5.14. "Cross
GCC-4.6.3 - Static" :

/clfs/sources/gcc-build/./gcc/xgcc -B/clfs/sources/gcc-build/./gcc/ -B/cros
s-tools/i686-pc-linux-gnu/bin/ -B/cross-tools/i686-pc-linux-gnu/lib/ -isyst
em /cross-tools/i686-pc-linux-gnu/include -isystem /cross-tools/i686-pc-lin
ux-gnu/sys-include    -g -O2 -O2  -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTU
RE  -W -Wall -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prot
otypes -Wold-style-definition  -isystem ./include  -fPIC -g  -DIN_LIBGCC2 -
D__GCC_FLOAT_NOT_NEEDED -fno-stack-protector -Dinhibit_libc  -I. -I. -I../.
././gcc -I../../../gcc-4.6.3/libgcc -I../../../gcc-4.6.3/libgcc/. -I../../.
./gcc-4.6.3/libgcc/../gcc -I../../../gcc-4.6.3/libgcc/../include  -DHAVE_CC
_TLS  -DUSE_TLS -o _fixunssfsi.o -MT _fixunssfsi.o -MD -MP -MF _fixunssfsi.
dep -DL_fixunssfsi -c ../../../gcc-4.6.3/libgcc/../gcc/libgcc2.c \

In file included from /clfs/sources/gcc-build/./gcc/include-fixed/syslimits
.h:7:0,
                 from /clfs/sources/gcc-build/./gcc/include-fixed/limits.h:
34,
                 from ../../../gcc-4.6.3/libgcc/../gcc/libgcc2.c:1689:
/clfs/sources/gcc-build/./gcc/include-fixed/limits.h:169:61: error: no incl
ude path in which to search for limits.h
make[1]: *** [_fixunssfsi.o] Error 1
make[1]: Leaving directory `/clfs/sources/gcc-build/i686-pc-linux-gnu/libgc
c'
make: *** [all-target-libgcc] Error 2
clfs:/clfs/sources/gcc-build$

I'm doing it By The Book, except for a few aliases and colors.
Some data that might be relevant:

$ env
CLFS_HOST=i486-cross-linux-gnu
TERM=xterm
CLFS_TARGET=i686-pc-linux-gnu
OLDPWD=/clfs/sources/gcc-4.6.3
LC_ALL=POSIX
LS_COLORS=di=01;34:ln=01;36:pi=40;33:so=01;35:do=01;35:bd=40;33;41:cd=40;34;42:or=01;37;41:mi=01;37;41:su=37;41:sg=30;43:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lz=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.rar=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:
 *.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:
 *.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01;35:*.ogx=01;35:*.pdf=00;32:*.ps=00;32:*.txt=00;32:*.patch=00;32:*.diff=00;32:*.log=00;32:*.tex=00;32:*.doc=00;32:*.aac=00;36:*.au=00;36:*.flac=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.axa=00;36:*.oga=00;36:*.spx=00;36:*.xspf=00;36:
CLFS=/mnt/clfs
PATH=/cross-tools/bin:/bin:/usr/bin
PWD=/clfs/sources/gcc-build
PS1=\u:\w\$
SHLVL=1
HOME=/home/clfs
_=/usr/bin/env


$ cat  ~/.bashrc
set +h
umask 022
CLFS=/mnt/clfs
LC_ALL=POSIX
PATH=/cross-tools/bin:/bin:/usr/bin
export CLFS LC_ALL PATH
export CLFS_HOST="i486-cross-linux-gnu"
export CLFS_TARGET="i686-pc-linux-gnu"
# aliases
alias ls='ls --color=auto'
alias grep='grep --colour=auto'
alias la='ls -a'
alias ll='ls -l'
alias lla='ls -al'
alias up='cd ..; ls'
alias lu='cd ..; ls -l'
#
alias rm='rm -i'
alias cp='cp -i'
alias mv='mv -i'
#
eval $(dircolors -b ~/.dir_colors)
shopt -s checkwinsize
shopt -s histappend

TIA

Jorge Almeida
&lt;/pre&gt;</description>
    <dc:creator>Jorge Almeida</dc:creator>
    <dc:date>2012-11-28T09:45:40</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2531">
    <title>Unexpected failures when installing Binutils-2.23</title>
    <link>http://comments.gmane.org/gmane.linux.lfs.clfs.support/2531</link>
    <description>&lt;pre&gt;Hi list,

I have encountered several unexpected failures when installing
Binutils-2.23 as basic system software (Chapter 10 of the CLFS book -
version GIT-20121112).

Specifically, after I ran command "make check", the test suite for
Binutils reported the summary as follows:

                === binutils Summary ===

# of expected passes            81
# of unexpected failures        3
# of unresolved testcases       1
# of unsupported tests          3

The three unexpected failures are as follows (you can find complete
test result at the end of this email):

FAIL: objdump -W (reason: unexpected output)
FAIL: objdump -W
FAIL: readelf -wa (compressed)

The host distribution and version being used to create CLFS is Ubuntu
12.04.1 LTS (Linux version 3.2.0-33).

The architecture of the host and target are x86 and PowerPC respectively.

Other environment variables include:
$CLFS_HOST  = i686-cross-linux-gnu
$CLFS_TARGET = powerpc-unknown-linux-gnu
$BUILD32 =
$BUILD64

Where I have deviated from the book include:
a) I have skipped installation of E2fsprogs,  Hfsutils, Powerpc-Utils,
and Yaboot because my target is an embedded system.
b) I have skipped installation of zlib 1.2.7 and Texinfo-4.13a when
constructing the temporary system because of some unresolved errors (I
can post these error messages if needed).

I have been searching answers for those unexpected failures online for
hours but I am still out of luck. Any thoughts will be appreciated!



Complete test result of Binutils-2.23:

                === binutils tests ===

Schedule of variations:
    unix

Running target unix
Running /sources/binutils-2.23/binutils/testsuite/binutils-all/ar.exp ...
PASS: ar long file names
PASS: ar symbol table
PASS: ar thin archive
PASS: ar thin archive with nested archive
PASS: ar argument parsing
PASS: ar deterministic archive
PASS: ar deleting an element
PASS: ar moving an element
PASS: ar unique symbol in archive
Running /sources/binutils-2.23/binutils/testsuite/binutils-all/arm/objdump.exp
...
Running /sources/binutils-2.23/binutils/testsuite/binutils-all/bfin/objdump.exp
...
Running /sources/binutils-2.23/binutils/testsuite/binutils-all/compress.exp ...
ERROR: /sources/binutils-2.23/binutils/testsuite/binutils-all/dw2-1.S:
assembly failed
UNRESOLVED: compressed debug sections
Running /sources/binutils-2.23/binutils/testsuite/binutils-all/dlltool.exp ...
Running /sources/binutils-2.23/binutils/testsuite/binutils-all/elfedit.exp ...
UNSUPPORTED: Update ELF header 1
PASS: Update ELF header 2
PASS: Update ELF header 3
UNSUPPORTED: Update ELF header 4
Running /sources/binutils-2.23/binutils/testsuite/binutils-all/hppa/objdump.exp
...
Running /sources/binutils-2.23/binutils/testsuite/binutils-all/i386/i386.exp ...
Running /sources/binutils-2.23/binutils/testsuite/binutils-all/m68k/objdump.exp
...
Running /sources/binutils-2.23/binutils/testsuite/binutils-all/nm.exp ...
PASS: nm (no arguments)
PASS: nm -g
PASS: nm -g on unique symbols
PASS: nm -P
Running /sources/binutils-2.23/binutils/testsuite/binutils-all/objcopy.exp ...
PASS: objcopy (simple copy)
PASS: objcopy --reverse-bytes
PASS: objcopy -i --interleave-width
PASS: objcopy -O srec
PASS: objcopy --set-start
PASS: objcopy --adjust-start
PASS: objcopy --adjust-vma
PASS: objcopy --adjust-section-vma +
PASS: objcopy --adjust-section-vma =
PASS: strip preserving OS/ABI
PASS: strip
PASS: strip with saving a symbol
PASS: simple objcopy of executable
PASS: run objcopy of executable
PASS: run stripped executable preserving OS/ABI
PASS: run stripped executable
PASS: run stripped executable with saving a symbol
PASS: keep only debug data
PASS: simple objcopy of debug data
PASS: objcopy (ELF unknown section type)
PASS: objcopy (ELF group)
PASS: objcopy (ELF group)
PASS: objcopy (ELF group)
PASS: objcopy (ELF group)
PASS: copy removing group member
PASS: copy removing all group member
PASS: copy with setting section flags 1
PASS: add notes section
PASS: copy with setting section flags 2
PASS: copy with setting section flags 3
PASS: strip --strip-unneeded on common symbol
PASS: strip with section group 1
PASS: strip with section group 2
PASS: strip empty file
PASS: strip with section group 4
PASS: strip with section group 5
PASS: strip with section group 6
PASS: strip with section group 7
PASS: strip with section group 8
PASS: strip with section group 9
PASS: strip on STB_GNU_UNIQUE
PASS: --localize-hidden test 1
PASS: unordered .debug_info references to .debug_ranges
UNSUPPORTED: unordered .debug_info references to .debug_ranges
PASS: objcopy add-section
PASS: objcopy add-empty-section
PASS: objcopy on sections with SHF_EXCLUDE
PASS: strip --strip-unneeded on sections with SHF_EXCLUDE
PASS: --localize-hidden test 2
Running /sources/binutils-2.23/binutils/testsuite/binutils-all/objdump.exp ...
PASS: objdump -i
PASS: objdump -f
PASS: objdump -h
PASS: objdump -t
PASS: objdump -r
PASS: objdump -s
PASS: objdump -s -j .zdebug_abbrev
FAIL: objdump -W (reason: unexpected output)
FAIL: objdump -W
PASS: objdump -WL
Running /sources/binutils-2.23/binutils/testsuite/binutils-all/readelf.exp ...
PASS: finding out ELF size with readelf -h
PASS: readelf -h
PASS: readelf -S
PASS: readelf -s
PASS: readelf -r
PASS: readelf -wi
FAIL: readelf -wa (compressed)
PASS: readelf -p
PASS: readelf -n
Running /sources/binutils-2.23/binutils/testsuite/binutils-all/size.exp ...
PASS: size (no arguments)
PASS: size -A
Running /sources/binutils-2.23/binutils/testsuite/binutils-all/vax/objdump.exp
...
Running /sources/binutils-2.23/binutils/testsuite/binutils-all/windres/windres.exp
...
Running /sources/binutils-2.23/binutils/testsuite/binutils-all/x86-64/x86-64.exp
...

                === binutils Summary ===

# of expected passes            81
# of unexpected failures        3
# of unresolved testcases       1
# of unsupported tests          3
&lt;/pre&gt;</description>
    <dc:creator>Bin Huang</dc:creator>
    <dc:date>2012-11-27T02:31:53</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.lfs.clfs.support/2530">
    <title>Updated livecd again</title>
    <link>http://comments.gmane.org/gmane.linux.lfs.clfs.support/2530</link>
    <description>&lt;pre&gt;Howdy all,

Today I updated the lfs livecd. I added lmsensors so people can view  
their system stats while building, and I've included more modules in  
the running kernel to support more devices, including coretemp which  
sensors can use.

http://cross-lfs.org/~kb0iic/livecdupd/

This works as a good host to build current CLFS and LFS builds.

You can use jhalfs to build LFS or CLFS, but some user intervention  
will need to be required to get a full jhalfs build. I've used it  
fine, with intervention, to build x86_64 to sparc64, ppc, and all. May  
build a hint for it later. Who knows.

Sincerely,

William Harrington
&lt;/pre&gt;</description>
    <dc:creator>William Harrington</dc:creator>
    <dc:date>2012-11-23T22:46:58</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.linux.lfs.clfs.support">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.linux.lfs.clfs.support</link>
  </textinput>
</rdf:RDF>
