Thanks Rene,
I will update my chroot scripts so that if they don't find uname & arch
in the proper place, it will print a warning and correct the situation.
I was also wondering about python on the iso image, on the last image i
was testing, there was no symlink between python3 & python, so that
everything in the Build-Target that was looking for python was failing.
If this was fixed in the iso, that would solve half of the trouble, but
it will still be an issue in the build stages where it chroots, and
there is no python in the chroot. so I think some of the t2 python
patches that I had would still be necessary.
Also, once I hit the glib build, I will probably revert glibc as per
your warning.
Will continue with more of the build, and let you know the regressions
as they pop up.
Jan
On 2/3/2020 4:19 AM, René Rebe wrote:
Hi,
as per my long YT development & test livestream this is coreutils not being
installed correctly causing uname and arch not being in /bin
You can probably move them over and re build coreutils to fully fix this.
Yes, it is also rather annoying and time consuming for myself that each time we
spin an ISO there are upstream regressions. Warning: t2/trunk glibc update
breaks glib and thus many other depends if you build a large package selection.
I will try to hunt down what is wrong between glib and glibc another day,
Google and mailing lists did not yet had an answer for that @GLIBC PRIVATE
symbol. For now I would locally revert the glibc update…
René
On 3. Feb 2020, at 06:04, Jan Rovins <[email protected]> wrote:
Hi Rene,
Can't seem to get at anything useful to trace this, it's failing very early in
the T2 wrappers, before the glibc debug dir is created.
ERROR-LOG attached.
Jan
On 2/2/20 11:08 PM, Jan Rovins wrote:
Hi Rene & List.
Just got my new fast build server set up, and saw that the new iso was out, so
I figured that I'd try a fresh T2 chroot build with the latest from svn.
Attached are the scripts that I'm using to set up the chroots, if you wan to review
them & share them on the site.
I will send outy notes on each regression as I hit them.
The build is a minimal generic, without anything special.
The first thing that I ran into was with glibc stage 0:
===[eval_config_command:284 (last $?=0)> ../configure
--prefix=/opt/t2-trunk/build/default-9.0-svn-generic-x86-64-linux/usr
--enable-hacker-mode
--with-headers=/opt/t2-trunk/build/default-9.0-svn-generic-x86-64-linux/usr/include
--with-libpam --with-pam --enable-libpam --enable-pam --with-tls --with-__thread
--enable-obsolete-rpc --disable-profile --disable-multi-arch
--enable-kernel=2.6.32 --with-fp --with-gnu-binutils --build=-nocross-linux-gnu
--host=x86_64-t2-linux-gnu --cache-file=./config.cache --without-gd
configure: loading cache ./config.cache
checking build system type... config.sub: invalid option -nocross-linux-gnu
Try `config.sub --help' for more information.
configure: error: /bin/sh ../scripts/config.sub -nocross-linux-gnu failed
Due to previous errors, no 0-glibc.log file!
(Try enabling xtrace in the config to track an error inside the build system.)
--- BUILD ERROR ---
Will start on debugging this next, and send an update shortly.
Jan
<ERROR-LOG.txt>-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
