Date: Tue, 05 Sep 2000 23:30:31 -0700 From: Marcel Moolenaar <marcel@cup.hp.com> To: Satoshi - Ports Wraith - Asami <asami@FreeBSD.ORG> Cc: obrien@FreeBSD.ORG, Akinori -Aki- MUSHA <knu@idaemons.org>, ports@FreeBSD.ORG, marcel@FreeBSD.ORG Subject: Re: USE_LINUX? Message-ID: <39B5E487.53669CAD@cup.hp.com> References: <200006070819.BAA14744@silvia.hip.berkeley.edu> <86u2f5zy3g.wl@localhost.local.idaemons.org> <vqczooxn561.fsf@silvia.hip.berkeley.edu> <20000607101234.A80031@dragon.nuxi.com> <vqcg0ne9spn.fsf@silvia.hip.berkeley.edu> <39B5C330.6C1A9CE4@cup.hp.com> <vqclmx6w0e5.fsf@bubble.hip.berkeley.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Satoshi - Ports Wraith - Asami wrote:
>
> * Not all ports depend on ${LINUXBASE}/lib/libc.so.6. Some depend on
> * ${LINUXBASE}/usr/i486-linux-libc5/lib/libc.so.5. This is probably
> * academic because both are present and we basicly only need to trigger
> * the automatic installation of either linux_base or linux_devtools
> * depending on the ports needs.
>
> Yes. I actually had the file you mentioned above but noticed that
> alpha support has been added to linux_base instead, so I went for the
> generic name.
>
> Actually, looking at PLIST.alpha I just found libc is called
> libc.so.6.1 there. Hmm. Should I switch with ${ARCH}, or is there
> another generic file I can RUN_DEPENDS on? I guess I can just use
> ldconfig for both BUILD_DEPENDS and RUN_DEPENDS?
Yes. Another option is /compat/linux/etc/redhat-release. I explicitly
kept that file for these purposes (but don't care if it's not used :-).
If such is needed in the future we can parse that file for the version
number and complain if it's not appropriate for the port.
I just looked in /usr/ports/devel/linux_devtools and it contains the
following dependencies:
RUN_DEPENDS =
${PREFIX}/etc/redhat-release:${PORTSDIR}/emulators/linux_base
where PREFIX .equ. LINUXBASE in the patch.
> Ok. The mtree files are used to ensure consistent directory
> structures among other ports, but since all Linux-compat ports depend
> on linux_base and will get the same set of directories from there,
> this isn't much of a problem. If you don't see the need, I'll just
> change it to NO_MTREE.
At this time I don't see the need. If new evidence pops up, we can
always decide to do it then.
> * Setting RUN_DEPENDS should be harmless WRT the linux_base port. It's
> * BUILD_DEPENDS that's causing problems. Do we have an INSTALL_DEPENDS?
>
> RUN_DEPENDS is INSTALL_DEPENDS if you mean "dependency checked from
> the install target". :)
Yes. I was thinking about why and when a port would need ldconfig and
concluded that it likely doesn't need ldconfig until after it has
installed the libraries. This of course means that a dependency on
ldconfig for the build phase is wrong. If a port builds linux binaries
from source, it depends on linux_devtools and BUILD_DEPENDS should
contain something like gcc. If it downloads and installs a distribution,
then BUILD_DEPENDS can be something like rpm, but not ldcondig. The
install target will need a dependency on ldconfig or libc.so or whatever
to make sure that linux_base is installed first.
I think that the BUILD_DEPENDS should be empty by default. Only fFr the
ports that depend on linux_devtools to work (linux_kdump for example),
something like
BUILD_DEPENDS =
${LINUXBASE}/usr/bin/gcc:${PORTSDIR}/devel/linux_devtools
will do the trick.
> Anyway, as I said above, I think linux_base can be the only port that
> sets PREFIX=${LINUX_BASE} directly and all others can use one of
> USE_LINUX_PREFIX or USE_LINUX. (Sort of like the relationship between
> USE_X_PREFIX and USE_XLIB -- the former implies the latter.)
Works for me.
--
Marcel Moolenaar
mail: marcel@cup.hp.com / marcel@FreeBSD.org
tel: (408) 447-4222
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39B5E487.53669CAD>