Fwd: New builds from the build-infra team

[Erik Joelsson]

On 2012-11-08 21:03, Jonathan Gibbons wrote:
> I'm trying to use the new build system.
>
> I'm working in a langtools repo, and I have a full shared TL forest 
> elsewhere on my system.
>
> In my langtools repo, I've created a build directory and I've executed 
> the configure script from the shared TL forest, specifying that I want 
> to override langtools ...
>
>>     mkdir toybuild
>>     cd toybuild
>> bash /w/jjg/work/tl/common/autoconf/configure 
>> --with-override-langtools=..
>
>
> The script appears to succeed, saying
>
>> A new configuration has been successfully created in
>> /w/jjg/work/newbuild/8/langtools/toybuild
>> using configure arguments '--with-override-langtools=..'.
>
>
> But when I try and build the "langtools" target, I get ...
>
>> $ make langtools
>> Building OpenJDK for target 'langtools' in configuration 
>> '/w/jjg/work/newbuild/8/langtools/toybuild'
>>
>>
>> ########################################################################
>> ########################################################################
>> ##### Entering langtools for target(s) all                         #####
>> ########################################################################
>>
>> Makefile:45: *** Build from top-level Makefile instead.  Stop.
>> Cannot locate top-level Makefile. Is this repo not checked out as 
>> part of a complete forest?
>> make: *** [langtools-only] Error 2
>
I haven't been involved in or tried this feature yet, but that sounds 
like it should work so I will do some investigation.
>
> Has configure not correctly recognized the root of my shared TL 
> forest?   Is there an option I can use to specify where the full 
> forest is?  I tried --srcdir, but the description is somewhat obscure 
> and I wasn't sure if that was the one I should be using, but anyway, 
> it didn't work (for me.)
>
> Also, another comment on the --help output,   many options explicitly 
> list that they take a value.  For example,
>   --with-PACKAGE[=ARG]    use PACKAGE [ARG=yes]
>
> But most of the other --with-* options do not, implying that they do 
> not accept a value.  But something seems to work if you give them a 
> value.  It's not clear (to me) if they are ignoring the value, or 
> whether the value is accepted, but something else is stopping my 
> config from working.
>
I'm sure we have missed explicitly declaring if the parameters take 
values. In some cases it's implied but this might need to be looked over.

/Erik