smithrb

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.

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...

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

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

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.

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