T2 problems - part d) building

[scsijon]

try2, sorry
----------------

I think i may have ?sorted out the wpa_supplicant problem.

It has a patch that wants libnl-3.0 in the packages list directory, and
as I read the error file, the build is failing because the package is
not installed.

00-minimal doesn't have libnl set to be included to start with.

libnl in the mirror and packages list is version 3.2.24.

Does this mean that I should remove the patch or add libnl to 00-minimal?

----------

For portmap, it seems to want ld -lwrap, but I can't find any -lwrap in
any of the ld's I have access too, so i'm not sure where to go from here.

-----------

For aufs and aufs3, I need guidance please, can I use existing patches
or what, or do I build without patches?

thanks

so there are 4 problem packages left for a 00-minimal.
Also as i said in my last email, I wonder if 1-man is required as it
builds ok at 5-man?
However problems still exist with 5-aufs, 5-portmap and
5-wpa_supplicant, I have attached their error files.
As you said last time for aufs, I also wonder if it's time to move to
aufs3 as aufs2 has no support for 3.16 and later. It lost it for 3.x
kernels back in oct 2012 according to the coders website.
Is it worth me manually building these failed packages and building a T2
v9 from that or is it best to await fixes?
My next step would be the xorg build, from that it becomes puppy
integration.
As I said when I first started worrying you, I really want to build the
puppy packages that I will use, and make available, from a working T2
V9.0 Trunk system, so I then know that any problems that appear are most
likely puppy related and not T2 related.
I also noticed a number of packages are giving warnings about 'the use
of custmain is depreciated, please use hooks instead'. I remember that
linux-header was the first it appeared in during building but there were
quite a few others. Not sure if your interested.
regards

Hi,
as per earlier email I personally fixed some of those shared file
(coreutils, mktemp, …) some days ago.
1-man was trying to install files outside of the new system root.
aufs may need an update

I should have waited a few more minutes.....
The minimal build has completed building it's packages with these
final package errors, so it's not useable yet!
aufs
coreutils
mktemp
portmap
procps
shadow
wpa_supplicant
Interesting that man was ok under 5-man
All error logs from packages of this build are attached. I haven't
added the overall build logs due to size. I will if you need it, but
i'd like to fix a few first and rerun the build. And yes I shall have
a look when free later today for obvious problems I can fix.
regards
scsijon
-------- Original Message --------
Subject: Re: [t2] T2 problems - part d) building
Date: Fri, 15 Aug 2014 08:49:09 +1000
Update: I eventually got T2 V8 minimal loaded on one of my testing
computers by blowing everything away and starting it as a raw
(unpartitioned or formatted) system but even that wouldn't build
anything so I went another path by using another puppy called slacko and
are using it as a base to build from.
I am currently building a minimal and when it's working I intend to use
that for further building, but I need to get there first.
I have set the following config changes for now as it at least runs and
should give useable logs for fixing.
Generic
minimal
pkgdist
/root/t290minpkg
-
-
-Build system configuration
Continue on package error after stage 0 (toolchain)
Retry building broken packages
Do not try building packages if deps failed
Keep src dirs on build errors
Create debug information (xtrace) for builds
1- Shouldn't the Kernel-Headers package use the same version of the
kernel as the actual Kernel Package? It is in puppy and in fact they are
both created, plus a kernel-?.src package also needed with the header
package for additional driver package building, at the same time.
2- Building Generic>Toolchain
The package Man fails to build until 5-man.log. I have attached the
errorfile 1-man.err for your perusal. This is from a generic, toolchain
only build.
3- Building Generic>minimal
I shall send you the results from the minimal build when it's
completed
however I already have error logs showing for 1-man, 1-mktemp, 1-procps,
3-coreutils, 3-mktemp and 3-procps, so there are serious problems
here also.
regards
<1-man.err><1-mktemp.err><1-procps.err><3-coreutils.err><3-mktemp.err><5-aufs.err><3-procps.err><5-coreutils.err><5-mktemp.err><5-portmap.err><5-shadow.err><5-wpa_supplicant.err>-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to

[scsijon]

OK, adding libnl to the 00-minimal list fixes wpa_supplicant so I am
taking it that that is the fix for that one.

For portmap, I have tracked the -lwrap down to line 79 of the makefile,
however it seems to have come from the no-pathto-libwrap.patch which has
the comment For lib64 and cross builds, ... and rene's name against it.
As I an doing neither I wonder if I can remove this one, I shall try it
and see if that fixes things. Maybe I will need to add a libwrap
package, we will see.

regards

Post by scsijon
try2, sorry
----------------
I think i may have ?sorted out the wpa_supplicant problem.
It has a patch that wants libnl-3.0 in the packages list directory, and
as I read the error file, the build is failing because the package is
not installed.
00-minimal doesn't have libnl set to be included to start with.
libnl in the mirror and packages list is version 3.2.24.
Does this mean that I should remove the patch or add libnl to 00-minimal?
----------
For portmap, it seems to want ld -lwrap, but I can't find any -lwrap in
any of the ld's I have access too, so i'm not sure where to go from here.
-----------
For aufs and aufs3, I need guidance please, can I use existing patches
or what, or do I build without patches?
thanks

