Yes. How stupid of me. Certainly the package description and not the command line option to start the program will is related to a missing runtime library. On Aug 27, 2014 3:03 AM, "François Revol" <revol@xxxxxxx> wrote: > On 27/08/2014 07:45, James Leone wrote: > > setarch=x86 \ > > ./myprogram > > > > That's not what he was asking about. > > ... > > > On Tue, Aug 26, 2014 at 2:20 PM, Fredrik Modéen <fredrik@xxxxxxxxx> > wrote: > >>> The package's architecture declaration must match the primary > >>> architecture of the system in which you want to install the package, > >>> regardless of which compiler you built it with (exception are generic > >>> architectures like "any"). > >>> > >> > >> So how do I do when I need to make a gcc4 package and want it to run in > a > >> GCC2 hybride? > > Just look at the haiku_x86 package: > > > package list > /system/packages/haiku_x86-r1~alpha4_pm_hrev47737-1-x86gcc2.hpkg > package-attributes: > name: haiku_x86 > [...] > architecture: x86_gcc2 > version: r1~alpha4_pm_hrev47737-1 > copyright: 2001-2013 Haiku, Inc. et al > license: MIT > license: GNU LGPL v2.1 > provides: haiku_x86 = r1~alpha4_pm_hrev47737-1 (compatible >= > r1~alpha1) > > The secondary architecture is only expressed in the package name and the > provides/requires directives. > > That is, to package kit it's still an x86_gcc2 package after all, with > different names. > > François. > >