-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Forget my earlier posts today, my brain wasn't yet switched on :)

> libdl.a is needed for Binutils tests, and libc.a is needed for GCC's 
> tests. So, they should be moved later. I changed the book just now.

Brilliant, i've svn-ed the latest book, make-d it, read it, used it.
Book version is now: SVN-20070705.
Retraced my steps, moved back libc.a, libdl.a, rebuilt glibc and gcc.
And sure enough: it works this time.
At least, i have now succesfully built the butterfly toolchain.

The glibc tests still fail as do the gcc tests (fair enough there's a blurb
in the 6.12 about 'the tests will be bad').

Should they complete without errors ? The book at least mentions that the
glibc tests can return one error in 'posix/annexc'. But my make -k check
returns a bunch of them and then stops (see earlier post).

And I guess the tcl/dejagnu/expect packages are built for the gcc/binutils
tests with a reason.


Two things I noticed in '6.12. Butterfly Toolchain':

  echo | cc -dM -E - | grep -E 'PIC|SSP|FORTIFY|OPTIMIZE'
doesn't list '#define __OPTIMIZE__ 1'
Not sure if this will be a problem as the fgets-overflow.c and
strcpy-overflow.c tests show the expected output.

And:
"The next commands demonstrates that without any protection this program can
run a buffer overflow silently, without any warnings, errors, or crashes:"

ehm:
  #gcc -o fgets-overflow fgets-overflow.c \
     -fno-stack-protector -U_FORTIFY_SOURCE -Wall -Wformat=2
  # echo abcdefghijklm | ./fgets-overflow 14
  abcdefghijklm
  Segmentation fault
I wouldn't call that exactly "silently, without crashes".

Thanks so far,
Albert
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGjLmWKltZixSsH2QRA4jlAJ4lwm0Qe/8PYv6rFsVMJ5CYbdt3zACfQ+AA
P3lBLS24JWipT7qYIv0JEQI=
=TpRg
-----END PGP SIGNATURE-----
-- 
http://linuxfromscratch.org/mailman/listinfo/hlfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to