Current 'next' won't build

Current 'next' won't build

[Matthias Fischer]

[-- Attachment #1: Type: text/plain, Size: 740 bytes --]

Hi,

First - all the best for chrismas and the new year. May the code be with
you! :-)

But..

Everytime I try, I'm getting the same error:

...
#Change KVER to Kernelversion
sed -e "s/KVER/4.14.86/g" -i /tmp/ROOTFILES
#Remove doubled files with tar/untar/tar to save space
tar -c --exclude='proc/*' --exclude='tmp/ROOTFILES' --exclude='#*'
--exclude='dev/pts/*' \
<->--exclude-from=/usr/src/config/rootfiles/core/127/exclude \
<->-C / --files-from=/tmp/ROOTFILES -f /ipfire.tar
tar: boot/boot.cmd: Cannot stat: No such file or directory
tar: boot/boot.scr: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
make: *** [core-updates:67: core/127] Error 2
...

Can anyone confirm?

Best,
Matthias

Re: Current 'next' won't build

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]

Hello,

Fixed by Arne:

  https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=f1f40274a095f0c5173a69767d9efa647e9f1a8a

Best,
-Michael

> On 23 Dec 2018, at 10:59, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> 
> Hi,
> 
> First - all the best for chrismas and the new year. May the code be with
> you! :-)
> 
> But..
> 
> Everytime I try, I'm getting the same error:
> 
> ...
> #Change KVER to Kernelversion
> sed -e "s/KVER/4.14.86/g" -i /tmp/ROOTFILES
> #Remove doubled files with tar/untar/tar to save space
> tar -c --exclude='proc/*' --exclude='tmp/ROOTFILES' --exclude='#*'
> --exclude='dev/pts/*' \
> <->--exclude-from=/usr/src/config/rootfiles/core/127/exclude \
> <->-C / --files-from=/tmp/ROOTFILES -f /ipfire.tar
> tar: boot/boot.cmd: Cannot stat: No such file or directory
> tar: boot/boot.scr: Cannot stat: No such file or directory
> tar: Exiting with failure status due to previous errors
> make: *** [core-updates:67: core/127] Error 2
> ...
> 
> Can anyone confirm?
> 
> Best,
> Matthias

Current 'next' won't build

[Matthias Fischer]

[-- Attachment #1: Type: text/plain, Size: 600 bytes --]

Hi,

today building current 'next' failed with the following error:

***SNIP***
...
# Compress root filesystem
# Reason for this tar+untar+tar is removing of entries listed two or
more in src/ROOTFILES
tar -c --exclude='#*' --exclude='proc/*' --exclude='dev/pts/*'
--exclude='tmp/ROOTFILES' \
    -C / --files-from=/tmp/ROOTFILES -f /ipfire.tar

    tar: You may not specify more than one '-Acdtrux', '--delete' or
'--test-label' option

    Try 'tar --help' or 'tar --usage' for more information.
    make: *** [cdrom:158: /usr/src/log/cdrom] Error 2
***SNAP***

Can anyone confirm?

Best,
Matthias

Re: Current 'next' won't build

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 793 bytes --]

For which architecture is this?

> On 8 Jun 2019, at 11:20, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> 
> Hi,
> 
> today building current 'next' failed with the following error:
> 
> ***SNIP***
> ...
> # Compress root filesystem
> # Reason for this tar+untar+tar is removing of entries listed two or
> more in src/ROOTFILES
> tar -c --exclude='#*' --exclude='proc/*' --exclude='dev/pts/*'
> --exclude='tmp/ROOTFILES' \
>    -C / --files-from=/tmp/ROOTFILES -f /ipfire.tar
> 
>    tar: You may not specify more than one '-Acdtrux', '--delete' or
> '--test-label' option
> 
>    Try 'tar --help' or 'tar --usage' for more information.
>    make: *** [cdrom:158: /usr/src/log/cdrom] Error 2
> ***SNAP***
> 
> Can anyone confirm?
> 
> Best,
> Matthias

Re: Current 'next' won't build

[Matthias Fischer]

