vp-build/common/build-profiles/armv7l.sh

XBPS_TARGET_CFLAGS="-march=armv7-a -mfpu=vfpv3 -mfloat-abi=hard"
XBPS_TARGET_CXXFLAGS="$XBPS_TARGET_CFLAGS"
XBPS_TARGET_FFLAGS=""
XBPS_TRIPLET="armv7l-unknown-linux-gnueabihf"
XBPS_RUST_TARGET="armv7-unknown-linux-gnueabihf"
xbps-src: set default compiler/preprocessor/linker flags via etc/conf. Rather than setting them in the build profile, just set them in etc/defaults.conf (overridable via etc/conf) to simplify the code. - Also enable _FORTIFY_SOURCE=2 in CPPFLAGS. - Also enable -z,relro in LDFLAGS. As suggested by @chneukirchen. 2015-03-04 15:17:05 +01:00			`XBPS_TARGET_CFLAGS="-march=armv7-a -mfpu=vfpv3 -mfloat-abi=hard"`
			`XBPS_TARGET_CXXFLAGS="$XBPS_TARGET_CFLAGS"`
xbps-src: trying to fix FFLAGS construction This still isn't perfect. When the common/xbps-src/shutils/chroot.sh function chroot_init() is called, the value for $XBPS_FFLAGS, which is defined in common/build-profiles/bootstrap.sh, is empty. Put the immediate value into the generated /etc/xbps/xbps-src.conf file until someone finds out where passing the value of $XBPS_FFLAGS throughout the scripts is missing. 2017-03-08 17:28:31 +01:00			`XBPS_TARGET_FFLAGS=""`
xbps-src: introduce XBPS_TRIPLET and set it in the build-profiles. This is for cases where host does not match build environment (x86_64 building for x86). So we just force build/host triplet in native builds. 2014-11-11 22:24:40 +01:00			`XBPS_TRIPLET="armv7l-unknown-linux-gnueabihf"`
build-profiles: set XBPS_RUST_TARGET 2018-10-12 02:21:13 +02:00			`XBPS_RUST_TARGET="armv7-unknown-linux-gnueabihf"`