lunch time and some 'time-to-play' available.
On 21/01/20 09:42, scsijon wrote:
Hi, nice to see a new iso out and it installed ok for me.
Thought i'd start the T2 builder and build a 'generic/minimal' at r49128
as a quick-test before going further.
However I found a couple of problems appearing, two builder script ones
at least that may be worth your attention.
It seems the builder is expecting uname to be in /bin, and it's now in
/usr/bin as a link to /usr/bin/uname26, not sure where you need to
change what in your builder scripts for this but I did a quickfix by
linking /usr/bin/uname26 and /bin/uname and the error went away so it
must be hard coded somewhere(, I had a quick look through them but I
couldn't find it).
No, my mistake, after changing to my own desktop and not T2's, with
further working I found that although this fix took away the error it's
wrong, the uname26 is a link itself to setarch (something totally
different) and /usr/bin has a uname executable in it, the correct thing
to do is link /usr/bin/uname to /bin/uname to deal with the problem
until the scripts are sorted out.
and the glibc package is now failing with 2 errors >
configure: error: /bin/sh ../scripts/config.sub -nocross-linux-gnu failed
?nothing else to help and a script error, any ideas?
haven't done anything here yet
PLUS it's looking for a >
/t2-trunk-r49128/build/default-9.0-svn-generic-x86-64-linux/TOOLCHAIN/tools.cross/sbin/init.d/nscd
?shouldn't this be in ~~/etc/init.d to start with,
no, t2 has duplicate copies of the same scripts both in /sbin/init.d and
/etc/init.d for some reason, sorry but not sure why as i'm use to only
one in /etc/init.d, can you explain the logic of creating it this way
please?
and it's saying to
install SysV Init script 'nscd' package first, which is strange for
build level-0.
I'll look into this last one and see if I can sort out what's up
tomorrow (my free day), can I leave the scripts to you since you most
likely know where to look already?
thanks for the new iso :-)
I shall fix the uname problem I caused and try from scratch, maybe the
glibc problems will go away.
YES, it fixes glibc to build at least although the configure error still
appears, it's not stopping it, and were up to ppl so i'll send this now.
Although package building is seriously repeatedly complaining about
uname, the error is >
You should not call uname during the build!
I'm not sure what to do about this, something in your scripts somewhere?
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