so there are 4 problem packages left for a 00-minimal.
Also as i said in my last email, I wonder if 1-man is required as it
builds ok at 5-man?
However problems still exist with 5-aufs, 5-portmap and
5-wpa_supplicant, I have attached their error files.
As you said last time for aufs, I also wonder if it's time to move to
aufs3 as aufs2 has no support for 3.16 and later. It lost it for 3.x
kernels back in oct 2012 according to the coders website.
Is it worth me manually building these failed packages and building a T2
v9 from that or is it best to await fixes?
My next step would be the xorg build, from that it becomes puppy
integration.
As I said when I first started worrying you, I really want to build the
puppy packages that I will use, and make available, from a working T2
V9.0 Trunk system, so I then know that any problems that appear are most
likely puppy related and not T2 related.
I also noticed a number of packages are giving warnings about 'the use
of custmain is depreciated, please use hooks instead'. I remember that
linux-header was the first it appeared in during building but there were
quite a few others. Not sure if your interested.
regards

Hi,
as per earlier email I personally fixed some of those shared file
(coreutils, mktemp, …) some days ago.
1-man was trying to install files outside of the new system root.
aufs may need an update

I should have waited a few more minutes.....
The minimal build has completed building it's packages with these
final package errors, so it's not useable yet!
aufs
coreutils
mktemp
portmap
procps
shadow
wpa_supplicant
Interesting that man was ok under 5-man
All error logs from packages of this build are attached. I haven't
added the overall build logs due to size. I will if you need it, but
i'd like to fix a few first and rerun the build. And yes I shall have
a look when free later today for obvious problems I can fix.
regards
scsijon
-------- Original Message --------
Subject: Re: [t2] T2 problems - part d) building
Date: Fri, 15 Aug 2014 08:49:09 +1000
Update: I eventually got T2 V8 minimal loaded on one of my testing
computers by blowing everything away and starting it as a raw
(unpartitioned or formatted) system but even that wouldn't build
anything so I went another path by using another puppy called slacko and
are using it as a base to build from.
I am currently building a minimal and when it's working I intend to use
that for further building, but I need to get there first.
I have set the following config changes for now as it at least runs and
should give useable logs for fixing.
Generic
minimal
pkgdist
/root/t290minpkg
-
-
-Build system configuration
Continue on package error after stage 0 (toolchain)
Retry building broken packages
Do not try building packages if deps failed
Keep src dirs on build errors
Create debug information (xtrace) for builds
1- Shouldn't the Kernel-Headers package use the same version of the
kernel as the actual Kernel Package? It is in puppy and in fact they are
both created, plus a kernel-?.src package also needed with the header
package for additional driver package building, at the same time.
2- Building Generic>Toolchain
The package Man fails to build until 5-man.log. I have attached the
errorfile 1-man.err for your perusal. This is from a generic, toolchain
only build.
3- Building Generic>minimal
I shall send you the results from the minimal build when it's
completed
however I already have error logs showing for 1-man, 1-mktemp, 1-procps,
3-coreutils, 3-mktemp and 3-procps, so there are serious problems
here also.
regards
<1-man.err><1-mktemp.err><1-procps.err><3-coreutils.err><3-mktemp.err><5-aufs.err><3-procps.err><5-coreutils.err><5-mktemp.err><5-portmap.err><5-shadow.err><5-wpa_supplicant.err>-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to

----------------------------------------------------------- If you wish
to unsubscribe from this mailing, send mail to

[scsijon]

OK, for portmap:

I found libwrap is part of tcp_wrappers and that is already installed so
it shouldn't be erroring. I don't know why it does.

I tracked further and found the building problem actually relates to the
perror.patch, removing that patch fixes the portmap build, although
there are a few warnings still.

that just leaves aufs3, and then i shall be able to build a base to
build the next stage (T2-xorg) from.

regards

Post by scsijon
OK, adding libnl to the 00-minimal list fixes wpa_supplicant so I am
taking it that that is the fix for that one.
For portmap, I have tracked the -lwrap down to line 79 of the makefile,
however it seems to have come from the no-pathto-libwrap.patch which has
the comment For lib64 and cross builds, ... and rene's name against it.
As I an doing neither I wonder if I can remove this one, I shall try it
and see if that fixes things. Maybe I will need to add a libwrap
package, we will see.
regards

Post by scsijon
try2, sorry
----------------
I think i may have ?sorted out the wpa_supplicant problem.
It has a patch that wants libnl-3.0 in the packages list directory, and
as I read the error file, the build is failing because the package is
not installed.
00-minimal doesn't have libnl set to be included to start with.
libnl in the mirror and packages list is version 3.2.24.
Does this mean that I should remove the patch or add libnl to 00-minimal?
----------
For portmap, it seems to want ld -lwrap, but I can't find any -lwrap in
any of the ld's I have access too, so i'm not sure where to go from here.
-----------
For aufs and aufs3, I need guidance please, can I use existing patches
or what, or do I build without patches?
thanks

so there are 4 problem packages left for a 00-minimal.
Also as i said in my last email, I wonder if 1-man is required as it
builds ok at 5-man?
However problems still exist with 5-aufs, 5-portmap and
5-wpa_supplicant, I have attached their error files.
As you said last time for aufs, I also wonder if it's time to move to
aufs3 as aufs2 has no support for 3.16 and later. It lost it for 3.x
kernels back in oct 2012 according to the coders website.
Is it worth me manually building these failed packages and building a T2
v9 from that or is it best to await fixes?
My next step would be the xorg build, from that it becomes puppy
integration.
As I said when I first started worrying you, I really want to build the
puppy packages that I will use, and make available, from a working T2
V9.0 Trunk system, so I then know that any problems that appear are most
likely puppy related and not T2 related.
I also noticed a number of packages are giving warnings about 'the use
of custmain is depreciated, please use hooks instead'. I remember that
linux-header was the first it appeared in during building but there were
quite a few others. Not sure if your interested.
regards

Hi,
as per earlier email I personally fixed some of those shared file
(coreutils, mktemp, …) some days ago.
1-man was trying to install files outside of the new system root.
aufs may need an update

I should have waited a few more minutes.....
The minimal build has completed building it's packages with these
final package errors, so it's not useable yet!
aufs
coreutils
mktemp
portmap
procps
shadow
wpa_supplicant
Interesting that man was ok under 5-man
All error logs from packages of this build are attached. I haven't
added the overall build logs due to size. I will if you need it, but
i'd like to fix a few first and rerun the build. And yes I shall have
a look when free later today for obvious problems I can fix.
regards
scsijon
-------- Original Message --------
Subject: Re: [t2] T2 problems - part d) building
Date: Fri, 15 Aug 2014 08:49:09 +1000
Update: I eventually got T2 V8 minimal loaded on one of my testing
computers by blowing everything away and starting it as a raw
(unpartitioned or formatted) system but even that wouldn't build
anything so I went another path by using another puppy called slacko and
are using it as a base to build from.
I am currently building a minimal and when it's working I intend to use
that for further building, but I need to get there first.
I have set the following config changes for now as it at least runs and
should give useable logs for fixing.
Generic
minimal
pkgdist
/root/t290minpkg
-
-
-Build system configuration
Continue on package error after stage 0 (toolchain)
Retry building broken packages
Do not try building packages if deps failed
Keep src dirs on build errors
Create debug information (xtrace) for builds
1- Shouldn't the Kernel-Headers package use the same version of the
kernel as the actual Kernel Package? It is in puppy and in fact they are
both created, plus a kernel-?.src package also needed with the header
package for additional driver package building, at the same time.
2- Building Generic>Toolchain
The package Man fails to build until 5-man.log. I have attached the
errorfile 1-man.err for your perusal. This is from a generic, toolchain
only build.
3- Building Generic>minimal
I shall send you the results from the minimal build when it's
completed
however I already have error logs showing for 1-man, 1-mktemp, 1-procps,
3-coreutils, 3-mktemp and 3-procps, so there are serious problems
here also.
regards
<1-man.err><1-mktemp.err><1-procps.err><3-coreutils.err><3-mktemp.err><5-aufs.err><3-procps.err><5-coreutils.err><5-mktemp.err><5-portmap.err><5-shadow.err><5-wpa_supplicant.err>-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to

----------------------------------------------------------- If you wish
to unsubscribe from this mailing, send mail to

----------------------------------------------------------- If you wish
to unsubscribe from this mailing, send mail to

[scsijon]

Blast!

1/ I updated with svn update to 43142 and it's broke something in the
build process as it stops at the start of stage2. Help would be appreciated.

A reminder that I am just building a 00-minimal x86-i486 at this stage.

errors as follows:
-------------------------

== 08/31/14 09:50:07 =[1]=> Finished building package sysfiles.

