public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Current 'next' won't build
Date: Sun, 29 Apr 2018 13:53:19 +0200	[thread overview]
Message-ID: <450c9e60-a84c-acac-e7ee-0784a4f3fd00@ipfire.org> (raw)

[-- 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

             reply	other threads:[~2018-04-29 11:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-29 11:53 Matthias Fischer [this message]
2018-04-29 12:08 ` Peter Müller
  -- strict thread matches above, loose matches on Subject: below --
2019-06-08 10:20 Matthias Fischer
2019-06-08 10:21 ` Michael Tremer
2019-06-08 10:33   ` Matthias Fischer
2019-06-08 10:35     ` Michael Tremer
2019-06-08 11:38       ` Matthias Fischer
2018-12-23  9:59 Matthias Fischer
2018-12-25  8:22 ` Michael Tremer
2017-10-18  2:39 Matthias Fischer
2017-10-18  2:39 ` Michael Tremer
2017-10-18 13:56   ` Matthias Fischer
2017-10-18 14:22     ` Matthias Fischer
2017-10-18 14:50       ` Michael Tremer
2017-10-18 15:54         ` Matthias Fischer
2017-10-18 17:03           ` Matthias Fischer
2017-10-18 17:42             ` Michael Tremer
2017-10-19 14:00               ` Matthias Fischer
2017-10-19 19:10               ` Matthias Fischer
2017-10-23 14:22                 ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=450c9e60-a84c-acac-e7ee-0784a4f3fd00@ipfire.org \
    --to=matthias.fischer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox