From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Building 'next' or 'master' fails
Date: Sun, 01 Mar 2015 19:59:03 +0100 [thread overview]
Message-ID: <1425236343.2721.24.camel@ipfire.org> (raw)
In-Reply-To: <54F20430.1080300@t-online.de>
[-- Attachment #1: Type: text/plain, Size: 2191 bytes --]
Hi,
On Sat, 2015-02-28 at 19:08 +0100, Matthias Fischer wrote:
> Hi,
>
> something I can't cope with:
>
> During compilation, procedure stops, throwing a bunch of errors in
> _ipfire.build.packages.log:
>
> ...
> # Create configuration
> mkdir -pv /install/harddisk/boot/grub
> chroot /install/harddisk grub-mkconfig -o /boot/grub/grub.cfg
> ERROR: ld.so: object '/tools/lib/libpakfire_preload.so' from LD_PRELOAD
> cannot be preloaded: ignored.
> [multiple times...]
> ...
> Generating grub.cfg ...
> ERROR: ld.so: object '/tools/lib/libpakfire_preload.so' from LD_PRELOAD
> cannot be preloaded: ignored.
> [and so on...]
> ...
> device-mapper: table ioctl on failed: No such device or address
> [dto.]
> ...
>
> ...
> ERROR: ld.so: object '/tools/lib/libpakfire_preload.so' from LD_PRELOAD
> cannot be preloaded: ignored.
> device-mapper: table ioctl on failed: No such device or address
> ...
> ERROR: ld.so: object '/tools/lib/libpakfire_preload.so' from LD_PRELOAD
> cannot be preloaded: ignored.
> device-mapper: table ioctl on failed: No such device or address
> ...
> ERROR: ld.so: object '/tools/lib/libpakfire_preload.so' from LD_PRELOAD
> cannot be preloaded: ignored.
> device-mapper: table ioctl on failed: No such device or address
> ...
The preloading issues are not really a problem. This library is just
used to fake some interfaces like uname(). We used this to make builds
working when there was the transition from kernel 2.6.x to 3.x and we
set the machine type to what ever we like.
> Compilation stops with:
> ...
> grep -f /usr/src/config/rootfiles/core/86/exclude -v /tmp/ROOTFILES.tmp
> > /tmp/ROOTFILES
> grep: /usr/src/config/rootfiles/core/86/exclude: No such file or directory
> make: *** [core/86] Error 2
>
> This happens with 'next' and 'master' (both original).
This is not right. The current master tree does not have a directory for
core update 86 [1]. This must be some left over files on your
filesystem. You can just delete them.
-Michael
[1] http://git.ipfire.org/?p=ipfire-2.x.git;a=tree;f=config/rootfiles/core;h=3ba963ceef588fc05193b6a55466f34eaded7b1b;hb=HEAD
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next parent reply other threads:[~2015-03-01 18:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54F20430.1080300@t-online.de>
2015-03-01 18:59 ` Michael Tremer [this message]
2015-03-01 21:14 ` Matthias Fischer
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=1425236343.2721.24.camel@ipfire.org \
--to=michael.tremer@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