Building RC4 packages [ Was: Help with getting my CYGWIN build environment working]

[Wouter]

I am trying to get a build environment up and running on a Windows Vista box in order to see how building packages is done for Alt-F. I think I have most of it correct but when doing the ./mkinitramfs.sh it states for almost all packages that not all files are included and that they might not be OK. When I look into my build-dns323.log I see some messages that seem to be a problem but I don't know how to fix those. I attach the full log, but I will put some snippets below of where I think it goes wrong. Does anybody sees where this goes wrong? Am I missing some more packages? Thanks.


make[1]: Map '/home/Sofie/alt-f-read-only/build/toolchain_build_arm/uClibc-0.9.30.3' wordt binnengegaan
  MKDIR include/config
/bin/sh: /home/Sofie/alt-f-read-only/build/build_arm/staging_dir/usr/bin/arm-linux-uclibcgnueabi-gcc: No such file or directory
make[2]: /home/Sofie/alt-f-read-only/build/build_arm/staging_dir/usr/bin/arm-linux-uclibcgnueabi-gcc: Command not found
make[2]: /home/Sofie/alt-f-read-only/build/build_arm/staging_dir/usr/bin/arm-linux-uclibcgnueabi-gcc: Command not found
/bin/sh: /home/Sofie/alt-f-read-only/build/build_arm/staging_dir/usr/bin/arm-linux-uclibcgnueabi-gcc: No such file or directory
make[2]: /home/Sofie/alt-f-read-only/build/build_arm/staging_dir/usr/bin/arm-linux-uclibcgnueabi-gcc: Command not found
make[2]: /home/Sofie/alt-f-read-only/build/build_arm/staging_dir/usr/bin/arm-linux-uclibcgnueabi-gcc: Command not found

and a bit later in the log:

+ /usr/bin/make -j1 -C /home/Sofie/alt-f-read-only/build/toolchain_build_arm/uClibc-0.9.30.3 PREFIX=/home/Sofie/alt-f-read-only/build/toolchain_build_arm/uClibc_dev/ DEVEL_PREFIX=/usr/ RUNTIME_PREFIX=/home/Sofie/alt-f-read-only/build/toolchain_build_arm/uClibc_dev/ HOSTCC=/usr/bin/gcc headers install_headers
make[1]: Map '/home/Sofie/alt-f-read-only/build/toolchain_build_arm/uClibc-0.9.30.3' wordt binnengegaan
/bin/sh: /home/Sofie/alt-f-read-only/build/build_arm/staging_dir/usr/bin/arm-linux-uclibcgnueabi-gcc: No such file or directory
make[1]: /home/Sofie/alt-f-read-only/build/build_arm/staging_dir/usr/bin/arm-linux-uclibcgnueabi-gcc: Opdracht niet gevonden
make[1]: /home/Sofie/alt-f-read-only/build/build_arm/staging_dir/usr/bin/arm-linux-uclibcgnueabi-gcc: Opdracht niet gevonden
  MKDIR include/bits
  GEN include/bits/uClibc_config.h
/bin/sh: /home/Sofie/alt-f-read-only/build/build_arm/staging_dir/usr/bin/arm-linux-uclibcgnueabi-gcc: No such file or directory
make[2]: /home/Sofie/alt-f-read-only/build/build_arm/staging_dir/usr/bin/arm-linux-uclibcgnueabi-gcc: Command not found
make[2]: /home/Sofie/alt-f-read-only/build/build_arm/staging_dir/usr/bin/arm-linux-uclibcgnueabi-gcc: Command not found

and in the end:

/bin/sh: regel 1: Files/Common: No such file or directory
package/gmp/gmp.mk:79: recept voor doel '/home/Sofie/alt-f-read-only/build/toolchain_build_arm/gmp-4.2.4-host/.configured' is mislukt
make: *** [/home/Sofie/alt-f-read-only/build/toolchain_build_arm/gmp-4.2.4-host/.configured] Fout 127

[João Cardoso]

On Sunday, August 3, 2014 4:54:25 PM UTC+1, Wouter wrote:

I am trying to get a build environment up and running on a Windows Vista box in order to see how building packages is done for Alt-F. I think I have most of it correct but when doing the ./mkinitramfs.sh

It gives errors much before you are able to run ./mkiniramfs.sh. Instead of doing

make >& build-dns323.log 

do

make >& build-dns323.log && echo OK || echo FAILED

I have no cygwin experience, can't help.

The build system was tested on 4 different *linux* distributions, 2 from opensuse, Debian and  Ubunto.
My best suggestion: install one of these linux distros (most tested is openSUSE) under a virtual machine in MS-Win?

The "Files/Common: " must be a cygwin issue, never found it.
The cross toolchain was not built at all, gcc was not even downloaded... I'm afraid you are *far* from having it set.
If it wasn't 46MB I would post my own pkgs.log ;-)

luck
 

[Wouter]

Ok thanks for you answer, I took another approach and installed ubuntu on a spare machine I had. Now I managed to build the system so I started looking into the: How to create packages" Wiki. And quite soon some questions are arising.

First, I am unable to find the .config-base, .config-pkgs and .config-toolchain files When I look in the directory packages I find a config.in file, is this the confi-pkgs file? In the toolchain directory I am also able to find a config.in file.

When I use the config.in file for your

cp .config-pkgs .config command I get stuck at the ./mkprepare.sh command since it cannot be found.

Am I doing something wrong?

[João Cardoso]

On Monday, August 11, 2014 12:53:58 PM UTC+1, Wouter wrote:

Ok thanks for you answer, I took another approach and installed ubuntu on a spare machine I had. Now I managed to build the system so I started looking into the: How to create packages" Wiki. And quite soon some questions are arising.

First, I am unable to find the .config-base, .config-pkgs and .config-toolchain files When I look in the directory packages I find a config.in file, is this the confi-pkgs file? In the toolchain directory I am also able to find a config.in file.

OK, my fault.
I have just updated both the how to build RC4 and how to build packages wiki.
In short, '. exports [board]' does it all.
 

[Wouter]

Thanks that worked for the build part, but when I do

./mkpkgs -all 

I get: -bash: ./mkpkgs: No such file or directory 

Am I missing something or is this a diference between building packages for RC3 and RC4 again?

On Monday, August 11, 2014 3:50:26 PM UTC+2, João Cardoso wrote:

On Monday, August 11, 2014 12:53:58 PM UTC+1, Wouter wrote:

Ok thanks for you answer, I took another approach and installed ubuntu on a spare machine I had. Now I managed to build the system so I started looking into the: How to create packages" Wiki. And quite soon some questions are arising.

First, I am unable to find the .config-base, .config-pkgs and .config-toolchain files When I look in the directory packages I find a config.in file, is this the confi-pkgs file? In the toolchain directory I am also able to find a config.in file.

OK, my fault.
I have just updated both the how to build RC4 and how to build packages wiki.
In short, '. exports [board]' does it all.
 

[João Cardoso]

On Monday, August 11, 2014 10:58:56 PM UTC+1, Wouter wrote:

Thanks that worked for the build part, but when I do

./mkpkgs -all 

I get: -bash: ./mkpkgs: No such file or directory 

a typo, it's 'mkpkg.sh'

[Wouter]

Ok that command now did work but I got errors on the pkgs directory not being available. Creating it in the place where it said it was missing did not help. So I started building the RC04 firmware again. That went good. And then started again with the packages but now I get errors in the build phase. All refering to undefined xml references. I have libxml2-dev and libxml installed but the errors are remaining. I have attached the build log, can you see what i am doing wrong here? Thanks.

[João Cardoso]

On Tuesday, August 12, 2014 9:53:36 PM UTC+1, Wouter wrote:

