On 03/09/2010 02:27 AM, Allan McRae wrote:

On 09/03/10 15:23, Paul Mattal wrote:

...

So this is a weird one, but I think I just made some headway.

Apparently, this seems to be related to the ACTUAL CPU of the box I build on. When building on an i686 Arch box running on an AMD 64 CPU, the build generates the broken binaries! When I build on an Intel CPU, it works fine.

So it would appear this is at least in part Tomcat's build process's fault for not building the right thing based on the uname -m but rather looking directly at the processor.

Yuck. Perhaps I will at least add a note to the PKGBUILD suggesting this issue, so that the next poor person who decides to update tomcat doesn't trip over this same thing.

Seriously... WTF! That is up there with some of the strangest build issues I have ever seen.

Allan

jsvc uses "arch" command. arch is marked as deprecated tool replaced by uname. Anyway "arch" will return correct values when using linux32 wrapper. (And I am on AMD64). what return "linux32 arch" on your weird chroot? -- Gerardo Exequiel Pozzi ( djgera ) http://www.djgera.com.ar KeyID: 0x1B8C330D Key fingerprint = 0CAA D5D4 CD85 4434 A219 76ED 39AB 221B 1B8C 330D