Hi scsijon,
I don't have access to the exact revisions right now, since that machine
is off, and I am leaving for work soon, but was using the base image
from the latest iso, and I pulled down the T2 SDE last night, so it
would be the latest revision as of yesterday. I will post the exact
numbers later tonight when I am working on it again.
The actual error was right before that, where configure was bombing out
on the previous line, the nscd failure was because the glibc project was
then trying to do something that depended on a piece of ncsd that it
should have installed itself, but due to the previous failure, it didn't
hapen. But that link on why not to use ncsd was very enlightening, I now
understand why it's not a good idea to use it as the final DNS in a distro.
Jan
On 2/3/2020 3:03 AM, scsijon wrote:
It seems to want you to install nscd, however nscd is basically out of
date and a nusance, doesn't do all functions.
See https://jameshfisher.com/2018/02/05/dont-use-nscd/.
I don't get your error at present.
What revision T2 build system have you installed by the way? I'm now
working towards testing r49191 (but with the 5.4.17 kernel NOT 5.5.1)
next and don't intend proceeding further until i'm happy with it, as I
have a 'minimum' at r49158 working and want to doc absolutely
everything already done first before starting the build process again.
regards
scsijon
On 03/02/20 16:04, Jan Rovins 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
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
