Has configure changed behaviour??

[David Holmes]

Went to do my first build in a couple of months. Sitting in top-level of 
forest (with empty build directory - having deleted old config).

bash ./common/bin/jib.sh configure -p linux-x64-debug

yields:

configure: Current directory is /scratch/dh198349/jdk10-hs.
configure: Since this is not the source root, configure will output the 
configuration here
configure: (as opposed to creating a configuration in 
<src_root>/build/<conf-name>).
configure: However, this directory is not empty. This is not allowed, 
since it could
configure: seriously mess up just about everything.
configure: Try 'cd /export/users/dh198349/jdk10-hs' and restart configure
configure: (or create a new empty directory and cd to it).

---

That is very confusing:

1. what is a src_root and why does it think I would want to create 
<src_root>/build/<conf-name> instead of ./build/<conf-name>?

2. Why does it tell me to try to cd to the directory I am already in??? 
( /scratch is a softlink to /export/users)

3. I created a new directory (build) and cd'd into as suggested, which got:

Error: java.io.FileNotFoundException: 
/export/users/dh198349/jdk10-hs/build/configure (No such file or directory)

---

I'm sure it wasn't this hard to run configure before I went on vacation. :)

How do I persuade configure to create <top-of-forest>/build/<conf-name> ?

And does the "advice" configure gave me make any sense?

Thanks,
David