Ok that command now did work but I got errors on the pkgs directory not being available. Creating it in the place where it said it was missing did not help. So I started building the RC04 firmware again.

hmmm, that's not as easy as it might seems.

What have you exactly done? 'rm -rf build' is the sure way to go (of course *I* don't need to do that). That preserves the SVN checkout and download directory but deletes (almost) everything else.

 

That went good. And then started again with the packages but now I get errors in the build phase. All refering to undefined xml references. I have libxml2-dev and libxml installed

The Alt-F version has to be build first. What if you have libxml2 version x.y installed in your system and Alt-F version is version y.x? That's what I call "buildroot leaking" into the build system, and can cause issues at runtime.

foomatic requires that libxml2-host to be built and installed first (at $HOSTDIR, to not contaminate your system). An incomplete install might be the reason for the build fail.

Assuming you start a fresh build:

-what does 'ls -ltr build/build_arm' outputs when the build fails?

-what is the output of 'echo $PATH'

-what is the output of 'ls -l $HOSTDIR/usr/lib/libxml2.*'

-what is your ubunto version? I succeed with an almost pristine Kubunto 10.04 installation.

[Wouter]

See inline for the answers.

On Wednesday, August 13, 2014 1:20:02 AM UTC+2, João Cardoso wrote:

On Tuesday, August 12, 2014 9:53:36 PM UTC+1, Wouter wrote:

Ok that command now did work but I got errors on the pkgs directory not being available. Creating it in the place where it said it was missing did not help. So I started building the RC04 firmware again.

hmmm, that's not as easy as it might seems.

What have you exactly done? 'rm -rf build' is the sure way to go (of course *I* don't need to do that). That preserves the SVN checkout and download directory but deletes (almost) everything else.

I deleted the whole alt-f-read-only directory and started from the beginning again.

 

That went good. And then started again with the packages but now I get errors in the build phase. All refering to undefined xml references. I have libxml2-dev and libxml installed

The Alt-F version has to be build first. What if you have libxml2 version x.y installed in your system and Alt-F version is version y.x? That's what I call "buildroot leaking" into the build system, and can cause issues at runtime.

foomatic requires that libxml2-host to be built and installed first (at $HOSTDIR, to not contaminate your system). An incomplete install might be the reason for the build fail.

Assuming you start a fresh build:

-what does 'ls -ltr build/build_arm' outputs when the build fails?

 drwxrwxr-x  3 wouter wouter  4096 Aug 12 14:30 host_dir
drwxrwxr-x 18 wouter wouter  4096 Aug 12 14:30 ncurses-5.9-host
drwxrwxr-x 12 wouter wouter  4096 Aug 12 14:30 texinfo-4.13a-host
drwxrwxr-x 22 wouter wouter  4096 Aug 12 14:43 libiconv-1.14
drwxrwxr-x 14 wouter wouter  4096 Aug 12 14:44 xz-5.0.5-host
drwxrwxr-x  2 wouter wouter  4096 Aug 12 14:50 alt-f-utils-0.1.7-host
drwxr-xr-x  8 wouter wouter  4096 Aug 12 14:51 fakeroot-1.9.5
drwxrwxr-x  7 wouter wouter  4096 Aug 12 14:51 fakeroot-1.9.5-host
drwxr-xr-x 14 wouter wouter  4096 Aug 12 14:51 zlib-1.2.8
drwxrwxr-x 22 wouter wouter  4096 Aug 12 14:53 openssl-1.0.1g
drwxrwxr-x  6 wouter wouter  4096 Aug 12 14:54 pkg-config-0.23-host
drwxrwxr-x  7 wouter wouter  4096 Aug 12 14:54 msmtp-1.4.31
drwxrwxr-x  3 wouter wouter  4096 Aug 12 14:55 devio-1.2-host
drwxr-xr-x  9 wouter wouter  4096 Aug 12 14:55 dnsmasq-2.68
drwxr-xr-x  6 wouter wouter  4096 Aug 12 14:55 dosfstools-3.0.24
drwxrwxr-x  5 wouter wouter 12288 Aug 12 14:56 dropbear-2014.63
drwxr-xr-x 18 wouter wouter  4096 Aug 12 14:56 e2fsprogs-1.41.14
drwxr-xr-x 17 wouter wouter  4096 Aug 12 14:57 ncurses-5.9
drwxrwxr-x  2 wouter wouter  4096 Aug 12 14:58 gptfdisk-0.8.6
drwxrwxr-x 12 wouter wouter  4096 Aug 12 14:58 inadyn-mt-02.24.38
drwxrwxr-x  3 wouter wouter  4096 Aug 12 14:58 ipkg-utils-050831-host
drwxrwxr-x 14 wouter wouter  4096 Aug 12 14:58 kexec-2.0.6
drwxr-xr-x  4 wouter wouter  4096 Aug 12 14:58 mdadm-3.1.5
drwxrwxr-x  5 wouter wouter  4096 Aug 12 14:58 mklibs-0.1.31-host
drwxr-xr-x  9 wouter wouter  4096 Aug 12 14:59 nfs-utils-1.2.9
drwxrwxr-x  8 wouter wouter  4096 Aug 12 14:59 ntfs-3g-2012.1.15
drwxrwxr-x 23 wouter wouter  4096 Aug 12 15:00 ntp-4.2.6p5
drwxrwxr-x  6 wouter wouter 20480 Aug 12 16:22 openssh-6.4p1
drwxr-xr-x  2 wouter wouter  4096 Aug 12 16:22 portmap-6.0.0
drwxrwxr-x 10 wouter wouter  4096 Aug 12 16:24 rsync-3.1.0
drwxrwxr-x 29 wouter wouter  4096 Aug 12 17:07 samba-small-3.5.22
drwxr-xr-x  2 wouter wouter  4096 Aug 12 17:12 sfdisk
drwxr-xr-x  9 wouter wouter  4096 Aug 12 17:13 smartmontools-6.2
drwxrwxr-x 14 wouter wouter  4096 Aug 12 17:13 zlib-1.2.8-host
drwxrwxr-x  4 wouter wouter  4096 Aug 12 17:13 squashfs-4.2-host
drwxrwxr-x  7 wouter wouter  4096 Aug 12 17:13 stunnel-4.56
drwxrwxr-x  3 wouter wouter  4096 Aug 12 17:13 uboot-mkimage-0.4-host
drwxr-x--x  8 wouter wouter  4096 Aug 12 17:13 vsftpd-3.0.2
drwxrwxr-x 11 wouter wouter  4096 Aug 12 17:14 wget-1.15
drwxrwxr-x  2 wouter wouter  4096 Aug 12 17:17 makedevs-host
drwxrwxr-x  3 wouter wouter  4096 Aug 12 17:17 genext2fs-1.4
drwxrwxr-x  2 wouter wouter  4096 Aug 12 17:17 at-3.1.14
drwxr-xr-x 10 wouter wouter  4096 Aug 12 17:40 gettext-0.16.1
drwxrwxr-x 10 wouter wouter  4096 Aug 12 17:43 gdb-6.8-target
drwxrwxr-x  2 wouter wouter  4096 Aug 12 17:44 gdbserver-6.8
drwxrwxr-x  6 wouter wouter  4096 Aug 12 17:47 gperf-3.0.3-host
drwxrwxr-x  7 wouter wouter  4096 Aug 12 17:47 file-5.04-host
drwxrwxr-x  7 wouter wouter  4096 Aug 12 17:47 file-5.04
drwxrwxr-x 20 wouter wouter  4096 Aug 12 17:48 a2ps-4.14
drwxrwxr-x 16 wouter wouter  4096 Aug 12 17:48 attr-2.4.47
drwxrwxr-x 16 wouter wouter  4096 Aug 12 17:48 acl-2.2.52
drwxrwxr-x  2 wouter wouter  4096 Aug 12 17:48 alt-f-utils-0.1.7
drwxrwxr-x 26 wouter wouter  4096 Aug 12 17:48 apr-1.4.6
drwxrwxr-x  7 wouter wouter  4096 Aug 12 17:48 cryptodev-1.5
drwxrwxr-x  6 wouter wouter  4096 Aug 12 17:49 readline-6.2
drwxrwxr-x  5 wouter wouter  4096 Aug 12 17:49 sqlite-3080200
drwxrwxr-x 13 wouter wouter  4096 Aug 12 17:50 expat-2.0.1
drwxrwxr-x 72 wouter wouter  4096 Aug 12 17:50 db-4.8.30
drwxrwxr-x 20 wouter wouter  4096 Aug 12 17:51 apr-util-1.5.1
drwxrwxr-x 15 wouter wouter 12288 Aug 12 17:52 libxml2-2.7.8-host
drwxrwxr-x 15 wouter wouter 12288 Aug 12 17:53 libxml2-2.7.8
drwxrwxr-x  8 wouter wouter  4096 Aug 12 17:53 pcre-8.20
drwxrwxr-x 11 wouter wouter  4096 Aug 12 17:54 libcurl-7.22.0
drwxrwxr-x  5 wouter wouter  4096 Aug 12 17:54 automatic-0.8.3
drwxrwxr-x  7 wouter wouter  4096 Aug 12 17:54 libdaemon-0.14
drwxrwxr-x  7 wouter wouter  4096 Aug 12 17:55 dbus-1.2.26
drwxrwxr-x 12 wouter wouter  4096 Aug 12 17:56 libglib2-2.20.4-host
drwxrwxr-x 12 wouter wouter  4096 Aug 12 17:58 libglib2-2.20.4
drwxrwxr-x 27 wouter wouter  4096 Aug 12 17:59 avahi-0.6.31
drwxrwxr-x 12 wouter wouter  4096 Aug 12 17:59 bash-4.2
drwxrwxr-x  4 wouter wouter  4096 Aug 12 17:59 bonniepp-1.03e
drwxrwxr-x  8 wouter wouter  4096 Aug 12 18:00 m4-1.4.9-host
drwxrwxr-x 13 wouter wouter  4096 Aug 12 18:00 libtool-1.5.24-host
drwxrwxr-x 10 wouter wouter  4096 Aug 12 18:00 autoconf-2.65-host
drwxrwxr-x  6 wouter wouter  4096 Aug 12 18:00 automake-1.10-host
drwxrwxr-x  2 wouter wouter  4096 Aug 12 18:00 stamps
drwxrwxr-x  7 wouter wouter  4096 Aug 12 18:00 bridge-1.5
drwxr-xr-x 34 wouter wouter  4096 Aug 12 18:00 busybox-1.20.2
drwxrwxr-x  2 wouter wouter  4096 Aug 12 18:00 bzip2-1.0.6
drwxrwxr-x  7 wouter wouter  4096 Aug 12 18:01 neon-0.29.6
drwxrwxr-x  7 wouter wouter  4096 Aug 12 18:01 cadaver-0.23.3
drwx------  3 wouter wouter  4096 Aug 12 18:01 gdbm-1.8.3
drwxr-x--- 18 wouter wouter  4096 Aug 12 18:05 Python-2.7.2
drwxr-xr-x  7 wouter wouter  4096 Aug 12 18:05 Cheetah-2.4.4
drwxrwxr-x  8 wouter wouter  4096 Aug 12 18:06 staging_dir
drwxr-xr-x 18 wouter wouter  4096 Aug 12 18:06 LVM2.2.02.88
drwxrwxr-x  7 wouter wouter  4096 Aug 12 18:06 libgpg-error-1.10
drwxr-xr-x 10 wouter wouter  4096 Aug 12 18:10 libgcrypt-1.5.0
drwxrwxr-x  8 wouter wouter  4096 Aug 12 18:11 popt-1.16
drwxrwxr-x 11 wouter wouter  4096 Aug 12 18:11 cryptsetup-1.4.1
drwxrwxr-x  9 wouter wouter  4096 Aug 12 18:11 libusb-0.1.12
drwxrwxr-x  7 wouter wouter  4096 Aug 12 18:11 libpng-1.2.38
drwxrwxr-x  4 wouter wouter 12288 Aug 12 18:11 jpeg-8c
drwxrwxr-x 12 wouter wouter  4096 Aug 12 18:12 tiff-3.9.4
drwxrwxr-x  9 wouter wouter  4096 Aug 12 18:13 libmcrypt-2.5.8
drwxrwxr-x 19 wouter wouter  4096 Aug 12 18:14 netsnmp-5.5.2
drwxrwxr-x 10 wouter wouter  4096 Aug 12 18:15 libexif-0.6.21
drwxrwxr-x 16 wouter wouter  4096 Aug 12 18:21 php-5.4.4
drwxrwxr-x 30 wouter wouter  4096 Aug 12 18:22 cups-1.4.8
drwxrwxr-x  7 wouter wouter  4096 Aug 12 18:23 davfs2-1.4.7
drwxr-xr-x  4 wouter wouter  4096 Aug 12 18:23 dialog-1.1-20070704
drwxrwxr-x  6 wouter wouter  4096 Aug 12 18:23 nano-2.2.4
drwxr-xr-x  2 wouter wouter  4096 Aug 12 18:24 em-4.0.15-lt
drwxr-xr-x  5 wouter wouter  4096 Aug 12 18:25 vim71
drwxrwxr-x  3 wouter wouter  4096 Aug 12 18:25 ethtool-3.7
drwxrwxr-x 10 wouter wouter  4096 Aug 12 18:26 flex-2.5.35
drwxrwxr-x 25 wouter wouter  4096 Aug 12 18:32 gs-8.71
drwxrwxr-x  5 wouter wouter  4096 Aug 12 18:32 foomatic-filters-4.0.4
drwxrwxr-x  4 wouter wouter  4096 Aug 12 18:33 foomatic-db-4.0-current
drwxr-xr-x  4 wouter wouter  4096 Aug 13 08:25 foomatic-db-engine-4.0.4

-what is the output of 'echo $PATH'

/home/wouter/alt-f-read-only/build/build_arm/host_dir/usr/bin:/home/wouter/alt-f-read-only/build//build_arm/staging_dir/usr/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/local/bin
 

-what is the output of 'ls -l $HOSTDIR/usr/lib/libxml2.*'

-rw-r--r-- 1 wouter wouter 2665710 Aug 12 17:52 /home/wouter/alt-f-read-only/build/build_arm/host_dir/usr/lib/libxml2.a
-rwxr-xr-x 1 wouter wouter    1049 Aug 12 17:52 /home/wouter/alt-f-read-only/build/build_arm/host_dir/usr/lib/libxml2.la
lrwxrwxrwx 1 wouter wouter      16 Aug 12 17:52 /home/wouter/alt-f-read-only/build/build_arm/host_dir/usr/lib/libxml2.so -> libxml2.so.2.7.8
lrwxrwxrwx 1 wouter wouter      16 Aug 12 17:52 /home/wouter/alt-f-read-only/build/build_arm/host_dir/usr/lib/libxml2.so.2 -> libxml2.so.2.7.8
-rwxr-xr-x 1 wouter wouter 2056611 Aug 12 17:52 /home/wouter/alt-f-read-only/build/build_arm/host_dir/usr/lib/libxml2.so.2.7.8
 

 

-what is your ubunto version? I succeed with an almost pristine Kubunto 10.04 installation.

Ubuntu 14.4 lts 64-bit. Nothing special installed on it.


What I'll do is start all over again and post the results of it here.

[Wouter]

• "rm -rf build"

• ". exports dns323"

No board configuration changes
No uClibc configuration found
No Busybox configuration found
No Kernel configuration found
#
# configuration written to .config
#
#
# make dependencies written to .auto.deps
# ATTENTION buildroot devels!
# See top of this file before playing with this auto-preprequisites!
#
if ! test -e .//dl; then mkdir -p .//dl; fi
mkdir -p /home/wouter/alt-f-read-only/build/project_build_arm/dns323/root
if ! [ -d "/home/wouter/alt-f-read-only/build/project_build_arm/dns323/root/bin" ]; then \
        if [ -d "target/generic/target_busybox_skeleton" ]; then \
            cp -fa target/generic/target_busybox_skeleton/* /home/wouter/alt-f-read-only/build/project_build_arm/dns323/root/; \
        fi; \
        if [ -d "" ]; then \
            toolchain/patch-kernel.sh /home/wouter/alt-f-read-only/build/project_build_arm/dns323/root / \*patch\*; \
        fi; \
        touch /home/wouter/alt-f-read-only/build/build_arm/staging_dir/.fakeroot.00000; \
    fi
find /home/wouter/alt-f-read-only/build/project_build_arm/dns323/root -type d -name CVS -print0 -o -name .svn -print0 | xargs -0 rm -rf
find /home/wouter/alt-f-read-only/build/project_build_arm/dns323/root -type f -name .empty -print0 | xargs -0 rm -rf
touch /home/wouter/alt-f-read-only/build/project_build_arm/dns323/.root
rm -rf /home/wouter/alt-f-read-only/build/project_build_arm/dns323/buildroot-config
mkdir -p /home/wouter/alt-f-read-only/build/project_build_arm/dns323
cp -dpRf package/config/buildroot-config /home/wouter/alt-f-read-only/build/project_build_arm/dns323/buildroot-config

Build ready for "dns323" at "/home/wouter/alt-f-read-only/build"

• make >& build-dns323.log && echo OK || echo FAIL

OK

• ./mkinitramfs.sh

Parallel mksquashfs: Using 2 processors
Creating 4.0 filesystem on rootfs.arm.sqall.xz, block size 262144.
[==============================================================-] 405/405 100%
Exportable Squashfs 4.0 filesystem, xz compressed, data block size 262144
    compressed data, compressed metadata, compressed fragments, compressed xattrs
    duplicates are removed
Filesystem size 6319.59 Kbytes (6.17 Mbytes)
    32.16% of uncompressed filesystem size (19647.88 Kbytes)
Inode table size 5330 bytes (5.21 Kbytes)
    22.48% of uncompressed inode table size (23706 bytes)
Directory table size 6348 bytes (6.20 Kbytes)
    52.51% of uncompressed directory table size (12090 bytes)
Number of duplicate files found 1
Number of inodes 690
Number of files 356
Number of fragments 31
Number of symbolic links  277
Number of device nodes 2
Number of fifo nodes 0
Number of socket nodes 0
Number of directories 55
Number of ids (unique uids + gids) 1
Number of uids 1
    root (0)
Number of gids 1
    root (0)

• ./mkfw.sh

Image Name:   Alt-F-0.1RC4, initrd
Created:      Wed Aug 13 09:54:18 2014
Image Type:   ARM Linux RAMDisk Image (uncompressed)
Data Size:    6471680 Bytes = 6320.00 kB = 6.17 MB
Load Address: 0x00800000
Entry Point:  0x00800000


___ DNS-323-rev-A1B1C1 ___
Image Name:   Alt-F-0.1RC4, kernel 3.10.32
Created:      Wed Aug 13 09:54:18 2014
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    1549304 Bytes = 1512.99 kB = 1.48 MB
Load Address: 0x00008000
Entry Point:  0x00008000
product_id=7
custom_id=1
model_id=1
sub_id=1
NewVersion=4
type=0
signature is "FrodoII"
kernel has 1549368 bytes
initramfs has 6471744 bytes
defaults has 0 bytes

Available kernel flash space: 23496 bytes
Available initramfs flash space: 16320 bytes

___ CH3SNAS ___
Image Name:   Alt-F-0.1RC4, kernel 3.10.32
Created:      Wed Aug 13 09:54:18 2014
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    1549304 Bytes = 1512.99 kB = 1.48 MB
Load Address: 0x00008000
Entry Point:  0x00008000
product_id=7
custom_id=2
model_id=1
sub_id=1
NewVersion=4
type=0
signature is "FrodoII"
kernel has 1549368 bytes
initramfs has 6471744 bytes
defaults has 0 bytes

Available kernel flash space: 23496 bytes
Available initramfs flash space: 16320 bytes

___ DUO-35LR ___
Image Name:   Alt-F-0.1RC4, kernel 3.10.32
Created:      Wed Aug 13 09:54:18 2014
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    1549304 Bytes = 1512.99 kB = 1.48 MB
Load Address: 0x00008000
Entry Point:  0x00008000
product_id=7
custom_id=3
model_id=1
sub_id=1
NewVersion=4
type=0
signature is "FrodoII"
kernel has 1549368 bytes
initramfs has 6471744 bytes
defaults has 0 bytes

Available kernel flash space: 23496 bytes
Available initramfs flash space: 16320 bytes
cp: target ‘/srv/tftpboot/’ is not a directory

So in this last step of building the firmware the last error is seen. When I look in the mkfw.sh in the very end it says the following:
# DNS-320/325 devel only
if true; then
    cp ${DESTD}/urootfs ${DESTD}/uImage /srv/tftpboot/
else
    rm kernel initramfs defaults ${DESTD}/urootfs ${DESTD}/uImage ${DESTD}/tImage
fi

Since I don't seem to be building for the 320/325 I don't think this is a real big issue. Can you confirm this, Joao?

When I do the checks as stated in the build RC04 wiki:

in $BINARIES, the kernel, "zImage", the root filesystem image, "rootfs.arm.ext2",
and the firmware files, "Alt-F-RC4-<model>.bin" are there.

in $ROOTFS I find the directory structure used to create the
root filesystem image.

in $KERNEL I find the built linux kernel.

So except for that last line all seems to be fine, so I continue to the how to create packages part:

. exports pkgs
No board configuration changes
Configuration for uClibc has changed. To examine differences use
   diff ./local/pkgs/uclibc-0.9.30.3.config $BLDDIR/toolchain_build_arm/uClibc-0.9.30.3/.config
Configuration for Busybox has changed. To examine differences use
   diff ./local/pkgs/busybox-1.20.2.config $BLDDIR/build_arm/busybox-1.20.2/.config
Configuration for Kernel has changed. To examine differences use
   diff ./local/pkgs/linux-3.10.32.config $BLDDIR/project_build_arm/dns323/linux-3.10.32/.config

Consider making "make saveconfig" or use ". exports -f pkgs" to ignore changes.
Continue using existing .config for dns323

doing the diff's as proposed gives the following results.

diff ./local/pkgs/uclibc-0.9.30.3.config $BLDDIR/toolchain_build_arm/uClibc-0.9.30.3/.config
4c4
< # Sun Mar 16 22:38:06 2014
---
> # Wed Aug 13 08:51:01 2014
74c74
< KERNEL_HEADERS="/home/jcard/Alt-F/alt-f/build/toolchain_build_arm/linux/include"
---
> KERNEL_HEADERS="/home/wouter/alt-f-read-only/build/toolchain_build_arm/linux/include"
231c231
< CROSS_COMPILER_PREFIX="/home/jcard/Alt-F/alt-f/build/build_arm/staging_dir/usr/bin/arm-linux-uclibcgnueabi-"
---
> CROSS_COMPILER_PREFIX="/home/wouter/alt-f-read-only/build/build_arm/staging_dir/usr/bin/arm-linux-uclibcgnueabi-"

diff ./local/pkgs/busybox-1.20.2.config $BLDDIR/build_arm/busybox-1.20.2/.config
4c4
< # Sun Jun 22 17:39:50 2014
---
> # Wed Aug 13 09:17:28 2014
90c90
< CONFIG_PREFIX="/home/jcard/Alt-F/alt-f/build/project_build_arm/dns323/root"
---
> CONFIG_PREFIX="/home/wouter/alt-f-read-only/build/project_build_arm/dns323/root"

diff ./local/pkgs/linux-3.10.32.config $BLDDIR/project_build_arm/dns323/linux-3.10.32/.config
101c101
< # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
---
> CONFIG_CC_OPTIMIZE_FOR_SIZE=y

 make saveconfig

tput: unknown terminal "xterm"
tput: unknown terminal "xterm"
mkdir -p ./local/dns323
cp .config ./local/dns323/dns323.config
if ! cmp -si $(head -n 4 /home/wouter/alt-f-read-only/build/build_arm/busybox-1.20.2/.config | wc -c):$(head -n 4 "./local/pkgs/busybox-1.20.2.config" | wc -c) /home/wouter/alt-f-read-only/build/build_arm/busybox-1.20.2/.config "./local/pkgs/busybox-1.20.2.config"; then \
        cp /home/wouter/alt-f-read-only/build/build_arm/busybox-1.20.2/.config "./local/pkgs/busybox-1.20.2.config"; \
    fi
if ! cmp -si $(head -n 4 /home/wouter/alt-f-read-only/build/toolchain_build_arm/uClibc-0.9.30.3/.config | wc -c):$(head -n 4 "./local/pkgs/uclibc-0.9.30.3.config" | wc -c) /home/wouter/alt-f-read-only/build/toolchain_build_arm/uClibc-0.9.30.3/.config "./local/pkgs/uclibc-0.9.30.3.config"; then \
        cp /home/wouter/alt-f-read-only/build/toolchain_build_arm/uClibc-0.9.30.3/.config "./local/pkgs/uclibc-0.9.30.3.config"; \
    fi
if ! cmp -si $(head -n 4 /home/wouter/alt-f-read-only/build/project_build_arm/dns323/linux-3.10.32/.config | wc -c):$(head -n 4 ./local/pkgs/linux-3.10.32.config | wc -c) /home/wouter/alt-f-read-only/build/project_build_arm/dns323/linux-3.10.32/.config ./local/pkgs/linux-3.10.32.config; then \
        cp /home/wouter/alt-f-read-only/build/project_build_arm/dns323/linux-3.10.32/.config ./local/pkgs/linux-3.10.32.config; \
    fi

make >& build.log && echo OK || echo FAIL
OK


./mkpkg.sh -all
Creating package a2ps...	skipping (not configured).
Creating package acl...	skipping (not configured).
Creating package alsa-lib...	skipping (not configured).
Creating package alsa-utils...	skipping (not configured).
Creating package alt-f-utils...	OK 
Creating package apr...	skipping (not configured).
Creating package apr-util...	skipping (not configured).
Creating package at...	OK 
Creating package attr...	skipping (not configured).
Creating package automatic...	skipping (not configured).
Creating package avahi...	skipping (not configured).
Creating package bash...	skipping (not configured).
Creating package bonniepp...	skipping (not configured).
Creating package bridge...	skipping (not configured).
Creating package bzip2...	skipping (not configured).
Creating package cadaver...	skipping (not configured).
Creating package cheetah...	skipping (not configured).
Creating package couchpotato2...	skipping (not configured).
Creating package couchpotato...	skipping (not configured).
Creating package cryptsetup...	skipping (not configured).
Creating package cups...	skipping (not configured).
Creating package davfs2...	skipping (not configured).
Creating package db...	skipping (not configured).
Creating package dbus...	skipping (not configured).
Creating package dev-bundle...	skipping (not configured).
Creating package dialog...	skipping (not configured).
Creating package dnsmasq...	OK 
Creating package dosfstools...	OK 
Creating package dropbear...	OK 
Creating package e2fsprogs...	OK 
Creating package ethtool...	skipping (not configured).
Creating package expat...	skipping (not configured).
Creating package ffmpeg...	skipping (not configured).
Creating package ffmpeg-libs...	skipping (not configured).
Creating package ffmpegthumbnailer...	skipping (not configured).
Creating package file...	skipping (not configured).
Creating package flac...	skipping (not configured).
Creating package flac-libs...	skipping (not configured).
Creating package flex...	skipping (not configured).
Creating package foomatic-db...	skipping (not configured).
Creating package foomatic-filters...	skipping (not configured).
Creating package forked-daapd...	skipping (not configured).
Creating package fuppes...	skipping (not configured).
Creating package gawk...	skipping (not configured).
Creating package gdb...	skipping (not configured).
Creating package gdbm...	skipping (not configured).
Creating package gettext...	skipping (not configured).
Creating package git...	skipping (not configured).
Creating package gnupg...	skipping (not configured).
Creating package gptfdisk...	FAIL (failed creating gptfdisk package (./usr/sbin/cgdisk not found))
Creating package gptfdisk-sgdisk...	OK (gptfdisk-sgdisk is a sub-package of gptfdisk)
Creating package groff...	skipping (not configured).
Creating package gs...	skipping (not configured).
Creating package hplip...	skipping (not configured).
Creating package htop...	skipping (not configured).
Creating package icu...	skipping (not configured).
Creating package inadyn-mt...	OK 
Creating package iperf...	skipping (not configured).
Creating package ipkg...	skipping (not configured).
Creating package ipsec-tools...	skipping (not configured).
Creating package iptables...	skipping (not configured).
Creating package iptraf...	skipping (not configured).
Creating package iscsitarget...	skipping (not configured).
Creating package jpeg...	skipping (not configured).
Creating package jpeg-libs...	skipping (not configured).
Creating package kernel-modules...	skipping (not configured).
Creating package kexec...	OK 
Creating package lame...	skipping (not configured).
Creating package libantlr...	skipping (not configured).
Creating package libavl...	skipping (not configured).
Creating package libconfuse...	skipping (not configured).
Creating package libcurl...	skipping (not configured).
Creating package libdaemon...	skipping (not configured).
Creating package libdlna...	skipping (not configured).
Creating package libevent2...	skipping (not configured).
Creating package libevent...	skipping (not configured).
Creating package libexif...	skipping (not configured).
Creating package libfuse...	skipping (not configured).
Creating package libgcrypt...	skipping (not configured).
Creating package libgd...	skipping (not configured).
Creating package libglib12...	skipping (not configured).
Creating package libglib2...	skipping (not configured).
Creating package libgpg-error...	skipping (not configured).
Creating package libiconv...	OK 
Creating package libid3tag...	skipping (not configured).
Creating package libmad...	skipping (not configured).
Creating package libmcrypt...	skipping (not configured).
Creating package libogg...	skipping (not configured).
Creating package libpar2...	skipping (not configured).
Creating package libpcap...	skipping (not configured).
Creating package libpng...	skipping (not configured).
Creating package libsigcpp...	skipping (not configured).
Creating package libtheora...	skipping (not configured).
Creating package libtirpc...	skipping (not configured).
Creating package libunistring...	skipping (not configured).
Creating package libupnp...	skipping (not configured).
Creating package libusb...	skipping (not configured).
Creating package libvorbis...	skipping (not configured).
Creating package libxml2...	skipping (not configured).
Creating package lighttpd...	skipping (not configured).
Creating package lsof...	skipping (not configured).
Creating package lvm2...	skipping (not configured).
Creating package lvm2-device-mapper...	skipping (not configured).
Creating package lzo...	skipping (not configured).
Creating package make...	skipping (not configured).
Creating package mc...	skipping (not configured).
Creating package mdadm...	OK 
Creating package mediatomb...	skipping (not configured).
Creating package minidlna...	skipping (not configured).
Creating package mp3gain...	skipping (not configured).
Creating package mpd...	skipping (not configured).
Creating package mplayer...	skipping (not configured).
Creating package msmtp...	OK 
Creating package mt-daapd...	skipping (not configured).
Creating package mtd-utils...	skipping (not configured).
Creating package mxml...	skipping (not configured).
Creating package nano...	skipping (not configured).
Creating package ncurses...	skipping (not configured).
Creating package ncurses-form...	skipping (not configured).
Creating package ncurses-menu...	skipping (not configured).
Creating package ncurses-panel...	skipping (not configured).
Creating package neon...	skipping (not configured).
Creating package netatalk2...	skipping (not configured).
Creating package netatalk...	skipping (not configured).
Creating package netcat...	skipping (not configured).
Creating package netperf...	skipping (not configured).
Creating package netsnmp...	skipping (not configured).
Creating package nfs-utils...	OK 
Creating package nmap...	skipping (not configured).
Creating package ntfs-3g...	OK 
Creating package ntfs-3g-ntfsprogs...	skipping (not configured).
Creating package ntp...	OK 
Creating package nuts...	skipping (not configured).
Creating package nzbget...	skipping (not configured).
Creating package nzbgetweb...	skipping (not configured).
Creating package openssh...	FAIL (failed creating openssh package (./etc/ssh/moduli not found))
Creating package openssh-sftp...	OK (openssh-sftp is a sub-package of openssh)
Creating package openssl...	OK 
Creating package openvpn...	skipping (not configured).
Creating package owncloud...	skipping (not configured).
Creating package par2cmdline...	skipping (not configured).
Creating package parted...	skipping (not configured).
Creating package pcre...	skipping (not configured).
Creating package perl...	skipping (not configured).
Creating package php...	skipping (not configured).
Creating package polipo...	skipping (not configured).
Creating package popt...	OK 
Creating package portmap...	OK 
Creating package pppd...	skipping (not configured).
Creating package pptp...	skipping (not configured).
Creating package pptpd...	skipping (not configured).
Creating package pyopenssl...	skipping (not configured).
Creating package python...	skipping (not configured).
Creating package quota-tools...	skipping (not configured).
Creating package readline...	skipping (not configured).
Creating package rsnapshot...	skipping (not configured).
Creating package rsync...	OK 
Creating package sabnzbd...	skipping (not configured).
Creating package samba...	skipping (not configured).
Creating package samba-doc...	skipping (not configured).
Creating package samba-extra...	skipping (not configured).
Creating package samba-modules...	skipping (not configured).
Creating package samba-small...	OK 
Creating package sane...	skipping (not configured).
Creating package screen...	skipping (not configured).
Creating package sfdisk...	OK 
Creating package sickbeard...	skipping (not configured).
Creating package smartmontools...	OK 
Creating package sqlite...	skipping (not configured).
Creating package sqlite-libs...	skipping (not configured).
Creating package strace...	skipping (not configured).
Creating package stunnel...	OK 
Creating package sudo...	skipping (not configured).
Creating package svn...	skipping (not configured).
Creating package sysstat...	skipping (not configured).
Creating package taglib...	skipping (not configured).
Creating package tcpdump...	skipping (not configured).
Creating package tcsh...	skipping (not configured).
Creating package tiff...	skipping (not configured).
Creating package transmission...	skipping (not configured).
Creating package twolame...	skipping (not configured).
Creating package uemacs...	skipping (not configured).
Creating package unrar...	skipping (not configured).
Creating package usbutils...	skipping (not configured).
Creating package ushare...	skipping (not configured).
Creating package vim...	skipping (not configured).
Creating package vsftpd...	OK 
Creating package wget...	OK 
Creating package yenc...	skipping (not configured).
Creating package zlib...	OK 
161 package(s) skipped.
2 package(s) FAILED.

This is how far I came untill now.27 packages created and a lot skipped because they were not configured. Any idea why the two openssh packages failed?

[João Cardoso]

On Wednesday, August 13, 2014 2:22:01 PM UTC+1, Wouter wrote:

• "rm -rf build"

• ". exports dns323"

So you are building for the dns323 board, the base firmware, not the full packages.

But that's OK, that's a start. As a matter of fact I use to start with the dns323, then continue with the 321, then the 325 and only finally pkgs. This way the build is reusing the previously compiled packages.

That's OK, it just copies some files to boot the dns325 board family using tftp.

When I do the checks as stated in the build RC04 wiki:

in $BINARIES, the kernel, "zImage", the root filesystem image, "rootfs.arm.ext2",
and the firmware files, "Alt-F-RC4-<model>.bin" are there.

in $ROOTFS I find the directory structure used to create the
root filesystem image.

in $KERNEL I find the built linux kernel.

So except for that last line all seems to be fine, so I continue to the how to create packages part:

. exports pkgs
No board configuration changes
Configuration for uClibc has changed. To examine differences use
   diff ./local/pkgs/uclibc-0.9.30.3.config $BLDDIR/toolchain_build_arm/uClibc-0.9.30.3/.config
Configuration for Busybox has changed. To examine differences use
   diff ./local/pkgs/busybox-1.20.2.config $BLDDIR/build_arm/busybox-1.20.2/.config
Configuration for Kernel has changed. To examine differences use
   diff ./local/pkgs/linux-3.10.32.config $BLDDIR/project_build_arm/dns323/linux-3.10.32/.config

Consider making "make saveconfig" or use ". exports -f pkgs" to ignore changes.
Continue using existing .config for dns323

notice the message: "Continue using existing .config for dns323" so the same config will be used, not the one for pkgs.

As you made no delibarated changes to the above config yourself you can/shall avoid the saving step:

"Consider making "make saveconfig" or use ". exports -f pkgs" to ignore changes.

Changes are essentially different build paths, just use   . exports -f pkgs

 

tput: unknown terminal "xterm"
tput: unknown terminal "xterm"
mkdir -p ./local/dns323
cp .config ./local/dns323/dns323.config
if ! cmp -si $(head -n 4 /home/wouter/alt-f-read-only/build/build_arm/busybox-1.20.2/.config | wc -c):$(head -n 4 "./local/pkgs/busybox-1.20.2.config" | wc -c) /home/wouter/alt-f-read-only/build/build_arm/busybox-1.20.2/.config "./local/pkgs/busybox-1.20.2.config"; then \
        cp /home/wouter/alt-f-read-only/build/build_arm/busybox-1.20.2/.config "./local/pkgs/busybox-1.20.2.config"; \
    fi
if ! cmp -si $(head -n 4 /home/wouter/alt-f-read-only/build/toolchain_build_arm/uClibc-0.9.30.3/.config | wc -c):$(head -n 4 "./local/pkgs/uclibc-0.9.30.3.config" | wc -c) /home/wouter/alt-f-read-only/build/toolchain_build_arm/uClibc-0.9.30.3/.config "./local/pkgs/uclibc-0.9.30.3.config"; then \
        cp /home/wouter/alt-f-read-only/build/toolchain_build_arm/uClibc-0.9.30.3/.config "./local/pkgs/uclibc-0.9.30.3.config"; \
    fi
if ! cmp -si $(head -n 4 /home/wouter/alt-f-read-only/build/project_build_arm/dns323/linux-3.10.32/.config | wc -c):$(head -n 4 ./local/pkgs/linux-3.10.32.config | wc -c) /home/wouter/alt-f-read-only/build/project_build_arm/dns323/linux-3.10.32/.config ./local/pkgs/linux-3.10.32.config; then \
        cp /home/wouter/alt-f-read-only/build/project_build_arm/dns323/linux-3.10.32/.config ./local/pkgs/linux-3.10.32.config; \
    fi

You are rebuilding for the dns323.

As the previous . exports pkgs fails, you have to repeat it again after a "saveconfig" or a "-f"

Those 27 packages are the ones needed for the base firmware, the dns323, you have to do . exports pkgs to build the full 161+27 packages

 

 Any idea why the two openssh packages failed?

Yes, but ignore that for now.

If you are going to try the 'pkgs' board next, you don't have to/should not perform the ./mkinitramfs.sh and ./mkfw.sh step, as 'pkgs' is a virtual board, no firmware can be build for it.

Also, it the pkgs build stops again at the foomatic-db package, I need the contents of

-build/build_arm/foomatic-db-engine-4.0.4 config.log,Makefile.in and Makefile

-build/build_arm/host_dir/usr/bin/xml2-config, 

-the build log from the first occurrence of foomatic-db-engine-4.0.4.tar.gz on it. If you try several builds, don't overwrite the *first* pkgs log, I need the configure step

Don't post/attach the full 47MB of the build log (or else make it available in Google Drive)

 

On Wednesday, August 13, 2014 8:43:28 AM UTC+2, Wouter wrote:

See inline for the answers.

On Wednesday, August 13, 2014 1:20:02 AM UTC+2, João Cardoso wrote:

On Tuesday, August 12, 2014 9:53:36 PM UTC+1, Wouter wrote:

Ok that command now did work but I got errors on the pkgs directory not being available. Creating it in the place where it said it was missing did not help. So I started building the RC04 firmware again.

hmmm, that's not as easy as it might seems.

What have you exactly done? 'rm -rf build' is the sure way to go (of course *I* don't need to do that). That preserves the SVN checkout and download directory but deletes (almost) everything else.

I deleted the whole alt-f-read-only directory and started from the beginning again.

 

That went good. And then started again with the packages but now I get errors in the build phase. All refering to undefined xml references. I have libxml2-dev and libxml installed

The Alt-F version has to be build first. What if you have libxml2 version x.y installed in your system and Alt-F version is version y.x? That's what I call "buildroot leaking" into the build system, and can cause issues at runtime.

foomatic requires that libxml2-host to be built and installed first (at $HOSTDIR, to not contaminate your system). An incomplete install might be the reason for the build fail.

Assuming you start a fresh build:

-what does 'ls -ltr build/build_arm' outputs when the build fails?

(...)

 

drwxrwxr-x 15 wouter wouter 12288 Aug 12 17:52 libxml2-2.7.8-host
drwxrwxr-x 15 wouter wouter 12288 Aug 12 17:53 libxml2-2.7.8

that'sOK

(...)

 

-what is the output of 'echo $PATH'

/home/wouter/alt-f-read-only/build/build_arm/host_dir/usr/bin:/home/wouter/alt-f-read-only/build//build_arm/staging_dir/usr/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/local/bin
 

That's OK

 

-what is the output of 'ls -l $HOSTDIR/usr/lib/libxml2.*'

-rw-r--r-- 1 wouter wouter 2665710 Aug 12 17:52 /home/wouter/alt-f-read-only/build/build_arm/host_dir/usr/lib/libxml2.a
-rwxr-xr-x 1 wouter wouter    1049 Aug 12 17:52 /home/wouter/alt-f-read-only/build/build_arm/host_dir/usr/lib/libxml2.la
lrwxrwxrwx 1 wouter wouter      16 Aug 12 17:52 /home/wouter/alt-f-read-only/build/build_arm/host_dir/usr/lib/libxml2.so -> libxml2.so.2.7.8
lrwxrwxrwx 1 wouter wouter      16 Aug 12 17:52 /home/wouter/alt-f-read-only/build/build_arm/host_dir/usr/lib/libxml2.so.2 -> libxml2.so.2.7.8
-rwxr-xr-x 1 wouter wouter 2056611 Aug 12 17:52 /home/wouter/alt-f-read-only/build/build_arm/host_dir/usr/lib/libxml2.so.2.7.8

 

 

Looks OK

[Wouter]

Ok I started over again:

• rm -rf build
• . exports pkgs

• make >& build.log && echo OK || echo FAIL

It now fails at the same foomatic package. Attached are the files as requested below (i have packed them since some of them were not allowed uncompressed therefore it is in the tar).

Also, it the pkgs build stops again at the foomatic-db package, I need the contents of

-build/build_arm/foomatic-db-engine-4.0.4 config.log,Makefile.in and Makefile

-build/build_arm/host_dir/usr/bin/xml2-config, 

-the build log from the first occurrence of foomatic-db-engine-4.0.4.tar.gz on it. If you try several builds, don't overwrite the *first* pkgs log, I need the configure step

Thanks

[João Cardoso]

On Friday, August 15, 2014 5:00:28 PM UTC+1, Wouter wrote:

Ok I started over again:

• rm -rf build
• . exports pkgs
• make >& build.log && echo OK || echo FAIL

It now fails at the same foomatic package. Attached are the files as requested below (i have packed them since some of them were not allowed uncompressed therefore it is in the tar).

Also, it the pkgs build stops again at the foomatic-db package, I need the contents of

-build/build_arm/foomatic-db-engine-4.0.4 config.log,Makefile.in and Makefile

-build/build_arm/host_dir/usr/bin/xml2-config, 

-the build log from the first occurrence of foomatic-db-engine-4.0.4.tar.gz on it. If you try several builds, don't overwrite the *first* pkgs log, I need the configure step

Thanks

Try editing build/build_arm/foomatic-db-engine-4.0.4/Makefile  around line 235 and adding $(XML_LIBS) at the line end:

was:

foomatic-perl-data: foomatic-perl-data.c
 $(CC) $(CFLAGS) $(XML_CFLAGS) $(XML_LIBS) -o foomatic-perl-data foomatic-perl-data.c

change to:

foomatic-perl-data: foomatic-perl-data.c
 $(CC) $(CFLAGS) $(XML_CFLAGS) $(XML_LIBS) -o foomatic-perl-data foomatic-perl-data.c $(XML_LIBS)

Than continue with a plain "make >& build2.log && ...'

Worked?

This should have been handled  by package/foomatic-db.mk, by the $(SED) in the $(FOOMATIC_DB_ENGINE_DIR)/.configured target

In any case, latter on the ./mkpkgs foomatic-db step might fail, as the printers database change almost daily and the list of printers will be outdated.

[Wouter]

Thanks I'll look into that tonight.

[Wouter]

Yes that worked but now it stops at the mt-daapd-0.2.4.2 package. I have attached the part of the build2.log from where it starts with the package.

Op maandag 18 augustus 2014 13:30:51 UTC+2 schreef Wouter:

[João Cardoso]

On Monday, August 18, 2014 10:00:20 PM UTC+1, Wouter wrote:

Yes that worked but now it stops at the mt-daapd-0.2.4.2 package. I have attached the part of the build2.log from where it starts with the package.

please apply the attached patch, then remove build/build_arm/mt-daapd-0.2.4.2, then do a normal make >& build3.log && ...

[Wouter]

Do I need to apply the patch in a specific directory?

[João Cardoso]

On Tuesday, August 19, 2014 5:18:37 PM UTC+1, Wouter wrote:

Do I need to apply the patch in a specific directory?

the directory where you execute the  'make' commands.

The patch top lines say:

Index: package/multimedia/mt-daapd/mt-daapd.mk

===================================================================

--- package/multimedia/mt-daapd/mt-daapd.mk     (revision 2975)

+++ package/multimedia/mt-daapd/mt-daapd.mk     (working copy)

when using the 'patch -i  mt-daapd-r3028.patch' it will search that (relative) path.

[Wouter]

Ok patching worked. Now the process stops at the pyopenssl package. See the part of the build log attached.

Op woensdag 20 augustus 2014 00:07:35 UTC+2 schreef João Cardoso:

[João Cardoso]

On Wednesday, August 20, 2014 11:27:06 AM UTC+1, Wouter wrote:

Ok patching worked. Now the process stops at the pyopenssl package. See the part of the build log attached.

Please try the attached patch.

If that is the issue, then the same needs to be done for pycurl and pycrypto, just let me know.

Thanks

[Wouter]

I applied the patch and it seems to work, now it fails at the yenc package. See attached last part of the build.log.

Op donderdag 21 augustus 2014 02:14:30 UTC+2 schreef João Cardoso:

[João Cardoso]

On Thursday, August 21, 2014 6:34:13 PM UTC+1, Wouter wrote:

I applied the patch and it seems to work, now it fails at the yenc package. See attached last part of the build.log.

Same issue as with pyopenssl, please try the attached patch (it all affects the cheetah package).

What is your system's make version? 

Thanks

[Wouter]

Make version is: GNU Make 3.81

When I do the make now it finished with an OK. When doing "./mkpkg -all" 2 packages fail: the foomatic one (as you predicted) and nano. For nano I am trying to find out why those html files are not in the expected place.


Op vrijdag 22 augustus 2014 00:10:50 UTC+2 schreef João Cardoso:

[João Cardoso]

On Friday, August 22, 2014 3:20:00 PM UTC+1, Wouter wrote:

Make version is: GNU Make 3.81

When I do the make now it finished with an OK.

Excelent.

So with the patches posted in this thread all RC4 packages can also be compiled under Ubuntu 14.4/64-bits.

But the first issue on footmatic-db you reported was solved by direct editing of the build makefile, whic means that if you ever remove the build dir and start fresh it will reappear. To solve that apply the attached patch.

 

When doing "./mkpkg -all" 2 packages fail: the foomatic one (as you predicted) and nano. For nano I am trying to find out why those html files are not in the expected place.

You might want to see if they was installed elsewhere by using './mkpkg.sh -debris', which will show you all files in the rootfs not belonging to any package.

'./mkpkg.sh -ls nano' shows you which package files was not found; './mkpkgs.sh -check nano' also does similar.

Packages control files are under 'ls ipkgfiles/nano.*'

 

[João Cardoso]

I took a look at nano, and it looks like confgure --datadir and --rootdatadir options direct where  files are installed.

On my build system it is by default /usr/share/nano, you might want to define those to 'configure', changing in package/editors/nano.mk

NANO_CONF_OPT = --program-prefix=''

to

NANO_CONF_OPT = --program-prefix='' --datadir=/usr/share

Although by default it should be OK, as configure uses

   --datarootdir=DIR       read-only arch.-independent data root [PREFIX/share]

  --datadir=DIR           read-only architecture-independent data [DATAROOTDIR]

[Wouter]

Thanks, I already checked in the file manager which files were missing and it seemed to be the html manual pages. I will try changing the nano.mk file to see whether that solves the issue.
Edit: that doesn't work, seems like the directory "man-html" is not created.
failed creating nano package (./usr/share/nano/man-html not found)

One note: I think './mkpkg.sh -ls nano' shows the installed files not the missing. './mkpkgs.sh -check nano' does show the missing files.

Also in ipkgfiles/nano.control file I added ncurses to "Depends" on the third line. Since I noticed by installing the package that it did not automatically included the ncurses package.


Op vrijdag 22 augustus 2014 23:11:50 UTC+2 schreef João Cardoso:

[João Cardoso]

On Wednesday, August 27, 2014 11:19:07 AM UTC+1, Wouter wrote:

Thanks, I already checked in the file manager which files were missing and it seemed to be the html manual pages. I will try changing the nano.mk file to see whether that solves the issue.
Edit: that doesn't work, seems like the directory "man-html" is not created.
failed creating nano package (./usr/share/nano/man-html not found)

Please attach the nano configure/build/install log and also config.log and doc/man/Makefile.

'configure' should generate doc/man/Makefile from doc/man/Makefile.in, using @GROFF_HTML_TRUE@htmlmandir = $(datadir)/nano/man-html, and defining htmldir to be /usr/share/nano/man-html.

It looks like it depends on 'groff' html support, so it might not be available on your system (config.log will show that. mine says

configure:8294: checking for HTML support in groff"

 and latter

GROFF_HTML_FALSE='#'

GROFF_HTML_TRUE=''

One note: I think './mkpkg.sh -ls nano' shows the installed files not the missing. './mkpkgs.sh -check nano' does show the missing files.

Also in ipkgfiles/nano.control file I added ncurses to "Depends" on the third line.

Thanks, fixed.

[Wouter]

You were right, I was missing the Groff package on my ubuntu system. After installing that package I tried again, after removing the nano dir in build_arm, I retried to build but that didn't work. I decided to start over again with a clean build directory. So removed the build dir and started over. Applied the foomatic-db patch. Then the build failed at package at-3.1.14, not sure why it failed. I just ran a build again with build1.log and then it finished ok. When I did a ./mkpkg -all only the foomatic-db package failed. So attached an updated nano package version 2.2.6. I haven't checked if it works yet. Before I can do that I need to look into creating a feed on my home network first.Tomorrow I go on holidays for two and a half weeks therefor that will be mid September the earliest when I will look into that. Thanks for you help.

Op donderdag 28 augustus 2014 23:09:07 UTC+2 schreef João Cardoso:

[João Cardoso]

On Friday, August 29, 2014 5:06:20 PM UTC+1, Wouter wrote:

You were right, I was missing the Groff package on my ubuntu system.

I fixed that by making groff-host a requirement for nano; that way groff will be built and installed in $HOSTDIR before nano being configured/built/installed. No need to install groff in the host.

After installing that package I tried again, after removing the nano dir in build_arm, I retried to build but that didn't work.

Removing the package build dir is not enough, it is stored in build/project_build_arm/pkgs/autotools-stamps that nano was installed. This is for autotargets.

For normal makefiles, a given binary installed in $ROOTFS is often the target, so it needs to be removed also.

Most often I do:

rm -rf build/build_arm/<pkg-dir> # or remove just the relevant .stamp files, such as .stamp-configured or .configured or .stamp-build or .build, or...

./mkpkgs -rm <pkg> # removes autotools-stamps for <pkg>, and also all <pkg> files from the rootfs

 

I decided to start over again with a clean build directory. So removed the build dir and started over. Applied the foomatic-db patch. Then the build failed at package at-3.1.14, not sure why it failed.

logs?

Someone reported that at-3.1.14 has disappeared from debian/pool

 

I just ran a build again with build1.log and then it finished ok. When I did a ./mkpkg -all only the foomatic-db package failed. So attached an updated nano package version 2.2.6. I haven't checked if it works yet. Before I can do that I need to look into creating a feed on my home network first.Tomorrow I go on holidays for two and a half weeks therefor that will be mid September the earliest when I will look into that. Thanks for you help.

Enjoy your holidays