[-- Attachment #1: Type: text/plain, Size: 114 bytes --]

On 08.06.2019 12:21, Michael Tremer wrote:
> For which architecture is this?

Sorry, forgot: i586

Best,
Matthias

Re: Current 'next' won't build

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 255 bytes --]

Can you pull and try again?

> On 8 Jun 2019, at 11:33, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> 
> On 08.06.2019 12:21, Michael Tremer wrote:
>> For which architecture is this?
> 
> Sorry, forgot: i586
> 
> Best,
> Matthias

Re: Current 'next' won't build

[Matthias Fischer]

[-- Attachment #1: Type: text/plain, Size: 188 bytes --]

On 08.06.2019 12:35, Michael Tremer wrote:
> Can you pull and try again?

Now it builds. Thanks!

Terrific.

I was looking for something like that, but didn't find it...

Best,

Matthias

Current 'next' won't build

[Matthias Fischer]

[-- Attachment #1: Type: text/plain, Size: 2549 bytes --]

Hi!

While testing 'dhcp 4.4.1', current 'next' won't build.

While 'building packages' it throws a bunch of errors in '_build_packagaes.log':

***SNIP***
...
# Create configuration
mkdir -pv /install/harddisk/boot/grub
chroot /install/harddisk grub-mkconfig -o /boot/grub/grub.cfg
ERROR: ld.so: object '/tools_i586/lib/libpakfire_preload.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/tools_i586/lib/libpakfire_preload.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
...
device-mapper: table ioctl on  failed: No such device or address
...
ERROR: ld.so: object '/tools_i586/lib/libpakfire_preload.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
...
# Install GRUB
grub-install --force --recheck --no-floppy --target=i386-pc \
	--root-directory=/install/harddisk /dev/loop0
device-mapper: table ioctl on  failed: No such device or address
device-mapper: table ioctl on  failed: No such device or address
...
***SNAP***

It ends with:

***SNIP***
...
# Add padding at the end of the image (to fix alignment issues if the image is
# not copied to a block device)
dd if=/dev/zero bs=1M count=100  >> /install/images/image.img
100+0 records in
100+0 records out
104857600 bytes (105 MB, 100 MiB) copied, 0.897412 s, 117 MB/s
# Compress Image
pigz -f9 < /install/images/image.img > /install/images/ipfire-2.19.1gb-ext4-scon.i586-full-core121.img.gz
rm -rf /install/images/image.img /install/harddisk
mv: cannot stat '/home/matz/ipfire-2.x/build/install/images/*.tgz': No such file or directory
mv: cannot stat '/home/matz/ipfire-2.x/build/install/images/*.bz2': No such file or directory
Apr 29 11:34:18: Building core-updates + cd /usr/src/lfs
+ MAKETUNING=-j9
+ make -f core-updates LFS_BASEDIR=/usr/src install
rm -rf /install/packages/package
mkdir -p /install/packages/package
eval $(cat /usr/src/config/rootfiles/core/121/meta)
#Generate ROOTFILES from filelists
BUILD_ARCH=i586 BUILDTARGET=i586-pc-linux-gnu KVER=3.14.79 \
	/usr/src/src/scripts/archive.files \
	/usr/src/config/rootfiles/core/121/filelists \
	/usr/src/config/rootfiles/core/121/files \
	/usr/src/config/rootfiles/core/121/files.i586 \
	> /tmp/ROOTFILES.tmp
#remove excluded files from ROOTFILES
grep -f /usr/src/config/rootfiles/core/121/exclude -v /tmp/ROOTFILES.tmp > /tmp/ROOTFILES
make: *** [core-updates:60: core/121] Error 1
...
***SNAP***

Anyone else? Any hints?

Best,
Matthias

Re: Current 'next' won't build

[Peter Müller]

[-- Attachment #1: Type: text/plain, Size: 3013 bytes --]

Hello,

I can confirm the second error:
> mv: cannot stat '/home/matz/ipfire-2.x/build/install/images/*.tgz': No such file or directory
> mv: cannot stat '/home/matz/ipfire-2.x/build/install/images/*.bz2': No such file or directory

It also appears here. Grub, however, seems builds fine.

Best regards,
Peter Müller

> Hi!
> 
> While testing 'dhcp 4.4.1', current 'next' won't build.
> 
> While 'building packages' it throws a bunch of errors in '_build_packagaes.log':
> 
> ***SNIP***
> ...
> # Create configuration
> mkdir -pv /install/harddisk/boot/grub
> chroot /install/harddisk grub-mkconfig -o /boot/grub/grub.cfg
> ERROR: ld.so: object '/tools_i586/lib/libpakfire_preload.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
> ERROR: ld.so: object '/tools_i586/lib/libpakfire_preload.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
> ...
> device-mapper: table ioctl on  failed: No such device or address
> ...
> ERROR: ld.so: object '/tools_i586/lib/libpakfire_preload.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
> ...
> # Install GRUB
> grub-install --force --recheck --no-floppy --target=i386-pc \
> 	--root-directory=/install/harddisk /dev/loop0
> device-mapper: table ioctl on  failed: No such device or address
> device-mapper: table ioctl on  failed: No such device or address
> ...
> ***SNAP***
> 
> It ends with:
> 
> ***SNIP***
> ...
> # Add padding at the end of the image (to fix alignment issues if the image is
> # not copied to a block device)
> dd if=/dev/zero bs=1M count=100  >> /install/images/image.img
> 100+0 records in
> 100+0 records out
> 104857600 bytes (105 MB, 100 MiB) copied, 0.897412 s, 117 MB/s
> # Compress Image
> pigz -f9 < /install/images/image.img > /install/images/ipfire-2.19.1gb-ext4-scon.i586-full-core121.img.gz
> rm -rf /install/images/image.img /install/harddisk
> mv: cannot stat '/home/matz/ipfire-2.x/build/install/images/*.tgz': No such file or directory
> mv: cannot stat '/home/matz/ipfire-2.x/build/install/images/*.bz2': No such file or directory
> Apr 29 11:34:18: Building core-updates + cd /usr/src/lfs
> + MAKETUNING=-j9
> + make -f core-updates LFS_BASEDIR=/usr/src install
> rm -rf /install/packages/package
> mkdir -p /install/packages/package
> eval $(cat /usr/src/config/rootfiles/core/121/meta)
> #Generate ROOTFILES from filelists
> BUILD_ARCH=i586 BUILDTARGET=i586-pc-linux-gnu KVER=3.14.79 \
> 	/usr/src/src/scripts/archive.files \
> 	/usr/src/config/rootfiles/core/121/filelists \
> 	/usr/src/config/rootfiles/core/121/files \
> 	/usr/src/config/rootfiles/core/121/files.i586 \
> 	> /tmp/ROOTFILES.tmp
> #remove excluded files from ROOTFILES
> grep -f /usr/src/config/rootfiles/core/121/exclude -v /tmp/ROOTFILES.tmp > /tmp/ROOTFILES
> make: *** [core-updates:60: core/121] Error 1
> ...
> ***SNAP***
> 
> Anyone else? Any hints?
> 
> Best,
> Matthias
> 


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Current 'next' won't build

[Matthias Fischer]

[-- Attachment #1: Type: text/plain, Size: 543 bytes --]

Hi,

Current 'next' always gives me:

***SNIP***
...
    tar -c -C / --files-from=/tmp/ROOTFILES \
    -f /ipfire.tar --exclude='#*' --exclude='dev/pts/*' \
    --exclude='proc/*' --exclude='tmp/ROOTFILES'
    rm -f /tmp/ROOTFILES
    tar -x -C /tmp -f /ipfire.tar
    rm -f /ipfire.tar
    cd /tmp && tar  cf /install/cdrom/distro.img --xz * && rm -rf *
    xz: (stdin): Cannot allocate memory
    make: *** [cdrom:75: /usr/src/log/cdrom] Error 141
...
***SNAP***

Building on Ubuntu 16.04.3 LTS / 32bit.

Can anyone confirm?

Best,
Matthias

Re: Current 'next' won't build

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 988 bytes --]

Hi,

how much memory does your build system have?

I changed the compression algorithm and it will now use up to ~370MB of
memory (probably times the number of processor cores you have).

If that is too much, we need to change this to something lower again.
The benefit right now is, that the ISO image is about 15 MB smaller.

-Michael

On Wed, 2017-10-18 at 04:39 +0200, Matthias Fischer wrote:
> Hi,
> 
> Current 'next' always gives me:
> 
> ***SNIP***
> ...
>     tar -c -C / --files-from=/tmp/ROOTFILES \
>     -f /ipfire.tar --exclude='#*' --exclude='dev/pts/*' \
>     --exclude='proc/*' --exclude='tmp/ROOTFILES'
>     rm -f /tmp/ROOTFILES
>     tar -x -C /tmp -f /ipfire.tar
>     rm -f /ipfire.tar
>     cd /tmp && tar  cf /install/cdrom/distro.img --xz * && rm -rf *
>     xz: (stdin): Cannot allocate memory
>     make: *** [cdrom:75: /usr/src/log/cdrom] Error 141
> ...
> ***SNAP***
> 
> Building on Ubuntu 16.04.3 LTS / 32bit.
> 
> Can anyone confirm?
> 
> Best,
> Matthias

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: Current 'next' won't build

[Matthias Fischer]

[-- Attachment #1: Type: text/plain, Size: 2004 bytes --]

Hi,

On 18.10.2017 04:39, Michael Tremer wrote:
> Hi,
> 
> how much memory does your build system have?

8GB, with 32bit Ubuntu.

'top' says:

KiB Mem :  7973868 total,  7739960 free,    44100 used,   189808 buff/cache
KiB Swap:  1046524 total,  1046524 free,        0 used.  7347712 avail Mem
 
> I changed the compression algorithm and it will now use up to ~370MB of
> memory (probably times the number of processor cores you have).

'lscpu' says:

Architecture:          i686
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                8
On-line CPU(s) list:   0-7
Thread(s) per core:    2
Core(s) per socket:    4
Socket(s):             1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 42
Model name:            Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
Stepping:              7
CPU MHz:               1600.921
CPU max MHz:           3800.0000
CPU min MHz:           1600.0000
BogoMIPS:              6784.18
Virtualisation:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              8192K

> If that is too much, we need to change this to something lower again.
> The benefit right now is, that the ISO image is about 15 MB smaller.

Anything I could test?

Best,
Matthias

> -Michael
> 
> On Wed, 2017-10-18 at 04:39 +0200, Matthias Fischer wrote:
>> Hi,
>> 
>> Current 'next' always gives me:
>> 
>> ***SNIP***
>> ...
>>     tar -c -C / --files-from=/tmp/ROOTFILES \
>>     -f /ipfire.tar --exclude='#*' --exclude='dev/pts/*' \
>>     --exclude='proc/*' --exclude='tmp/ROOTFILES'
>>     rm -f /tmp/ROOTFILES
>>     tar -x -C /tmp -f /ipfire.tar
>>     rm -f /ipfire.tar
>>     cd /tmp && tar  cf /install/cdrom/distro.img --xz * && rm -rf *
>>     xz: (stdin): Cannot allocate memory
>>     make: *** [cdrom:75: /usr/src/log/cdrom] Error 141
>> ...
>> ***SNAP***
>> 
>> Building on Ubuntu 16.04.3 LTS / 32bit.
>> 
>> Can anyone confirm?
>> 
>> Best,
>> Matthias
> 

Re: Current 'next' won't build

[Matthias Fischer]

[-- Attachment #1: Type: text/plain, Size: 479 bytes --]

On 18.10.2017 15:56, Matthias Fischer wrote:
> On 18.10.2017 04:39, Michael Tremer wrote:
>> Hi,
>>
>> how much memory does your build system have?
>> ...

Another info:

***SNIP***
root(a)Devel: /home/matz/ipfire-2.x # xz --info-memory
Total amount of physical memory (RAM):  7,787 MiB (8,165,240,832 B)
Memory usage limit for compression:     Disabled
Memory usage limit for decompression:   Disabled
***SNAP***

8GB. So why is it telling me 'out of memory...?

Best,
Matthias

Re: Current 'next' won't build

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 945 bytes --]

Hi,

I have no idea why that is. It is supposed to use only 370MB for the
compression.

However, the build failed on the nightly build server, too which also has 8GB.
If xz uses that per core (of which this one has 8) this should still be well
under the limit.

I reverted the commits and now it will only compress in parallel. Please pull
from next.

-Michael

On Wed, 2017-10-18 at 16:22 +0200, Matthias Fischer wrote:
> On 18.10.2017 15:56, Matthias Fischer wrote:
> > On 18.10.2017 04:39, Michael Tremer wrote:
> > > Hi,
> > > 
> > > how much memory does your build system have?
> > > ...
> 
> Another info:
> 
> ***SNIP***
> root(a)Devel: /home/matz/ipfire-2.x # xz --info-memory
> Total amount of physical memory (RAM):  7,787 MiB (8,165,240,832 B)
> Memory usage limit for compression:     Disabled
> Memory usage limit for decompression:   Disabled
> ***SNAP***
> 
> 8GB. So why is it telling me 'out of memory...?
> 
> Best,
> Matthias

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: Current 'next' won't build

[Matthias Fischer]

[-- Attachment #1: Type: text/plain, Size: 493 bytes --]

Hi,

On 18.10.2017 16:50, Michael Tremer wrote:
> I reverted the commits and now it will only compress in parallel. Please pull
> from next.

***SNIP***
***Build is finished now and took 0 hour(s) 28 minute(s) 17 second(s)!
root(a)Devel: /home/matz/ipfire-2.x #
***SNAP***

It worked.

I'll try a complete clean build with '--memory=70%" and will report.

Best,
Matthias

P.S.:
...
The limit can be specified as a percentage of physical RAM.
Example: --memory=70%
...

Re: Current 'next' won't build

[Matthias Fischer]

[-- Attachment #1: Type: text/plain, Size: 367 bytes --]

Hi,

On 18.10.2017 17:54, Matthias Fischer wrote:
> I'll try a complete clean build with '--memory=70%" and will report.

This *didn't* work, tried again with '--memlimit=70%', didn't work either.

Only working solution:

--memory=700MiB (or: 750MiB, to be sure)

Or:

--memory=700000000 (doesn't look good...)

Buildtime for cdrom: ~339-355 seconds.

Best,
Matthias

Re: Current 'next' won't build

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 549 bytes --]

Did you compare image size after? Is that being influenced by the memory
parameter?

On Wed, 2017-10-18 at 19:03 +0200, Matthias Fischer wrote:
> Hi,
> 
> On 18.10.2017 17:54, Matthias Fischer wrote:
> > I'll try a complete clean build with '--memory=70%" and will report.
> 
> This *didn't* work, tried again with '--memlimit=70%', didn't work either.
> 
> Only working solution:
> 
> --memory=700MiB (or: 750MiB, to be sure)
> 
> Or:
> 
> --memory=700000000 (doesn't look good...)
> 
> Buildtime for cdrom: ~339-355 seconds.
> 
> Best,
> Matthias

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: Current 'next' won't build

[Matthias Fischer]

[-- Attachment #1: Type: text/plain, Size: 1943 bytes --]

Hi,

On 18.10.2017 19:42, Michael Tremer wrote:
> Did you compare image size after? Is that being influenced by the memory
> parameter?

Slightly.

Current 'next':

Buildtime 03:59:03

***SNIP***
-rw-r--r--   1 root root 255029305 Oct 19 05:15 ipfire-2.19.1gb-ext4.i586-full-core115.img.gz
-rw-r--r--   1 root root        80 Oct 19 05:26 ipfire-2.19.1gb-ext4.i586-full-core115.img.gz.md5
-rw-r--r--   1 root root 252170425 Oct 19 05:19 ipfire-2.19.1gb-ext4-scon.i586-full-core115.img.gz
-rw-r--r--   1 root root        85 Oct 19 05:26 ipfire-2.19.1gb-ext4-scon.i586-full-core115.img.gz.md5
-rw-r--r--   1 root root 184549376 Oct 19 04:50 ipfire-2.19.i586-full-core115.iso
-rw-r--r--   1 root root        68 Oct 19 05:26 ipfire-2.19.i586-full-core115.iso.md5
-rw-r--r--   1 root root      3522 Oct 19 05:26 ipfire-2.19.xen.i586-downloader-core115.tar.bz2
-rw-r--r--   1 root root        82 Oct 19 05:26 ipfire-2.19.xen.i586-downloader-core115.tar.bz2.md5
***SNAP***


Optimized ('... && XZ_OPT="-T0 -8' / '... export XZ_OPT = --threads=0 -8 --memory=750MiB'):

Buildtime 4:25:29

***SNIP***
-rw-r--r--   1 root root 255221827 Oct 19 15:39 ipfire-2.19.1gb-ext4.i586-full-core115.img.gz
-rw-r--r--   1 root root        80 Oct 19 15:52 ipfire-2.19.1gb-ext4.i586-full-core115.img.gz.md5
-rw-r--r--   1 root root 252146461 Oct 19 15:42 ipfire-2.19.1gb-ext4-scon.i586-full-core115.img.gz
-rw-r--r--   1 root root        85 Oct 19 15:52 ipfire-2.19.1gb-ext4-scon.i586-full-core115.img.gz.md5
-rw-r--r--   1 root root 175112192 Oct 19 15:11 ipfire-2.19.i586-full-core115.iso
-rw-r--r--   1 root root        68 Oct 19 15:52 ipfire-2.19.i586-full-core115.iso.md5
-rw-r--r--   1 root root      3537 Oct 19 15:52 ipfire-2.19.xen.i586-downloader-core115.tar.bz2
-rw-r--r--   1 root root        82 Oct 19 15:52 ipfire-2.19.xen.i586-downloader-core115.tar.bz2.md5
***SNAP***


Take your pick... ;-)

Best,
Matthias

Re: Current 'next' won't build

[Matthias Fischer]

[-- Attachment #1: Type: text/plain, Size: 1910 bytes --]

Hi,

On 18.10.2017 19:42, Michael Tremer wrote:
> Did you compare image size after? Is that being influenced by the memory
> parameter?

For the records:

Current 'next', as in previous posting:

Buildtime 03:59:03

***SNIP***
-rw-r--r--   1 root root 255029305 Oct 19 05:15 ipfire-2.19.1gb-ext4.i586-full-core115.img.gz
-rw-r--r--   1 root root        80 Oct 19 05:26 ipfire-2.19.1gb-ext4.i586-full-core115.img.gz.md5
-rw-r--r--   1 root root 252170425 Oct 19 05:19 ipfire-2.19.1gb-ext4-scon.i586-full-core115.img.gz
-rw-r--r--   1 root root        85 Oct 19 05:26 ipfire-2.19.1gb-ext4-scon.i586-full-core115.img.gz.md5
-rw-r--r--   1 root root 184549376 Oct 19 04:50 ipfire-2.19.i586-full-core115.iso
-rw-r--r--   1 root root        68 Oct 19 05:26 ipfire-2.19.i586-full-core115.iso.md5
-rw-r--r--   1 root root      3522 Oct 19 05:26 ipfire-2.19.xen.i586-downloader-core115.tar.bz2
-rw-r--r--   1 root root        82 Oct 19 05:26 ipfire-2.19.xen.i586-downloader-core115.tar.bz2.md5
***SNAP***

'xz' updated to '5.2.3', "optimized":

Build time 3:30:05
***SNIP***-rw-r--r--   1 root root 255172283 Oct 19 20:41 ipfire-2.19.1gb-ext4.i586-full-core115.img.gz
-rw-r--r--   1 root root        80 Oct 19 20:54 ipfire-2.19.1gb-ext4.i586-full-core115.img.gz.md5
-rw-r--r--   1 root root 252156393 Oct 19 20:45 ipfire-2.19.1gb-ext4-scon.i586-full-core115.img.gz
-rw-r--r--   1 root root        85 Oct 19 20:54 ipfire-2.19.1gb-ext4-scon.i586-full-core115.img.gz.md5
-rw-r--r--   1 root root 175112192 Oct 19 20:14 ipfire-2.19.i586-full-core115.iso
-rw-r--r--   1 root root        68 Oct 19 20:54 ipfire-2.19.i586-full-core115.iso.md5
-rw-r--r--   1 root root      3531 Oct 19 20:54 ipfire-2.19.xen.i586-downloader-core115.tar.bz2
-rw-r--r--   1 root root        82 Oct 19 20:54 ipfire-2.19.xen.i586-downloader-core115.tar.bz2.md5
***SNAP***

Looks interesting?

Best,
Matthias

Re: Current 'next' won't build

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 2706 bytes --]

Hi,

did you test if this is a hard limit for all threads together? 

If so that would be quite nice because we can use -9 then and it would just go
up to the ceiling of memory usage and then just cap the size of the dictionary
there (that's what I get from the man page).

I think we can even go up to 1GB since that is a minimum each build system
should have. I would really like to see that extra 10-15MB shaven off the ISO
image.

Would you like to send a patch with all of this? I reverted all previous commits
again because the nightly builds failed.

Best,
-Michael

On Thu, 2017-10-19 at 21:10 +0200, Matthias Fischer wrote:
> Hi,
> 
> On 18.10.2017 19:42, Michael Tremer wrote:
> > Did you compare image size after? Is that being influenced by the memory
> > parameter?
> 
> For the records:
> 
> Current 'next', as in previous posting:
> 
> Buildtime 03:59:03
> 
> ***SNIP***
> -rw-r--r--   1 root root 255029305 Oct 19 05:15 ipfire-2.19.1gb-ext4.i586-
> full-core115.img.gz
> -rw-r--r--   1 root root        80 Oct 19 05:26 ipfire-2.19.1gb-ext4.i586-
> full-core115.img.gz.md5
> -rw-r--r--   1 root root 252170425 Oct 19 05:19 ipfire-2.19.1gb-ext4-
> scon.i586-full-core115.img.gz
> -rw-r--r--   1 root root        85 Oct 19 05:26 ipfire-2.19.1gb-ext4-
> scon.i586-full-core115.img.gz.md5
> -rw-r--r--   1 root root 184549376 Oct 19 04:50 ipfire-2.19.i586-full-
> core115.iso
> -rw-r--r--   1 root root        68 Oct 19 05:26 ipfire-2.19.i586-full-
> core115.iso.md5
> -rw-r--r--   1 root root      3522 Oct 19 05:26 ipfire-2.19.xen.i586-
> downloader-core115.tar.bz2
> -rw-r--r--   1 root root        82 Oct 19 05:26 ipfire-2.19.xen.i586-
> downloader-core115.tar.bz2.md5
> ***SNAP***
> 
> 'xz' updated to '5.2.3', "optimized":
> 
> Build time 3:30:05
> ***SNIP***-rw-r--r--   1 root root 255172283 Oct 19 20:41 ipfire-2.19.1gb-
> ext4.i586-full-core115.img.gz
> -rw-r--r--   1 root root        80 Oct 19 20:54 ipfire-2.19.1gb-ext4.i586-
> full-core115.img.gz.md5
> -rw-r--r--   1 root root 252156393 Oct 19 20:45 ipfire-2.19.1gb-ext4-
> scon.i586-full-core115.img.gz
> -rw-r--r--   1 root root        85 Oct 19 20:54 ipfire-2.19.1gb-ext4-
> scon.i586-full-core115.img.gz.md5
> -rw-r--r--   1 root root 175112192 Oct 19 20:14 ipfire-2.19.i586-full-
> core115.iso
> -rw-r--r--   1 root root        68 Oct 19 20:54 ipfire-2.19.i586-full-
> core115.iso.md5
> -rw-r--r--   1 root root      3531 Oct 19 20:54 ipfire-2.19.xen.i586-
> downloader-core115.tar.bz2
> -rw-r--r--   1 root root        82 Oct 19 20:54 ipfire-2.19.xen.i586-
> downloader-core115.tar.bz2.md5
> ***SNAP***
> 
> Looks interesting?
> 
> Best,
> Matthias

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]