This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Sequential build of libjava
- From: Brad Lucier <lucier at math dot purdue dot edu>
- To: psmith at gnu dot org
- Cc: lucier at math dot purdue dot edu (Brad Lucier), ghazi at caip dot rutgers dot edu (Kaveh R. Ghazi), gcc at gcc dot gnu dot org, java at gcc dot gnu dot org, matz at suse dot de, mszick at goquest dot com, phil at jaj dot com, tromey at redhat dot com
- Date: Fri, 13 Sep 2002 23:06:55 -0500 (EST)
- Subject: Re: Sequential build of libjava
>
> %% Brad Lucier <lucier@math.purdue.edu> writes:
>
> >> We can't rely on GNU make (libjava does, but that is a bug).
> >> So we can only do this if someone writes the configury code to detect
> >> this situation.
>
> bl> In other words, configure should figure out if we're using gnu
> bl> make, and if so, put a plus sign there in the definition of
> bl> MULTIDO.
>
> It's not hard for configure to find out if a given make is GNU
> make... here's an easy test:
>
> echo 'all:;@echo $(MAKE_VERSION)' | make -f-
>
> If this returns with 3.*, for example, it's GNU make. Or you could just
> run "make --version".
>
> The problem, and the reason configure doesn't do this now, is that make
> is the user's tool... how does configure fine the make that the user
> will run?
>
> What if configure finds "/usr/bin/make", but then the user types "gmake"
> to invoke the build? Or something?
OK, so what can be done at build invocation time to get this right?
Brad