From: Sergey Mironov <ierton@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: [gentoo-embedded] ebuild deps and cross-compiling
Date: Fri, 23 Apr 2010 15:20:26 +0400 [thread overview]
Message-ID: <k2uaa09d86e1004230420h88b4d66i22fd6c12e416d7a0@mail.gmail.com> (raw)
Hello.
I am maintaining small arm tree built with gentoo crosstools. My
rootfs is based on busybox, which has implementation of udev (called
mdev). My questions are about bad things i found while working with
it.
Recently i have to compile sys-devel/libtool to get libltdl - one of
its runtime libs. The ebuild has following deps:
RDEPEND="sys-devel/gnuconfig
>=sys-devel/autoconf-2.60
>=sys-devel/automake-1.10.1"
DEPEND="${RDEPEND}
|| ( app-arch/xz-utils app-arch/lzma-utils )
sys-apps/help2man"
I think that auto* tools are not required on target system for ltdl to
work. More, those auto-tools implicitly require bash which is not
installed in system.
I solved the problem by fixing the ebuild in local overlay but it is
just workaround. Should i register a libtool bug? Maybe (just guess)
one should split libtool into 'runtime' and 'buildtime' packets?
Here is another issue:
Lets look at dev-libs/openct ebuild.
RDEPEND="pcsc-lite? ( sys-apps/pcsc-lite )
usb? ( virtual/libusb:0 )
>=sys-fs/udev-096"
My system doesn't have udev. It has mdev from busybox. Openct docs
says that mdev is ok, so should i register an ebuild-bug and suggest
something like 'udev useflag'? There are util-linux dependencies,
which are also incompatible with busybox. I am in doubt.
Will be glad to hear your opinion.
--
Thanks,
Sergey
next reply other threads:[~2010-04-23 12:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 11:20 Sergey Mironov [this message]
2010-04-23 14:50 ` [gentoo-embedded] ebuild deps and cross-compiling Ed W
2010-04-24 11:26 ` Gentoo
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=k2uaa09d86e1004230420h88b4d66i22fd6c12e416d7a0@mail.gmail.com \
--to=ierton@gmail.com \
--cc=gentoo-embedded@lists.gentoo.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