configure WARNINGS

[David Holmes]

On 23/10/2012 12:08 AM, Magnus Ihse Bursie wrote:
> On 2012-10-22 13:51, David Holmes wrote:
>> configure: WARNING: you should use --build, --host, --target
>> configure: WARNING: you should use --build, --host, --target
>>
>> Previuously reported internally but now sending to the list. My host
>> machine is 64-bit linux and I'm building 32-bit linux. What do I have
>> to set and why?
>>
>> My configure command used --with-target-bits=32
>
> Is that all? Are you sure?

Well that is the only significant option. The full set is:

CONFIGURE_COMMAND_LINE='--with-jdk-variant=normal 
--with-jvm-variants=client --with-target-bits=32 
--with-cups-include=/java/devtools/share/cups/include/ --disable-ccache'

> Autoconf has a legacy-mode where you can specify a platform (used for
> both build and target, I don't know really what that would be useful for
> other maybe if the configure autodetection fails), without giving any
> --option prefix, e.g.
> sh configure my-platform
> instead of
> sh configure --build my-platform --target my-platform
>
> This feature has been deprecated for a long time, but does not seem like
> it's going away. However it prints this warning.
>
> So my guess is that you are sending in some additional piece of command
> line arguments. If you also specify target setting using
> --openjdk-target or --build/--target/--host, these will override, and
> you can send in "badgerbadgerbadger" for all it's worth, and the only
> result would be the above warning.

None of the above AFAICT. Here's the relevant output from bash -x configure

++ case $ac_dashdash$ac_option in
+++ expr x--with-target-bits=32 : 'x-*with-\([^=]*\)'
++ ac_useropt=target-bits
++ expr xtarget-bits : 
'.*[^-+._abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789]'
++ ac_useropt_orig=target-bits
+++ printf '%s\n' target-bits
+++ sed 's/[-+.]/_/g'
++ ac_useropt=target_bits
++ case $ac_user_opts in
++ eval 'with_target_bits=$ac_optarg'
+++ with_target_bits=32
++ for ac_option in '"$@"'
++ test -n ''
++ case $ac_option in
++ ac_optarg=yes
++ case $ac_dashdash$ac_option in
++ printf '%s\n' 'configure: WARNING: you should use --build, --host, 
--target'
configure: WARNING: you should use --build, --host, --target

I'm guessing that setting target-bits is triggering some other kind of 
argument checking ??


BTW I also noticed this:

  ac_msg='sources are in 
/java/embedded/users/dh198349/build-infra/builds/../common/autoconf, but 
`cd 
/java/embedded/users/dh198349/build-infra/builds/../common/autoconf'\'' 
does not work'

Though it doesn't seem to cause any problems.

Thanks,
David
-----