From owner-freebsd-ports Tue Sep 5 23:30:38 2000 Delivered-To: freebsd-ports@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id D14FD37B423; Tue, 5 Sep 2000 23:30:34 -0700 (PDT) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id AE932603; Tue, 5 Sep 2000 23:30:33 -0700 (PDT) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id XAA28638; Tue, 5 Sep 2000 23:30:32 -0700 (PDT) Message-ID: <39B5E487.53669CAD@cup.hp.com> Date: Tue, 05 Sep 2000 23:30:31 -0700 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Satoshi - Ports Wraith - Asami Cc: obrien@FreeBSD.ORG, Akinori -Aki- MUSHA , ports@FreeBSD.ORG, marcel@FreeBSD.ORG Subject: Re: USE_LINUX? References: <200006070819.BAA14744@silvia.hip.berkeley.edu> <86u2f5zy3g.wl@localhost.local.idaemons.org> <20000607101234.A80031@dragon.nuxi.com> <39B5C330.6C1A9CE4@cup.hp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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