Trying to build the 1.11 red-brick image from source and I'm receiving the following after running prepare-host.sh:

 

"E: You must put some 'source' URIs in your sources.list"

 

If this referring to /etc/apt/sources.list for the host that I'm building on?

 

Thanks

You're probably missing a deb-src line in your /etc/apt/sources.list. Maybe the deb-src line is there but commented out.

Confused about why the host would require this line in sources.list.  I don't want sources in general for the host, I just that which is needed to rebuild the red-brick image from sources.

After a little more, not confused regarding deb-src need.

 

after running prepare-host.sh, I get the following:

 

.../tf/red-brick/image/tools/qemu-2.10.1/rules.mak:66: recipe for target 'util/memfd.o' failed

Okay, the situation is this: There was a bug in QEMU that affected the image building process. That bug got fixed in QEMU 2.10.1. But at the time this QEMU versions didn't hit the distro repositories yet. That's why the prepare-host.sh builds it from source. That's also why the deb-src line is required.

 

I just checked and Ubuntu Bionic Beaver ships QEMU 2.11, so we don't have to build it from source anymore. We'll modify the scripts to check if the system-provided QEMU is new enough and only build from source if it's not.

 

In you case you can ignore the build-error from QEMU. This was the last step in the prepare-host.sh script anyway. You can consider prepare-host.sh as successfully passed.

 

To make the remaining image building process work now, you need to modify make-root-fs.sh and change line 185 from

 

cp $TOOLS_DIR/$QEMU_BASE_NAME/arm-linux-user/qemu-arm $ROOTFS_DIR$QEMU_BIN

 

to

 

cp /usr/bin/qemu-arm-static $ROOTFS_DIR$QEMU_BIN

 

to make the script pick up the system QEMU instead of the unsuccessfully build one.

 

After that you can continue the image build process according to the readme file.

Got through your suggestions.  Now I'm seeing...

 

2018-03-20 19:18:22 - Error: U-Boot was not built for the current image configuration

 

after having run

 

sudo ./make-root-fs.sh full

 

 

 

Du you run "./compile-source.sh full" before?

I did - yes.  Missed seeing a dependency issue, had to

 

install swig libpython-dev

 

and got a clean compile.

 

Now seeing:

W: GPG error: http://security.debian.org stretch/updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9D6D8F6BC857C906 NO_PUBKEY 8B48AD6246925553

E: The repository 'http://security.debian.org stretch/updates InRelease' is not signed.

N: Updating from such a repository can't be done securely, and is therefore disabled by default.

N: See apt-secure( manpage for repository creation and user configuration details.

W: GPG error: http://ftp.debian.org/debian stretch-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010

E: The repository 'http://ftp.debian.org/debian stretch-updates InRelease' is not signed.

N: Updating from such a repository can't be done securely, and is therefore disabled by default.

N: See apt-secure( manpage for repository creation and user configuration details.

W: GPG error: http://ftp.debian.org/debian stretch Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY EF0F382A1A7B6500

E: The repository 'http://ftp.debian.org/debian stretch Release' is not signed.

N: Updating from such a repository can't be done securely, and is therefore disabled by default.

N: See apt-secure( manpage for repository creation and user configuration details.

apt update failed. Exit value: 100

+ cleanup

+ report_info 'Cleaning up before exit...'

++ date '+%Y-%m-%d %H:%M:%S'

+ echo -e '\n2018-03-21 18:00:25 - Info: Cleaning up before exit...\n'

 

2018-03-21 18:00:25 - Info: Cleaning up before exit...

We've fixed the missing dependency issue.

 

We can reproduce the GPG error, but only on Ubuntu Bionic Beaver. It doesn't occur on the previous Ubuntu versions. We're looking into it.

Great - not urgent, but I do want to build from source at some point...

 

I realize I'm early with Bionic Beaver, but other things are driving that.

 

Bionic Beaver releases end of April I believe.