./configure lies about target on CentOS

[j_freeman]

On CentOS 4, I successfully build jam and the cross-tools, and I check out the Haiku source tree. When I run ./configure I receive this message:

The compiler specified as Haiku target compiler is not a valid Haiku cross-compiler. Please see ReadMe.cross-compile.
compiler: gcc
compiler is configured for target: i386-redhat-linux

However, if I go ahead and do a "jam -q haiku-image" the image builds flawlessly every time. (And yes, I *did* follow ReadMe.cross-compile to the letter.)

Build tools and Haiku are both at hrev20325.

[j_freeman]

Whoops, the revision is actually hrev20355.

[bonefish]

Replying to j_freeman:

However, if I go ahead and do a "jam -q haiku-image" the image builds flawlessly every time. (And yes, I *did* follow ReadMe.cross-compile to the letter.)

No you didn't. Let me quote the last sentence of the section "Building on a non-BeOS platform" of the ReadMe:

After following the instructions you can directly continue
with the section Building.

and the last sentences of the ReadMe.cross-compile:

The process can take quite some time, but when it finishes the build system is
fully configured and you are ready to compile your first Haiku image.

Instructions on how to build Haiku can be found in the section Building in the
'ReadMe' document.

Both tell you to continue with the section "Building". Running ./configure a second time is nothing this section instructs, but which you obviously did.

[j_freeman]

These are the steps I took, verbatim:

svn checkout svn://svn.berlios.de/haiku/buildtools/trunk haiku
svn checkout svn://svn.berlios.de/haiku/buildtools/trunk buildtools
cd  buildtools/jam
make
./jam0 install
cd ..
cd ..
cd haiku
./configure --build-cross-tools ../buildtools/
./configure (according to the Readme: "When building on Linux and other non-BeOS platforms "haiku" is the only supported target platform, so you don't need the "--target" parameter")

Running ./configure a second time is nothing this section instructs, but which you obviously did.

You must invoke configure twice: once to build the cross tools, and once to set the target platform. It is on the second instance that I received the message telling me my compiler (which I had just built using the first configure) is not a valid cross compiler.

You're absolutely right that Readme.cross-compile does not instruct a second running of ./configure, but if one follows the instructions in Readme.cross-compile, one is lead to Readme where there is a second running of ./configure.

Please correct me if I'm mistaken.

[j_freeman]

Okay, I just realized the source of my confusion:

There's a note under the "Configuring on BeOS" section about not needing to pass the --target parameter if building under Linux. (If someone is "configuring under BeOS", why would they care what needs, or not needs, to be done under Linux?)

Who can I contact about taking that blurb out of the BeOS section? Perhaps moving it to the non-BeOS section?

[bonefish]

I've removed it in hrev20358.

[j_freeman]

Alright, thanks! It was just one of those minor things that can totally mess up an idiot like myself. ;) I'll try and pay closer attention next time.