Build T2-TRUNK

[Josmar Calin De Pierri]

Hello!

While trying to build T2-TRUNK, that I synced today, using as the build
system a VM where I installed t2-8.0-minimal-x86_64.iso, I got the error
below, that I can't solve yet:

== 18:37:34 =[0]=> Building base/autoconf [2.69 9.0-trunk].
-> Preparing build in
src.autoconf.default.20131122.183732.11794.TCC-T2
-> Building. Writing output to $root/var/adm/logs/0-autoconf.out
!> checking whether directories can have trailing spaces... yes
!> checking for expr... /usr/bin/expr
!> checking for GNU M4 that supports accurate traces...
configure: error: no acceptable m4 could be found in $PATH.
!> GNU M4 1.4.6 or later is required; 1.4.16 or newer is
recommended.
!> GNU M4 1.4.15 uses a buggy replacement strstr on some
systems.
!> Glibc 2.9 - 2.12 and GNU M4 1.4.11 - 1.4.15 have another
strstr bug.
!> Due to previous errors, no 0-autoconf.log file!
!> (Try enabling xtrace in the config to track an error inside
the build system.)
== 11/22/13 18:37:49 =[0]=> Aborted building package autoconf.
-> Unmounting loop mounts ...

Any hints?

Tks,
Josmar

[i***@ns.pandcinfo.ro]

Hi,

1. use configure to create a default configuration. give it any name you
want.
2. select minimal x86 in config and leave everything as it is.
3. use download -required to download all packages ( requires a fair
amount of coffee since the process is time consuming)
4. use ./scripts emerge-pkg -cfg yourconfig m4 to update your m4.
5. try rebuilding again.

the issue you are facing is that base minimal t2 is not in sync anymore
with the current updated package list. We are struggling to create an
updated 9.0 image but it seems we are not having enough time to finalize.

regards,

Iulian

Post by Josmar Calin De Pierri
Hello!
While trying to build T2-TRUNK, that I synced today, using as the build
system a VM where I installed t2-8.0-minimal-x86_64.iso, I got the error
== 18:37:34 =[0]=> Building base/autoconf [2.69 9.0-trunk].
-> Preparing build in
src.autoconf.default.20131122.183732.11794.TCC-T2
-> Building. Writing output to $root/var/adm/logs/0-autoconf.out
!> checking whether directories can have trailing spaces... yes
!> checking for expr... /usr/bin/expr
!> checking for GNU M4 that supports accurate traces...
configure: error: no acceptable m4 could be found in $PATH.
!> GNU M4 1.4.6 or later is required; 1.4.16 or newer is
recommended.
!> GNU M4 1.4.15 uses a buggy replacement strstr on some
systems.
!> Glibc 2.9 - 2.12 and GNU M4 1.4.11 - 1.4.15 have another
strstr bug.
!> Due to previous errors, no 0-autoconf.log file!
!> (Try enabling xtrace in the config to track an error inside
the build system.)
== 11/22/13 18:37:49 =[0]=> Aborted building package autoconf.
-> Unmounting loop mounts ...
Any hints?
Tks,
Josmar

[Josmar Calin De Pierri]

Hi Iulian.

Great hint!
I updated m4 (and some others; installed libffi and python) and my build is progressing for some good time now ...

Thanks,
Josmar


Josmar Calin De Pierri
Analista de Suporte
COAMO - Campo Mourão/PR
Fone: (44) 3599-8298 ou Ramal Interno 8298
www.coamo.com.br


-----Original Message-----
From: ***@ns.pandcinfo.ro [mailto:***@ns.pandcinfo.ro]
Sent: Monday, November 25, 2013 6:18 AM
To: Josmar Calin De Pierri
Cc: T2 developers mailing list
Subject: Re: [t2] Build T2-TRUNK

Hi,

1. use configure to create a default configuration. give it any name you
want.
2. select minimal x86 in config and leave everything as it is.
3. use download -required to download all packages ( requires a fair
amount of coffee since the process is time consuming)
4. use ./scripts emerge-pkg -cfg yourconfig m4 to update your m4.
5. try rebuilding again.

the issue you are facing is that base minimal t2 is not in sync anymore
with the current updated package list. We are struggling to create an
updated 9.0 image but it seems we are not having enough time to finalize.

regards,

Iulian

[i***@ns.pandcinfo.ro]

hi Josmar,

it would be good if you update perl also. It depends very much on what you
intend to build. My advice would be to build a minimal and fix issues,
reinstall the new minimal as a building base and go from there. I know it
is painfull but if you have the processing power it will not take too
long. Be carefull at the dependencies, and if possible read the mailing
list for hints on how to go over several issues. If you get stuck again,
send a mail and we will try to help.


