On Mon, May 23, 2016 at 6:31 AM, Patrick Ohly <patrick.o...@intel.com> wrote:
> On Mon, 2016-05-23 at 04:52 +0000, Khem Raj wrote: > > I am getting these errors with clang now > > > > > > http://errors.yoctoproject.org/Errors/Details/64935/ > > And I am getting the same link error also during normal builds for > Beaglebone (but not other platforms): > > https://ostroproject.org/jenkins/job/build_beaglebone/1663/console > ... > arm-ostro-linux-gnueabi-gcc -march=armv7-a -mfpu=neon -mfloat-abi=hard > -mcpu=cortex-a8 > --sysroot=/var/lib/jenkins/ostro-worker-17-slot-1-JopZL/ostro-os/build/tmp-glibc/sysroots/beaglebone > -O2 -pipe -g -feliminate-unused-debug-types > -fdebug-prefix-map=/var/lib/jenkins/ostro-worker-17-slot-1-JopZL/ostro-os/build/tmp-glibc/work/cortexa8hf-neon-ostro-linux-gnueabi/mkelfimage/4.0+gitAUTOINC+686a48a339-r0=/usr/src/debug/mkelfimage/4.0+gitAUTOINC+686a48a339-r0 > -fdebug-prefix-map=/var/lib/jenkins/ostro-worker-17-slot-1-JopZL/ostro-os/build/tmp-glibc/sysroots/x86_64-linux= > -fdebug-prefix-map=/var/lib/jenkins/ostro-worker-17-slot-1-JopZL/ostro-os/build/tmp-glibc/sysroots/beaglebone= > -fstack-protector-strong -pie -fpie -D_FORTIFY_SOURCE=2 -Wformat > -Wformat-security -Werror=format-security -fno-stack-protector -Wall > -DVERSION='"2.7"' -DRELEASE_DATE='"27 March 2006"' -I include > -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" > -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" > -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 > -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 > -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_ZLIB_H=1 -Wl,-O1 > -Wl,--hash-style=gnu -Wl,--as-needed -fstack-protector-strong > -Wl,-z,relro,-z,now objdir/main/mkelfImage.o > objdir/linux-i386/mkelf-linux-i386.o objdir/linux-ia64/mkelf-linux-ia64.o > -o objdir/sbin/mkelfImage -lz > /var/lib/jenkins/ostro-worker-17-slot-1-JopZL/ostro-os/build/tmp-glibc/sysroots/x86_64-linux/usr/bin/arm-ostro-linux-gnueabi/../../libexec/arm-ostro-linux-gnueabi/gcc/arm-ostro-linux-gnueabi/5.3.0/ld: > objdir/linux-i386/mkelf-linux-i386.o: relocation R_ARM_MOVW_ABS_NC against > `a local symbol' can not be used when making a shared object; recompile > with -fPIC > objdir/linux-i386/mkelf-linux-i386.o: error adding symbols: Bad value > collect2: error: ld returned 1 exit status > main/Makefile:6: recipe for target 'objdir/sbin/mkelfImage' failed > ... > > Reverting the commit fixes that, so can we just do that in OE-core > master while the problem gets sorted out? I'm not opposed to reverting this, as the issue being fixed was clearly not as bad as this result, but I'm completely unable to repro this for beaglebone with meta-ti, either with the internal toolchain or the external sourcery toolchain. Was this with clang, or some specific toolchain version? Or perhaps ostro is doing something special there? -- Christopher Larson kergoth at gmail dot com Founder - BitBake, OpenEmbedded, OpenZaurus Maintainer - Tslib Senior Software Engineer, Mentor Graphics
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
