I am working on creating a gentoo ebuild for a software package, and a problem that I am running into is that the main configure script is sending some bad switches to one of the daughter configure scripts. The problem is that this is only happening when the ebuild is being emerged. If I do the configure manually, there are no problems.

So the initial configure command looks like the following:

This appears to work fine, at least until the script spawns a configure script in a daughter directory:

As can be seen in the above configure command, a couple of switches are mangled. I have not been able to find where the heck these are even coming from in the first place, but I am suspecting that there is something broken with the main configure script.

Anyone have any idea what might be wrong?

Why are you passing the --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu? Those are used when cross-compiling, which it doesn't look like you're doing. If you're trying to override config.guess, only --build is needed.

Good call! Of course, I am not that sure how to turn that off in the first place. I am not trying to cross compile at this time. So now the question is how are those items getting set in the first place? I am not familiar with this portion of the gentoo build system, unfortunately.

It looks like you're passing them to the configure script in the initial configure command.

Nope. This is all being done in an ebuild script that I have in my personal overlay, which is then executed by the emerge command. The src_compile() section of the ebuild script looks like this:

Have you tried executing the configure script directly instead of using econf?

Yep, and it works just fine. I stated that in the last sentence of the first paragraph of my original question.

I didn't know if that meant you built the package manually and it worked or whether you used configure directly in the ebuild. Why can't you just use configure in the ebuild instead of the econf function?