regards,

Iulian

Post by Josmar Calin De Pierri
Hi Iulian.
Great hint!
I updated m4 (and some others; installed libffi and python) and my build
is progressing for some good time now ...
Thanks,
Josmar
Josmar Calin De Pierri
Analista de Suporte
COAMO - Campo Mourão/PR
Fone: (44) 3599-8298 ou Ramal Interno 8298
www.coamo.com.br
-----Original Message-----
Sent: Monday, November 25, 2013 6:18 AM
To: Josmar Calin De Pierri
Cc: T2 developers mailing list
Subject: Re: [t2] Build T2-TRUNK
Hi,
1. use configure to create a default configuration. give it any name you
want.
2. select minimal x86 in config and leave everything as it is.
3. use download -required to download all packages ( requires a fair
amount of coffee since the process is time consuming)
4. use ./scripts emerge-pkg -cfg yourconfig m4 to update your m4.
5. try rebuilding again.
the issue you are facing is that base minimal t2 is not in sync anymore
with the current updated package list. We are struggling to create an
updated 9.0 image but it seems we are not having enough time to finalize.
regards,
Iulian

[Josmar Calin De Pierri]

Iulian,

Suggestion accepted. I will build and reinstall a new minimal, so I
reconfigured and restarted the build.
I followed the mailing list archives (as you suggested) and could come
around the gawk failure as well as a few other minor glitches.

Now, however, I think I'm officially stuck again, with this:

== 16:21:31 =[1]=> Building base/sysvinit [2.88 9.0-trunk].
-> Parallel build using 2 jobs enabled.
-> Reading package config: package/base/sysvinit/sysvinit.conf
-> Preparing build in
src.sysvinit.default.20131125.162131.355.TCC-T2
-> Building. Writing output to $root/var/adm/logs/1-sysvinit.out
!> Clear (old) md5sums ...
!> Creating md5sum files ... done.
!> Creating package description ...
!> Making post-install adaptions.
!> Found shared files with other packages:
!> sbin/sulogin: sysvinit util-linux
!> usr/share/man/man8/sulogin.8: sysvinit util-linux
!> Due to previous errors.
== 11/25/13 16:21:37 =[1]=> Aborted building package sysvinit.
-> Unmounting loop mounts ...

I already applied the fix from Jan Rovins ( +var_append makeopt ' '
'SULOGINLIBS=-lcrypt LUTIL=-lutil ROOT=$root DISTRO=$DISTRO all' ), but
it seems to have no effect on the issue above.

I hope you have a remedy for this too ...
:)

Thanks,
Josmar


-----Original Message-----
From: ***@ns.pandcinfo.ro
[mailto:***@ns.pandcinfo.ro]
Sent: Monday, November 25, 2013 9:27 AM
To: Josmar Calin De Pierri
Cc: ***@ns.pandcinfo.ro; T2 developers mailing list
Subject: RE: [t2] Build T2-TRUNK

hi Josmar,

it would be good if you update perl also. It depends very much on what
you
intend to build. My advice would be to build a minimal and fix issues,
reinstall the new minimal as a building base and go from there. I know
it
is painfull but if you have the processing power it will not take too
long. Be carefull at the dependencies, and if possible read the mailing
list for hints on how to go over several issues. If you get stuck again,
send a mail and we will try to help.


regards,

Iulian

[i***@ns.pandcinfo.ro]

Hi Josmar,

the problem with this package is that it has a conflict with the package
util-linux. Actually the conflict is the sulogin utility and the
associated man page.

to fix this you have to go back a little and do the following:

1. find the util-linux configuration in packages, edit the configuration
util-linux.conf and append to the confopt argument '-disable-sulogin" if i
remember corectly. basically you have to disable the build of sulogin from
util-linux.
now you have 2 options:

2A. cleanup the build and start over ( time consuming but i recommend it)
2B. Delete the offending files from build ( the man and the utility) and
go forward.( sort of a test until you get everything fixed up)


this is not the first time you will encounter this kind of issue with
util-linux. it might happen a little bit later on while you are building
other packages.

Regards,

Iulian

