Hi Jean, There is a problem with uploading opkg newly generated by opkgc. - I usually rebuild rpms with --target=i686 even though OSCAR packages tree does not have ***-i686 tree(i.e., no $OSCAR_HOME/packages/openmpi/distro/rhel5-i686) because I believes that i686 compiled packages can take care of i386 as well but I am not sure vice versa. Anyway, i686 rpms under ***_i386 distro work fine and I thought they are more general solution to handle a little broad architectures. - On the other hand, the opkg-****.rpm's generated by opkgc picks up the i386 architecture which is matching with the distro tree no matter what it is on the i-series architecture. - So, the ordinary rpms rebuilt with the target i686 and the opkg-****.rpm's generated by opkgc are located in the different places on the gforege repository. For example, my openmpi-1.2.3-1.i686.rpm is under /yum/dists/rhel5/i686/RPMS and opkg-openmpi-1:1.2.3-1.i386 is under /yum/dists/rhel5/i386/RPMS.
Anyway, if OPD can automagically figure out the right RPMs on the repos, I think this would not be a problem whether the rpms are located in i686 or in i386. Otherwise, we have to fix this behavior. Probably I have to recompile all the RedHat rpms to i386? Regards, -- - DongInn ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
