From: Bart Veer <bartv@ecoscentric.com>
To: ecos-maintainers@sources.redhat.com
Subject: [APPROVE] fix toplevel configure script as per 86597
Date: Thu, 27 Mar 2003 23:46:00 -0000 [thread overview]
Message-ID: <20030327234631.1E6A1EC6F1@delenn.bartv.net> (raw)
I believe this patch will fix the problems reported in 86597, and have
committed the changes to the trunk. It is probably a good idea for the
release branch as well, but somebody else should probably test it
first in their world.
Bart
2003-03-27 Bart Veer <bartv@ecoscentric.com>
* configure.in, configure:
Look for the host-side sources in tools/src as well as in host, as
per the 2.0 release tree.
Look for per-package host-side software in any/all versions of a
package, not just "current".
Index: configure.in
===================================================================
RCS file: /cvs/ecos/ecos/configure.in,v
retrieving revision 1.2
diff -u -u -r1.2 configure.in
--- configure.in 11 Aug 2002 21:40:50 -0000 1.2
+++ configure.in 27 Mar 2003 23:33:28 -0000
@@ -85,7 +85,7 @@
dnl configure script will search the packages tree for any packages
dnl that have host-side software that needs to be built -
dnl specifically, that have a file "configure" inside a "host"
-dnl subdirectory in version "current" of a package.
+dnl subdirectory in a version of a package.
dnl
dnl 2) if instead the repository contains additional packages
dnl installed as epk's and managed by an administration tool then
@@ -137,8 +137,17 @@
dnl need to worry about compiler flags etc. Instead, the problem is
dnl figuring out what should actually get built.
dnl
-dnl 1) the host subdirectory should always get built.
-SUBDIRS="host"
+dnl 1) the host subdirectory should always get built, if it exists.
+dnl With the 2.0 release system the directory gets moved to
+dnl tools/src
+
+if test -f "${srcdir}/host/configure" ; then
+ SUBDIRS="host"
+elif test -f "${srcdir}/tools/src/configure" ; then
+ SUBDIRS="tools/src"
+else
+ SUBDIRS=""
+fi
dnl 2) any package which has a configure script in a
dnl current/host subdirectory should also get built.
@@ -157,11 +166,11 @@
PKGHOSTDIRS=""
FOUND_CONFIGURES=""
-FOUND_CONFIGURES="${FOUND_CONFIGURES} ${srcdir}/packages/*/current/host/configure"
-FOUND_CONFIGURES="${FOUND_CONFIGURES} ${srcdir}/packages/*/*/current/host/configure"
-FOUND_CONFIGURES="${FOUND_CONFIGURES} ${srcdir}/packages/*/*/*/current/host/configure"
-FOUND_CONFIGURES="${FOUND_CONFIGURES} ${srcdir}/packages/*/*/*/*/current/host/configure"
-FOUND_CONFIGURES="${FOUND_CONFIGURES} ${srcdir}/packages/*/*/*/*/*/current/host/configure"
+FOUND_CONFIGURES="${FOUND_CONFIGURES} ${srcdir}/packages/*/*/host/configure"
+FOUND_CONFIGURES="${FOUND_CONFIGURES} ${srcdir}/packages/*/*/*/host/configure"
+FOUND_CONFIGURES="${FOUND_CONFIGURES} ${srcdir}/packages/*/*/*/*/host/configure"
+FOUND_CONFIGURES="${FOUND_CONFIGURES} ${srcdir}/packages/*/*/*/*/*/host/configure"
+FOUND_CONFIGURES="${FOUND_CONFIGURES} ${srcdir}/packages/*/*/*/*/*/*/host/configure"
for configure in ${FOUND_CONFIGURES}; do
if test -f ${configure}; then
dnl A configure script has been found in the source tree.
reply other threads:[~2003-03-27 23:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030327234631.1E6A1EC6F1@delenn.bartv.net \
--to=bartv@ecoscentric.com \
--cc=ecos-maintainers@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).