On Tuesday 08 November 2011, Alexander Graf wrote:
Adrian and Dirk, do you remember what exactly the problems were we were facing?
we were unsure if we should build only the toolchain with that triplet or also set the default rpm target to -gnueabi. What exactly should be the toolchain triplet? arm-suse-linux-gnueabihf ? armv7-suse-linux-gnueabihf? The default rpm target we chose to leave at -suse-linux, as there is some weird triplet processing code in rpm that only checks for "-gnu" and nothing else, so we were quite sure that -gnueabi would already break / change the behavior. Thats why we have this inconsistency of building the toolchain with -gnueabi, but setting the default triplet to suse-linux (without any extension). we had quite some issues with the default "build platform" macros in rpm being defined wrongly/incompletly by default in rpm, which is why we first tried to get something running, and then fix the details later. you can see the problematic code here: http://www.google.de/codesearch#oOaobEEuy5M/pub/devil/devel/sources/1.2/rpm-4.0.4.tar.gz%7CZJw7mjoLboI/rpm-4.0.4/lib/rpmrc.c&exact_package=ftp://ftp.lmd.ens.fr/pub/devil/devel/sources/1.2/rpm-4.0.4.tar.gz&q=strcasecmp.co,&type=cs&l=1425 I don't mind switching it if we can get rpm fixed to properly handle the gnueabihf triplet and also initialize the platform target macros properly. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org