Warnings when building mLinux-3.x

[Jeff Cooper]

I have an Conduit and I’m trying to make a factory image. I’ve created a VM running Ubuntu 14.04.1 LTS and executed the following steps:

git clone git://git.multitech.net/mlinux mlinux-3.x
cd mlinux-3.x/
./setup.sh
source env-oe.sh
bitbake mlinux-factory-image

The build appeared to succeed, but it generated 94 warning messages of various types. Some of the errors were:

WARNING: Failed to fetch URL http://argparse.googlecode.com/files/argparse-1.2.1.tar.gz, attempting MIRRORS if available
WARNING: lora-packet-forwarder-usb: No generic license file exists for: SEMTECH in any provider
WARNING: autossh: No generic license file exists for: custom-freely-distributable in any provider
WARNING: Checksum failure encountered with download of https://fedorahosted.org/releases/c/r/cronie/cronie-1.4.11.tar.gz – will attempt other sources if available
WARNING: Renaming /home/jeffc/projects/amsted/mlinux-3.x/downloads/cronie-1.4.11.tar.gz to /home/jeffc/projects/amsted/mlinux-3.x/downloads/cronie-1.4.11.tar.gz_bad-checksum_378c3a8074d716d8146b943c28909ea1
WARNING: Failed to fetch URL ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/lsof_4.87.tar.bz2, attempting MIRRORS if available
WARNING: Failed to fetch URL ftp://ftp.uni-erlangen.de/pub/Linux/LOCAL/dosfstools/dosfstools-2.11.src.tar.gz, attempting MIRRORS if available
WARNING: at91bootstrap: No generic license file exists for: custom-freely-distributable in any provider
WARNING: /home/jeffc/projects/amsted/mlinux-3.x/build/tmp/sstate-control/manifest-mtcdt-libecj-bootstrap.populate_sysroot not found
WARNING: /home/jeffc/projects/amsted/mlinux-3.x/build/tmp/sstate-control/manifest-mtcdt-ecj-initial.populate_sysroot not found
WARNING: /home/jeffc/projects/amsted/mlinux-3.x/build/tmp/sstate-control/manifest-mtcdt-jikes-initial.populate_sysroot not found
WARNING: /home/jeffc/projects/amsted/mlinux-3.x/build/tmp/sstate-control/manifest-mtcdt-cacao-initial.populate_sysroot not found
WARNING: /home/jeffc/projects/amsted/mlinux-3.x/build/tmp/sstate-control/manifest-mtcdt-classpath-initial.populate_sysroot not found
WARNING: QA Issue: lora-gateway-usb: Files/directories were installed but not shipped
/opt/lora/gateway-utils-usb/.debug
/opt/lora/gateway-utils-usb/.debug/util_tx_test-usb
/opt/lora/gateway-utils-usb/.debug/util_spi_stress-usb
/opt/lora/gateway-utils-usb/.debug/util_pkt_logger-usb
/opt/lora/gateway-utils-usb/.debug/util_band_survey-usb
WARNING: QA Issue: ELF binary ‘/home/jeffc/projects/amsted/mlinux-3.x/build/tmp/work/arm926ejste-mlinux-linux-gnueabi/ruby-serialport/1.1.0-r2/packages-split/ruby-serialport/usr/lib/ruby/serialport.so’ has relocations in .text
WARNING: QA Issue: ELF binary ‘/home/jeffc/projects/amsted/mlinux-3.x/build/tmp/work/arm926ejste-mlinux-linux-gnueabi/ruby-sqlite3/1.3.7-r0/packages-split/ruby-sqlite3/usr/lib/ruby/sqlite3/sqlite3_native.so’ has relocations in .text
WARNING: /home/jeffc/projects/amsted/mlinux-3.x/build/tmp/sstate-control/manifest-mtcdt-libecj-bootstrap.populate_sysroot not found
WARNING: /home/jeffc/projects/amsted/mlinux-3.x/build/tmp/sstate-control/manifest-mtcdt-ecj-initial.populate_sysroot not found
WARNING: /home/jeffc/projects/amsted/mlinux-3.x/build/tmp/sstate-control/manifest-mtcdt-jikes-initial.populate_sysroot not found
WARNING: /home/jeffc/projects/amsted/mlinux-3.x/build/tmp/sstate-control/manifest-mtcdt-cacao-initial.populate_sysroot not found
WARNING: /home/jeffc/projects/amsted/mlinux-3.x/build/tmp/sstate-control/manifest-mtcdt-classpath-initial.populate_sysroot not found
WARNING: QA Issue: ELF binary ‘/home/jeffc/projects/amsted/mlinux-3.x/build/tmp/work/arm926ejste-mlinux-linux-gnueabi/openjdk-7-jre/25b30-2.3.12-r5.1/packages-split/openjdk-7-vm-zero/usr/lib/jvm/java-7-openjdk/jre/lib/arm/server/libjvm.so’ has relocations in .text

Is that the expected output or should I be expecting a clean build?

Is 14.04.1 LTS the wrong build environment? If so, what should I be using?

thanks,
Jeff

[Jeff Hatch]

Jeff,

That number of warnings is fairly normal. At least for the “attempting MIRRORS if available” messages. If something is required for the image and it fails to fetch the build will fail with an error.

I am not sure about the populate_sysroot warnings. It appears that there is no populate_sysroot in the bitbake recipes for those pieces of software. It may be that the bitbake cache is messed up somehow. Have you tried rebuilding from scratch?

Jeff

[Author]

Posts