Hi,
I've downloaded the latest T2 SDE 9.0 and am encountering an error
in the build of base/glibc32:
== 12:40:17 =[1]=> Building base/glibc32 [2.23 9.0-svn].
-> Parallel build using 8 jobs enabled.
-> Reading package config: package/base/glibc32/glibc32.conf
-> Set arch_target to i686-t2-linux-gnu ...
ls: cannot access /opt/T2/t2-trunk-9.0-2-29-2016/package/base/glibc32/../glibc/*.patch.cross:
No such file or directory
-> Preparing build in
src.glibc32.minimal.20160308.124017.12307.flyingleap421
-> Building. Writing output to $root/var/adm/logs/1-glibc32.out
!> }
!> ^
!> ../sysdeps/unix/sysv/linux/posix_fallocate64.c:42:1: error: bp cannot be
used in asm here
!>
/opt/T2/t2-trunk-9.0-2-29-2016/src.glibc32.minimal.20160308.124017.12307.flyingleap421/gli
..
!> Makefile:214: recipe for target 'io/subdir_lib' failed
!> Makefile:9: recipe for target 'all' failed
!> Due to previous errors, no 1-glibc32.log file!
!> (Try enabling xtrace in the config to track an error inside the
build system.)
== 03/08/16 12:41:34 =[1]=> Aborted building package glibc32.
-> Unmounting loop mounts ...
Note that in the above output there is an 'ls: cannot access' error
related to not finding package/base/glibc32/../glibc/*.patch.cross.
I do not know if this is truly a missing file or if the 'ls' command
is simply being used to test for the presence of the file and
skipping its use if not present.
In the ERROR-TXT (attached) I see this near the bottom of the file:
../sysdeps/unix/sysv/linux/posix_fallocate.c: In function 'posix_fallocate':
../sysdeps/unix/sysv/linux/posix_fallocate.c:39:1: error: bp cannot be used in
asm here
<snip>
../sysdeps/unix/sysv/linux/posix_fallocate64.c: In function
'__posix_fallocate64_l64':
../sysdeps/unix/sysv/linux/posix_fallocate64.c:42:1: error: bp cannot be used
in asm here
A google of the error "error: bp cannot be used in asm here" shows a
discussion amongst glibc developers related to a compiler issue
using the newer gcc 5 compiler. However, the patches shown in that
discussion thread appear to already be present in glibc 2.23
(according to the glibc git repository). I've looked at the glibc
2.23 source tar ball included in the T2 SDE and the changes
represented in the patches appear to be present.
This is a bit beyond my knowledge level so any help is appreciated.
I am currently trying to build the minimal configuration:
# ./scripts/Config -cfg minimal
In Config menuconfig system I select LiveCD and turn on xtrace and
save the config (no other changes). Then build:
# ./scripts/Build-Target -cfg minimal
Note that attempts to build '-cfg system' are also failing with
the same error.
My build host is openSuSE LEAP 42.1 x86_64.
One other note, SuSE LEAP does not provide static libraries on the
installation media and actively discourage use of static libs. T2
SDE packages archiver/mine and base/module-init-tools both require
some components be linked static so rather than alter the T2 conf
files for those packages to remove static linking I downloaded and
installed these RPMs:
glibc-devel-static-2.19-19.1.x86_64.rpm
glibc-devel-static-32bit-2.19-19.1.x86_64.rpm
I don't think adding these glibc-devel-static RPMs to the system is
causing an issue because I also saw the glibc32 "error: bp cannot be
used in asm here" before I installed the above RPMs.
Any suggestions?
Thanks,
Mark
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
li...@t2-project.org with a subject of: unsubscribe t2