Post by Josmar Calin De Pierri
Iulian,
Suggestion accepted. I will build and reinstall a new minimal, so I
reconfigured and restarted the build.
I followed the mailing list archives (as you suggested) and could come
around the gawk failure as well as a few other minor glitches.
== 16:21:31 =[1]=> Building base/sysvinit [2.88 9.0-trunk].
-> Parallel build using 2 jobs enabled.
-> Reading package config: package/base/sysvinit/sysvinit.conf
-> Preparing build in
src.sysvinit.default.20131125.162131.355.TCC-T2
-> Building. Writing output to $root/var/adm/logs/1-sysvinit.out
!> Clear (old) md5sums ...
!> Creating md5sum files ... done.
!> Creating package description ...
!> Making post-install adaptions.
!> sbin/sulogin: sysvinit util-linux
!> usr/share/man/man8/sulogin.8: sysvinit util-linux
!> Due to previous errors.
== 11/25/13 16:21:37 =[1]=> Aborted building package sysvinit.
-> Unmounting loop mounts ...
I already applied the fix from Jan Rovins ( +var_append makeopt ' '
'SULOGINLIBS=-lcrypt LUTIL=-lutil ROOT=$root DISTRO=$DISTRO all' ), but
it seems to have no effect on the issue above.
I hope you have a remedy for this too ...
:)
Thanks,
Josmar
-----Original Message-----
Sent: Monday, November 25, 2013 9:27 AM
To: Josmar Calin De Pierri
Subject: RE: [t2] Build T2-TRUNK
hi Josmar,
it would be good if you update perl also. It depends very much on what you
intend to build. My advice would be to build a minimal and fix issues,
reinstall the new minimal as a building base and go from there. I know it
is painfull but if you have the processing power it will not take too
long. Be carefull at the dependencies, and if possible read the mailing
list for hints on how to go over several issues. If you get stuck again,
send a mail and we will try to help.
regards,
Iulian

[Josmar Calin De Pierri]

Hi Iulian.

Since I found, near the end of util-linux.conf, this line:

pkgselected sysvinit && var_append extraconfopt ' '
'--disable-sulogin'

I'm wondering if I should: Remove it from there? Leave it there and put
another one on confopt? Put one on sysvinit.conf too? Put one on
sysvinit.conf but remove this one from util-linux.conf? Run to the
hills?



-----Original Message-----
From: ***@ns.pandcinfo.ro
[mailto:***@ns.pandcinfo.ro]
Sent: Monday, November 25, 2013 6:41 PM
To: Josmar Calin De Pierri
Cc: ***@ns.pandcinfo.ro; T2 developers mailing list
Subject: RE: [t2] Build T2-TRUNK

Hi Josmar,

the problem with this package is that it has a conflict with the package
util-linux. Actually the conflict is the sulogin utility and the
associated man page.

to fix this you have to go back a little and do the following:

1. find the util-linux configuration in packages, edit the configuration
util-linux.conf and append to the confopt argument '-disable-sulogin" if
i
remember corectly. basically you have to disable the build of sulogin
from
util-linux.
now you have 2 options:

2A. cleanup the build and start over ( time consuming but i recommend
it)
2B. Delete the offending files from build ( the man and the utility) and
go forward.( sort of a test until you get everything fixed up)


this is not the first time you will encounter this kind of issue with
util-linux. it might happen a little bit later on while you are building
other packages.

Regards,

Iulian

[i***@ns.pandcinfo.ro]

Hi Josmar,

I encountered the same issue as you did. The Q&D (Quick and Dirty)
solution was to force --disable-sulogin in confopt regardless of that
switch. it worked.

i did not have enough time to dig deeper into the scripts but the Q&D
approach did the trick. I will try to look into the script but it will
take some time since now i am really busy with RTAI building for the same
T2.

regards,

Iulian

Post by Josmar Calin De Pierri
Hi Iulian.
pkgselected sysvinit && var_append extraconfopt ' '
'--disable-sulogin'
I'm wondering if I should: Remove it from there? Leave it there and put
another one on confopt? Put one on sysvinit.conf too? Put one on
sysvinit.conf but remove this one from util-linux.conf? Run to the
hills?
-----Original Message-----
Sent: Monday, November 25, 2013 6:41 PM
To: Josmar Calin De Pierri
Subject: RE: [t2] Build T2-TRUNK
Hi Josmar,
the problem with this package is that it has a conflict with the package
util-linux. Actually the conflict is the sulogin utility and the
associated man page.
1. find the util-linux configuration in packages, edit the configuration
util-linux.conf and append to the confopt argument '-disable-sulogin" if i
remember corectly. basically you have to disable the build of sulogin from
util-linux.
2A. cleanup the build and start over ( time consuming but i recommend it)
2B. Delete the offending files from build ( the man and the utility) and
go forward.( sort of a test until you get everything fixed up)
this is not the first time you will encounter this kind of issue with
util-linux. it might happen a little bit later on while you are building
other packages.
Regards,
Iulian