From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2014.12.0 released
Date: Tue, 16 Dec 2014 06:58:19 +0100 [thread overview]
Message-ID: <20141216055819.GP31594@pengutronix.de> (raw)
In-Reply-To: <5053571.Pnod4RTFze@ws-stein>
Hi,
On Mon, Dec 15, 2014 at 09:50:36AM +0100, Alexander Stein wrote:
> On Friday 12 December 2014 17:12:17, Michael Olbrich wrote:
> > I'm happy to announce that I've just released OSELAS.Toolchain-2014.12.0.
>
> Thanks for the new release. But I have trouble generating the .deb file. I'm running a non-Debian disto, Gentoo in particular, but this souldn't matter as the debian related packages are installed.
> I attached the logfile containing the .deb build step. I'm not a shell expert, but it seems to me that the argument list is too long.
> As I don't need the .deb file, I workaround that by touching e.g. dist/oselas.toolchain-2014.12.0-arm-1136jfs-linux-gnueabi-gcc-4.9.2-glibc-2.20-binutils-2.24-kernel-3.16-sanitized_2014.12.0_amd64.deb
> Any idea how to fix that?
[...]
> -----------------------------------------------------------------------------------------------------------------------------------------
> target: oselas.toolchain-2014.12.0-arm-1136jfs-linux-gnueabi-gcc-4.9.2-glibc-2.20-binutils-2.24-kernel-3.16-sanitized_2014.12.0_amd64.deb
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Copy data...
> Generate dependencies...
> dpkg-shlibdeps: error: no dependency information found for /lib64/libc.so.6 (used by /home/alex/Dokumente/repo/OSELAS.Toolchain/dist//oselas.toolchain-2014.12.0-arm-1136jfs-linux-gnueabi-gcc-4.9.2-glibc-2.20-binutils-2.24-kernel-3.16-sanitized-temp/tmp/opt/OSELAS.Toolchain-2014.12.0/arm-1136jfs-linux-gnueabi/gcc-4.9.2-glibc-2.20-binutils-2.24-kernel-3.16-sanitized/bin/arm-1136jfs-linux-gnueabi-gcc-ar)
> Hint: check if the library actually comes from a package.
[...]
> make: *** [/home/alex/Dokumente/repo/OSELAS.Toolchain/dist/oselas.toolchain-2014.12.0-arm-1136jfs-linux-gnueabi-gcc-4.9.2-glibc-2.20-binutils-2.24-kernel-3.16-sanitized_2014.12.0_amd64.deb] Error 2
With the new release, make_deb.sh uses dpkg-shlibdeps to expand the
dependencies of the Debian packages. This is done by checking all binaries
and collecting the libraries they need.
If dpkg-shlibdeps finds a library that is not part of a Debian package, it
fails with this error.
I've seen this on one host as well (with /lib/libc.so.6). I _think_ it's
just a leftover from a failed update, because it doesn't exist on the other
servers. But we've not removed it yet.
Hacking the ptxconfig file to remove the option should probably work for
you. I guess I should make those packages optional for future releases.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2014-12-16 5:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 16:12 Michael Olbrich
2014-12-15 8:50 ` Alexander Stein
2014-12-16 5:58 ` Michael Olbrich [this message]
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=20141216055819.GP31594@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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