Am 28.08.2014 um 21:58 schrieb Fredrik Modéen <fredrik@xxxxxxxxx>: > 2014-08-28 21:50 skrev Stephan Aßmus: >> Hi, >> Am 28.08.2014 um 21:31 schrieb Fredrik Modéen <fredrik@xxxxxxxxx>: >>> So there are 2 places to express what architecture this package are? In the >>> name and architecture: ? >>> It's the name of the package that are the one that are important? >> No. If you are running a Haiku hybrid with the base system being >> x86_gcc2, but with support for x86 binaries, then if you want to >> provide the same software for both architecture of the hybrid, then >> both packages would be for the „x86_gcc2“ base architecture of your >> Haiku. One would be called „your_package-version-x86_gcc2.hpkg“ and >> the other would be called „your_package_x86-version-x86_gcc2.hpkg“ and >> contain the same software, but in the x86 secondary architecture >> folders. The names would need to be different already because both >> packages would be located in the same folder. >> If your Haiku is an x86 based hybrid, then your packages would be named >> your_package-version-x86.hpkg (targeting main arch for x86 Haiku) >> your_package_x86_gcc2-version-x86.hpkg (targeting secondary arch for x86 >> Haiku) > > Ok. It's the official x86_gcc2 hybrid image so base are x86_gcc2 but there > will not be an x86_gcc2 version. > > Anyhow "x86 secondary architecture folders" perhaps that's what's missing? > Perhaps the system try to run an x86 program with x86_gcc2 libs? Sure, that could be the problem. Maybe look at the WebKit package(s) with Expander to see where stuff goes. Best regards, -Stephan