Building tools in build/.../TOOLCHAIN/tools.chroot:
-> Building tools.chroot/wrapper/cmd_wrapper.
scripts/core-functions.in: line 21: -t: command not found
./scripts/Build-Tools: line 114: $tmp: ambiguous redirect
chmod: missing operand after '+rx'
Try 'chmod --help' for more information.
mv: missing destination file operand after
'build/default-9.0-trunk-generic-x86-i486-linux/TOOLCHAIN/tools.chroot/wrapper/apxs'
Try 'mv --help' for more information.
scripts/core-functions.in: line 21: -t: command not found
./scripts/Build-Tools: line 114: $tmp: ambiguous redirect
chmod: missing operand after '+rx'
Try 'chmod --help' for more information.
mv: missing destination file operand after
'build/default-9.0-trunk-generic-x86-i486-linux/TOOLCHAIN/tools.chroot/wrapper/i486-t2-linux-gnu-cc'
Try 'mv --help' for more information.
scripts/core-functions.in: line 21: -t: command not found
./scripts/Build-Tools: line 114: $tmp: ambiguous redirect
chmod: missing operand after '+rx'
Try 'chmod --help' for more information.
mv: missing destination file operand after
'build/default-9.0-trunk-generic-x86-i486-linux/TOOLCHAIN/tools.chroot/wrapper/i486-t2-linux-gnu-gcc'
Try 'mv --help' for more information.
scripts/core-functions.in: line 21: -t: command not found
./scripts/Build-Tools: line 114: $tmp: ambiguous redirect
chmod: missing operand after '+rx'
Try 'chmod --help' for more information.
mv: missing destination file operand after
'build/default-9.0-trunk-generic-x86-i486-linux/TOOLCHAIN/tools.chroot/wrapper/i486-t2-linux-gnu-cpp'
Try 'mv --help' for more information.
scripts/core-functions.in: line 21: -t: command not found
./scripts/Build-Tools: line 114: $tmp: ambiguous redirect
chmod: missing operand after '+rx'
Try 'chmod --help' for more information.
mv: missing destination file operand after
'build/default-9.0-trunk-generic-x86-i486-linux/TOOLCHAIN/tools.chroot/wrapper/i486-t2-linux-gnu-c++'
Try 'mv --help' for more information.
scripts/core-functions.in: line 21: -t: command not found
./scripts/Build-Tools: line 114: $tmp: ambiguous redirect
chmod: missing operand after '+rx'
Try 'chmod --help' for more information.
mv: missing destination file operand after
'build/default-9.0-trunk-generic-x86-i486-linux/TOOLCHAIN/tools.chroot/wrapper/i486-t2-linux-gnu-g++'
Try 'mv --help' for more information.
scripts/core-functions.in: line 21: -t: command not found
./scripts/Build-Tools: line 114: $tmp: ambiguous redirect
chmod: missing operand after '+rx'
Try 'chmod --help' for more information.
mv: missing destination file operand after
'build/default-9.0-trunk-generic-x86-i486-linux/TOOLCHAIN/tools.chroot/wrapper/i486-t2-linux-gnu-kcc'
Try 'mv --help' for more information.
scripts/core-functions.in: line 21: -t: command not found
./scripts/Build-Tools: line 114: $tmp: ambiguous redirect
chmod: missing operand after '+rx'
Try 'chmod --help' for more information.
mv: missing destination file operand after
'build/default-9.0-trunk-generic-x86-i486-linux/TOOLCHAIN/tools.chroot/wrapper/cc'
Try 'mv --help' for more information.
scripts/core-functions.in: line 21: -t: command not found
./scripts/Build-Tools: line 114: $tmp: ambiguous redirect
chmod: missing operand after '+rx'
Try 'chmod --help' for more information.
mv: missing destination file operand after
'build/default-9.0-trunk-generic-x86-i486-linux/TOOLCHAIN/tools.chroot/wrapper/gcc'
Try 'mv --help' for more information.
scripts/core-functions.in: line 21: -t: command not found
./scripts/Build-Tools: line 114: $tmp: ambiguous redirect
chmod: missing operand after '+rx'
Try 'chmod --help' for more information.
mv: missing destination file operand after
'build/default-9.0-trunk-generic-x86-i486-linux/TOOLCHAIN/tools.chroot/wrapper/c++'
Try 'mv --help' for more information.
scripts/core-functions.in: line 21: -t: command not found
./scripts/Build-Tools: line 114: $tmp: ambiguous redirect
chmod: missing operand after '+rx'
Try 'chmod --help' for more information.
mv: missing destination file operand after
'build/default-9.0-trunk-generic-x86-i486-linux/TOOLCHAIN/tools.chroot/wrapper/g++'
Try 'mv --help' for more information.
scripts/core-functions.in: line 21: -t: command not found
./scripts/Build-Tools: line 114: $tmp: ambiguous redirect
chmod: missing operand after '+rx'
Try 'chmod --help' for more information.
mv: missing destination file operand after
'build/default-9.0-trunk-generic-x86-i486-linux/TOOLCHAIN/tools.chroot/wrapper/f77'
Try 'mv --help' for more information.
scripts/core-functions.in: line 21: -t: command not found
./scripts/Build-Tools: line 114: $tmp: ambiguous redirect
chmod: missing operand after '+rx'
Try 'chmod --help' for more information.
mv: missing destination file operand after
'build/default-9.0-trunk-generic-x86-i486-linux/TOOLCHAIN/tools.chroot/wrapper/gfortran'
Try 'mv --help' for more information.
scripts/core-functions.in: line 21: -t: command not found
./scripts/Build-Tools: line 114: $tmp: ambiguous redirect
chmod: missing operand after '+rx'
Try 'chmod --help' for more information.
mv: missing destination file operand after
'build/default-9.0-trunk-generic-x86-i486-linux/TOOLCHAIN/tools.chroot/wrapper/kcc'
Try 'mv --help' for more information.
scripts/core-functions.in: line 21: -t: command not found
./scripts/Build-Tools: line 114: $tmp: ambiguous redirect
chmod: missing operand after '+rx'
Try 'chmod --help' for more information.
mv: missing destination file operand after
'build/default-9.0-trunk-generic-x86-i486-linux/TOOLCHAIN/tools.chroot/wrapper/cpp'
Try 'mv --help' for more information.
scripts/core-functions.in: line 21: -t: command not found
./scripts/Build-Tools: line 114: $tmp: ambiguous redirect
chmod: missing operand after '+rx'
Try 'chmod --help' for more information.
mv: missing destination file operand after
'build/default-9.0-trunk-generic-x86-i486-linux/TOOLCHAIN/tools.chroot/wrapper/clang'
Try 'mv --help' for more information.
scripts/core-functions.in: line 21: -t: command not found
./scripts/Build-Tools: line 114: $tmp: ambiguous redirect
chmod: missing operand after '+rx'
Try 'chmod --help' for more information.
mv: missing destination file operand after
'build/default-9.0-trunk-generic-x86-i486-linux/TOOLCHAIN/tools.chroot/wrapper/clang++'
Try 'mv --help' for more information.
scripts/core-functions.in: line 21: -t: command not found
./scripts/Build-Tools: line 114: $tmp: ambiguous redirect
chmod: missing operand after '+rx'
Try 'chmod --help' for more information.
mv: missing destination file operand after
'build/default-9.0-trunk-generic-x86-i486-linux/TOOLCHAIN/tools.chroot/wrapper/cpp'
Try 'mv --help' for more information.
-> Building tools.chroot/wrapper/strip_wrapper.
-> Building tools.chroot/wrapper/{uname,arch}.
-> Building tools.chroot/wrapper/install_wrapper.
-> Building tools.chroot/bin/getdu.
-> Building tools.chroot/bin/getfiles.
-> Building tools.chroot/bin/fl_wrparse.
-> Building tools.chroot/bin/fl_stparse.
-> Building tools.chroot/lib/fl_wrapper.so.
scripts/core-functions.in: line 21: -t: command not found
cc: error: missing filename after '-o'
ldd: missing file arguments
Try `ldd --help' for more information.
!> The package build aborted with the following config error:
!> Unable to detect default libc for flwrapper
== 08/31/14 09:50:10 =[2]=> Aborted building package .

Package build ended abnormally!
!> Usually a package build creates either a *.log
!> or a *.err file. Neither the 1st nor the 2nd is
!> there. So I'm going to create a *.err file now
!> and abort the build process.
-> Unmounting loop mounts ...
#
-------------------------

2/ While I was at it i found an error in the glibc.desc file, last line
says:

#[D] 0 glibc-libidn-2.1810.1.tar.gz http://ftp.gnu.org/gnu/glibc/

should be

#[D] 0 glibc-libidn-2.10.1.tar.gz http://ftp.gnu.org/gnu/glibc/


3/ I will go back to my previous version for now, but I was having gross
problems with getting aufs3 to work, which was why I upgraded. I shall
try again.

regards

Post by scsijon
I found libwrap is part of tcp_wrappers and that is already installed so
it shouldn't be erroring. I don't know why it does.
I tracked further and found the building problem actually relates to the
perror.patch, removing that patch fixes the portmap build, although
there are a few warnings still.
that just leaves aufs3, and then i shall be able to build a base to
build the next stage (T2-xorg) from.
regards

Post by scsijon
OK, adding libnl to the 00-minimal list fixes wpa_supplicant so I am
taking it that that is the fix for that one.
For portmap, I have tracked the -lwrap down to line 79 of the makefile,
however it seems to have come from the no-pathto-libwrap.patch which has
the comment For lib64 and cross builds, ... and rene's name against it.
As I an doing neither I wonder if I can remove this one, I shall try it
and see if that fixes things. Maybe I will need to add a libwrap
package, we will see.
regards

Post by scsijon
try2, sorry
----------------
I think i may have ?sorted out the wpa_supplicant problem.
It has a patch that wants libnl-3.0 in the packages list directory, and
as I read the error file, the build is failing because the package is
not installed.
00-minimal doesn't have libnl set to be included to start with.
libnl in the mirror and packages list is version 3.2.24.
Does this mean that I should remove the patch or add libnl to 00-minimal?
----------
For portmap, it seems to want ld -lwrap, but I can't find any -lwrap in
any of the ld's I have access too, so i'm not sure where to go from here.
-----------
For aufs and aufs3, I need guidance please, can I use existing patches
or what, or do I build without patches?
thanks

so there are 4 problem packages left for a 00-minimal.
Also as i said in my last email, I wonder if 1-man is required as it
builds ok at 5-man?
However problems still exist with 5-aufs, 5-portmap and
5-wpa_supplicant, I have attached their error files.
As you said last time for aufs, I also wonder if it's time to move to
aufs3 as aufs2 has no support for 3.16 and later. It lost it for 3.x
kernels back in oct 2012 according to the coders website.
Is it worth me manually building these failed packages and building a T2
v9 from that or is it best to await fixes?
My next step would be the xorg build, from that it becomes puppy
integration.
As I said when I first started worrying you, I really want to build the
puppy packages that I will use, and make available, from a working T2
V9.0 Trunk system, so I then know that any problems that appear are most
likely puppy related and not T2 related.
I also noticed a number of packages are giving warnings about 'the use
of custmain is depreciated, please use hooks instead'. I remember that
linux-header was the first it appeared in during building but there were
quite a few others. Not sure if your interested.
regards

/cut

[ExactCODE]

Hi,

I added libel to the 00-minimal list for wpa_supplicant:

Committed revision 43169.

René

Post by scsijon
try2, sorry
----------------
I think i may have ?sorted out the wpa_supplicant problem.
It has a patch that wants libnl-3.0 in the packages list directory, and
as I read the error file, the build is failing because the package is
not installed.
00-minimal doesn't have libnl set to be included to start with.
libnl in the mirror and packages list is version 3.2.24.
Does this mean that I should remove the patch or add libnl to 00-minimal?
----------
For portmap, it seems to want ld -lwrap, but I can't find any -lwrap in
any of the ld's I have access too, so i'm not sure where to go from here.
-----------
For aufs and aufs3, I need guidance please, can I use existing patches
or what, or do I build without patches?
thanks

so there are 4 problem packages left for a 00-minimal.
Also as i said in my last email, I wonder if 1-man is required as it
builds ok at 5-man?
However problems still exist with 5-aufs, 5-portmap and
5-wpa_supplicant, I have attached their error files.
As you said last time for aufs, I also wonder if it's time to move to
aufs3 as aufs2 has no support for 3.16 and later. It lost it for 3.x
kernels back in oct 2012 according to the coders website.
Is it worth me manually building these failed packages and building a T2
v9 from that or is it best to await fixes?
My next step would be the xorg build, from that it becomes puppy
integration.
As I said when I first started worrying you, I really want to build the
puppy packages that I will use, and make available, from a working T2
V9.0 Trunk system, so I then know that any problems that appear are most
likely puppy related and not T2 related.
I also noticed a number of packages are giving warnings about 'the use
of custmain is depreciated, please use hooks instead'. I remember that
linux-header was the first it appeared in during building but there were
quite a few others. Not sure if your interested.
regards

Hi,
as per earlier email I personally fixed some of those shared file
(coreutils, mktemp, …) some days ago.
1-man was trying to install files outside of the new system root.
aufs may need an update

I should have waited a few more minutes.....
The minimal build has completed building it's packages with these
final package errors, so it's not useable yet!
aufs
coreutils
mktemp
portmap
procps
shadow
wpa_supplicant
Interesting that man was ok under 5-man
All error logs from packages of this build are attached. I haven't
added the overall build logs due to size. I will if you need it, but
i'd like to fix a few first and rerun the build. And yes I shall have
a look when free later today for obvious problems I can fix.
regards
scsijon
-------- Original Message --------
Subject: Re: [t2] T2 problems - part d) building
Date: Fri, 15 Aug 2014 08:49:09 +1000
Update: I eventually got T2 V8 minimal loaded on one of my testing
computers by blowing everything away and starting it as a raw
(unpartitioned or formatted) system but even that wouldn't build
anything so I went another path by using another puppy called slacko and
are using it as a base to build from.
I am currently building a minimal and when it's working I intend to use
that for further building, but I need to get there first.
I have set the following config changes for now as it at least runs and
should give useable logs for fixing.
Generic
minimal
pkgdist
/root/t290minpkg
-
-
-Build system configuration
Continue on package error after stage 0 (toolchain)
Retry building broken packages
Do not try building packages if deps failed
Keep src dirs on build errors
Create debug information (xtrace) for builds
1- Shouldn't the Kernel-Headers package use the same version of the
kernel as the actual Kernel Package? It is in puppy and in fact they are
both created, plus a kernel-?.src package also needed with the header
package for additional driver package building, at the same time.
2- Building Generic>Toolchain
The package Man fails to build until 5-man.log. I have attached the
errorfile 1-man.err for your perusal. This is from a generic, toolchain
only build.
3- Building Generic>minimal
I shall send you the results from the minimal build when it's
completed
however I already have error logs showing for 1-man, 1-mktemp, 1-procps,
3-coreutils, 3-mktemp and 3-procps, so there are serious problems
here also.
regards
<1-man.err><1-mktemp.err><1-procps.err><3-coreutils.err><3-mktemp.err><5-aufs.err><3-procps.err><5-coreutils.err><5-mktemp.err><5-portmap.err><5-shadow.err><5-wpa_supplicant.err>-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to

[scsijon]

This leaves just the 5-portmap and 5-aufs packages with problems

Haven't looked at Portmap yet. I will have a quick look later today in
case it's something simple to fix.

The aufs problem is a version problem as it needs aufs3 for kernel
3.16.x, aufs2 is out of date for kernel 3.9 +.
I shall have a go at working this out using packages/filesystems/aufs or
aufs2 as a template to create aufs3-util and aufs3. It should then only
need the list ammending, or do we also ammend aufs which has both
combined (maybe later) itself?

----------------------------------------------------

The stage 2 building problem has been sorted.

It has it's own thread if you want to follow.

------------------------------------------------------------
Thanks

Post by ExactCODE
Hi,
Committed revision 43169.
René

Post by scsijon
try2, sorry
----------------
I think i may have ?sorted out the wpa_supplicant problem.
It has a patch that wants libnl-3.0 in the packages list directory, and
as I read the error file, the build is failing because the package is
not installed.
00-minimal doesn't have libnl set to be included to start with.
libnl in the mirror and packages list is version 3.2.24.
Does this mean that I should remove the patch or add libnl to 00-minimal?
----------
For portmap, it seems to want ld -lwrap, but I can't find any -lwrap in
any of the ld's I have access too, so i'm not sure where to go from here.
-----------
For aufs and aufs3, I need guidance please, can I use existing patches
or what, or do I build without patches?
thanks

so there are 4 problem packages left for a 00-minimal.
Also as i said in my last email, I wonder if 1-man is required as it
builds ok at 5-man?
However problems still exist with 5-aufs, 5-portmap and
5-wpa_supplicant, I have attached their error files.
As you said last time for aufs, I also wonder if it's time to move to
aufs3 as aufs2 has no support for 3.16 and later. It lost it for 3.x
kernels back in oct 2012 according to the coders website.
Is it worth me manually building these failed packages and building a T2
v9 from that or is it best to await fixes?
My next step would be the xorg build, from that it becomes puppy
integration.
As I said when I first started worrying you, I really want to build the
puppy packages that I will use, and make available, from a working T2
V9.0 Trunk system, so I then know that any problems that appear are most
likely puppy related and not T2 related.
I also noticed a number of packages are giving warnings about 'the use
of custmain is depreciated, please use hooks instead'. I remember that
linux-header was the first it appeared in during building but there were
quite a few others. Not sure if your interested.
regards

Hi,
as per earlier email I personally fixed some of those shared file
(coreutils, mktemp, …) some days ago.
1-man was trying to install files outside of the new system root.
aufs may need an update

I should have waited a few more minutes.....
The minimal build has completed building it's packages with these
final package errors, so it's not useable yet!
aufs
coreutils
mktemp
portmap
procps
shadow
wpa_supplicant
Interesting that man was ok under 5-man
All error logs from packages of this build are attached. I haven't
added the overall build logs due to size. I will if you need it, but
i'd like to fix a few first and rerun the build. And yes I shall have
a look when free later today for obvious problems I can fix.
regards
scsijon
-------- Original Message --------
Subject: Re: [t2] T2 problems - part d) building
Date: Fri, 15 Aug 2014 08:49:09 +1000
Update: I eventually got T2 V8 minimal loaded on one of my testing
computers by blowing everything away and starting it as a raw
(unpartitioned or formatted) system but even that wouldn't build
anything so I went another path by using another puppy called slacko and
are using it as a base to build from.
I am currently building a minimal and when it's working I intend to use
that for further building, but I need to get there first.
I have set the following config changes for now as it at least runs and
should give useable logs for fixing.
Generic
minimal
pkgdist
/root/t290minpkg
-
-
-Build system configuration
Continue on package error after stage 0 (toolchain)
Retry building broken packages
Do not try building packages if deps failed
Keep src dirs on build errors
Create debug information (xtrace) for builds
1- Shouldn't the Kernel-Headers package use the same version of the
kernel as the actual Kernel Package? It is in puppy and in fact they are
both created, plus a kernel-?.src package also needed with the header
package for additional driver package building, at the same time.
2- Building Generic>Toolchain
The package Man fails to build until 5-man.log. I have attached the
errorfile 1-man.err for your perusal. This is from a generic, toolchain
only build.
3- Building Generic>minimal
I shall send you the results from the minimal build when it's
completed
however I already have error logs showing for 1-man, 1-mktemp, 1-procps,
3-coreutils, 3-mktemp and 3-procps, so there are serious problems
here also.
regards
<1-man.err><1-mktemp.err><1-procps.err><3-coreutils.err><3-mktemp.err><5-aufs.err><3-procps.err><5-coreutils.err><5-mktemp.err><5-portmap.err><5-shadow.err><5-wpa_supplicant.err>-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to

[Toan Pham]

​scsijon,

Have you considered using overlayfs from kernel 3.x.x. I tried it about a
year ago but it was unstable. A good thing about it is that it is
supported and maintained in the kernel.

[ExactCODE]

Hi

Post by Toan Pham
​scsijon,
Have you considered using overlayfs from kernel 3.x.x. I tried it about a year ago but it was unstable. A good thing about it is that it is supported and maintained in the kernel.

I do not think overlayfs made it into the stable kernel, yet, or did it?

[ExactCODE]

Hi,

yes, portmap failed here, too - maybe due to recent glibc update or something. I fixed it by updating it:

Committed revision 43204.

René

Post by scsijon
This leaves just the 5-portmap and 5-aufs packages with problems
Haven't looked at Portmap yet. I will have a quick look later today in case it's something simple to fix.
The aufs problem is a version problem as it needs aufs3 for kernel 3.16.x, aufs2 is out of date for kernel 3.9 +.
I shall have a go at working this out using packages/filesystems/aufs or aufs2 as a template to create aufs3-util and aufs3. It should then only need the list ammending, or do we also ammend aufs which has both combined (maybe later) itself?
----------------------------------------------------
The stage 2 building problem has been sorted.
It has it's own thread if you want to follow.
------------------------------------------------------------
Thanks

Post by ExactCODE
Hi,
Committed revision 43169.
René

Post by scsijon
try2, sorry
----------------
I think i may have ?sorted out the wpa_supplicant problem.
It has a patch that wants libnl-3.0 in the packages list directory, and
as I read the error file, the build is failing because the package is
not installed.
00-minimal doesn't have libnl set to be included to start with.
libnl in the mirror and packages list is version 3.2.24.
Does this mean that I should remove the patch or add libnl to 00-minimal?
----------
For portmap, it seems to want ld -lwrap, but I can't find any -lwrap in
any of the ld's I have access too, so i'm not sure where to go from here.
-----------
For aufs and aufs3, I need guidance please, can I use existing patches
or what, or do I build without patches?
thanks

so there are 4 problem packages left for a 00-minimal.
Also as i said in my last email, I wonder if 1-man is required as it
builds ok at 5-man?
However problems still exist with 5-aufs, 5-portmap and
5-wpa_supplicant, I have attached their error files.
As you said last time for aufs, I also wonder if it's time to move to
aufs3 as aufs2 has no support for 3.16 and later. It lost it for 3.x
kernels back in oct 2012 according to the coders website.
Is it worth me manually building these failed packages and building a T2
v9 from that or is it best to await fixes?
My next step would be the xorg build, from that it becomes puppy
integration.
As I said when I first started worrying you, I really want to build the
puppy packages that I will use, and make available, from a working T2
V9.0 Trunk system, so I then know that any problems that appear are most
likely puppy related and not T2 related.
I also noticed a number of packages are giving warnings about 'the use
of custmain is depreciated, please use hooks instead'. I remember that
linux-header was the first it appeared in during building but there were
quite a few others. Not sure if your interested.
regards

Hi,
as per earlier email I personally fixed some of those shared file
(coreutils, mktemp, …) some days ago.
1-man was trying to install files outside of the new system root.
aufs may need an update

I should have waited a few more minutes.....
The minimal build has completed building it's packages with these
final package errors, so it's not useable yet!
aufs
coreutils
mktemp
portmap
procps
shadow
wpa_supplicant
Interesting that man was ok under 5-man
All error logs from packages of this build are attached. I haven't
added the overall build logs due to size. I will if you need it, but
i'd like to fix a few first and rerun the build. And yes I shall have
a look when free later today for obvious problems I can fix.
regards
scsijon
-------- Original Message --------
Subject: Re: [t2] T2 problems - part d) building
Date: Fri, 15 Aug 2014 08:49:09 +1000
Update: I eventually got T2 V8 minimal loaded on one of my testing
computers by blowing everything away and starting it as a raw
(unpartitioned or formatted) system but even that wouldn't build
anything so I went another path by using another puppy called slacko and
are using it as a base to build from.
I am currently building a minimal and when it's working I intend to use
that for further building, but I need to get there first.
I have set the following config changes for now as it at least runs and
should give useable logs for fixing.
Generic
minimal
pkgdist
/root/t290minpkg
-
-
-Build system configuration
Continue on package error after stage 0 (toolchain)
Retry building broken packages
Do not try building packages if deps failed
Keep src dirs on build errors
Create debug information (xtrace) for builds
1- Shouldn't the Kernel-Headers package use the same version of the
kernel as the actual Kernel Package? It is in puppy and in fact they are
both created, plus a kernel-?.src package also needed with the header
package for additional driver package building, at the same time.
2- Building Generic>Toolchain
The package Man fails to build until 5-man.log. I have attached the
errorfile 1-man.err for your perusal. This is from a generic, toolchain
only build.
3- Building Generic>minimal
I shall send you the results from the minimal build when it's
completed
however I already have error logs showing for 1-man, 1-mktemp, 1-procps,
3-coreutils, 3-mktemp and 3-procps, so there are serious problems
here also.
regards
<1-man.err><1-mktemp.err><1-procps.err><3-coreutils.err><3-mktemp.err><5-aufs.err><3-procps.err><5-coreutils.err><5-mktemp.err><5-portmap.err><5-shadow.err><5-wpa_supplicant.err>-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to

[scsijon]

thanks for that, all I did to get it working was remove that one patch.
I shall try your update tonight and see if it still builds.

................................................

On the topic of aufs, i've had all sorts of trouble trying to get a
working aufs-3.16/aufs-util-3.16 pair to build though, I even went to
the main repositry. As it's the last problem I have for 00-minimal could
you have a look please, it's clearly above my level of competance. You
just need to remember that aufs-util must be built first otherwise aufs
itself fails to build properly.

And while were on aufs, I noticed that the aufs2 and aufs2-util packages
have the same build number. I ?think, if I am starting to understand
your build system correctly, this would cause aufs2 to attempt to be
built before aufs2-util and that is the wrong way around, aufs2 should
fail as this is, maybe a quick fix is to drop the build number by one
for aufs-util to ensure it is build first.

thanks for putting up with me and your work with T2
regards
jon

Post by ExactCODE
Hi,
Committed revision 43204.
René

Post by scsijon
This leaves just the 5-portmap and 5-aufs packages with problems
Haven't looked at Portmap yet. I will have a quick look later today in case it's something simple to fix.
The aufs problem is a version problem as it needs aufs3 for kernel 3.16.x, aufs2 is out of date for kernel 3.9 +.
I shall have a go at working this out using packages/filesystems/aufs or aufs2 as a template to create aufs3-util and aufs3. It should then only need the list ammending, or do we also ammend aufs which has both combined (maybe later) itself?
----------------------------------------------------
The stage 2 building problem has been sorted.
It has it's own thread if you want to follow.
------------------------------------------------------------
Thanks

Post by ExactCODE
Hi,
Committed revision 43169.
René

Post by scsijon
try2, sorry
----------------
I think i may have ?sorted out the wpa_supplicant problem.
It has a patch that wants libnl-3.0 in the packages list directory, and
as I read the error file, the build is failing because the package is
not installed.
00-minimal doesn't have libnl set to be included to start with.
libnl in the mirror and packages list is version 3.2.24.
Does this mean that I should remove the patch or add libnl to 00-minimal?
----------
For portmap, it seems to want ld -lwrap, but I can't find any -lwrap in
any of the ld's I have access too, so i'm not sure where to go from here.
-----------
For aufs and aufs3, I need guidance please, can I use existing patches
or what, or do I build without patches?
thanks

so there are 4 problem packages left for a 00-minimal.
Also as i said in my last email, I wonder if 1-man is required as it
builds ok at 5-man?
However problems still exist with 5-aufs, 5-portmap and
5-wpa_supplicant, I have attached their error files.
As you said last time for aufs, I also wonder if it's time to move to
aufs3 as aufs2 has no support for 3.16 and later. It lost it for 3.x
kernels back in oct 2012 according to the coders website.
Is it worth me manually building these failed packages and building a T2
v9 from that or is it best to await fixes?
My next step would be the xorg build, from that it becomes puppy
integration.
As I said when I first started worrying you, I really want to build the
puppy packages that I will use, and make available, from a working T2
V9.0 Trunk system, so I then know that any problems that appear are most
likely puppy related and not T2 related.
I also noticed a number of packages are giving warnings about 'the use
of custmain is depreciated, please use hooks instead'. I remember that
linux-header was the first it appeared in during building but there were
quite a few others. Not sure if your interested.
regards

Hi,
as per earlier email I personally fixed some of those shared file
(coreutils, mktemp, …) some days ago.
1-man was trying to install files outside of the new system root.
aufs may need an update

I should have waited a few more minutes.....
The minimal build has completed building it's packages with these
final package errors, so it's not useable yet!
aufs
coreutils
mktemp
portmap
procps
shadow
wpa_supplicant
Interesting that man was ok under 5-man
All error logs from packages of this build are attached. I haven't
added the overall build logs due to size. I will if you need it, but
i'd like to fix a few first and rerun the build. And yes I shall have
a look when free later today for obvious problems I can fix.
regards
scsijon
-------- Original Message --------
Subject: Re: [t2] T2 problems - part d) building
Date: Fri, 15 Aug 2014 08:49:09 +1000
Update: I eventually got T2 V8 minimal loaded on one of my testing
computers by blowing everything away and starting it as a raw
(unpartitioned or formatted) system but even that wouldn't build
anything so I went another path by using another puppy called slacko and
are using it as a base to build from.
I am currently building a minimal and when it's working I intend to use
that for further building, but I need to get there first.
I have set the following config changes for now as it at least runs and
should give useable logs for fixing.
Generic
minimal
pkgdist
/root/t290minpkg
-
-
-Build system configuration
Continue on package error after stage 0 (toolchain)
Retry building broken packages
Do not try building packages if deps failed
Keep src dirs on build errors
Create debug information (xtrace) for builds
1- Shouldn't the Kernel-Headers package use the same version of the
kernel as the actual Kernel Package? It is in puppy and in fact they are
both created, plus a kernel-?.src package also needed with the header
package for additional driver package building, at the same time.
2- Building Generic>Toolchain
The package Man fails to build until 5-man.log. I have attached the
errorfile 1-man.err for your perusal. This is from a generic, toolchain
only build.
3- Building Generic>minimal
I shall send you the results from the minimal build when it's
completed
however I already have error logs showing for 1-man, 1-mktemp, 1-procps,
3-coreutils, 3-mktemp and 3-procps, so there are serious problems
here also.
regards
<1-man.err><1-mktemp.err><1-procps.err><3-coreutils.err><3-mktemp.err><5-aufs.err><3-procps.err><5-coreutils.err><5-mktemp.err><5-portmap.err><5-shadow.err><5-wpa_supplicant.err>-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to