On Mon, Nov 05, 2018 at 09:11:02AM -0500, Greg Troxel wrote: > "Herbert J. Skuhra" <herb...@gojira.at> writes: > > > On Sun, 04 Nov 2018 22:41:12 +0100, "Nick Hudson" wrote: > >> > >> Module Name: src > >> Committed By: skrll > >> Date: Sun Nov 4 21:41:12 UTC 2018 > >> > >> Modified Files: > >> src/etc/etc.evbarm: Makefile.inc > >> > >> Log Message: > >> Only add GENERIC to earmv6 and earmv7 builds > > > > This change obviously breaks "./build.sh -m evbarm -a earmv7hf -U release". > > That seems like an unusual invocation. Do you really mean it that way, > instead of -a evbarm? Passing earmv7hf to -a is an alias which sets > both a amd m, and then the line is also setting m. Why do you include > '-m evbarm' - what cpu type are you trying to build for?
I am trying to build an image for my Raspberry Pi 2B on FreeBSD 12.0-BETA3 and I am just following the instructions from <https://wiki.netbsd.org/ports/evbarm/raspberry_pi/>: ---- CPU types Raspberry Pi 1 uses "earmv6hf". Raspberry Pi 2 uses "earmv7hf". Raspberry Pi 3 uses "earmv7hf". Building yourself Getting sources and building a release with build.sh is not special for evbarm. Pick a CPU type alias and pass it to build.sh with -m. Examples (the first two are equivalent): ./build.sh -m earmv6hf -u release ./build.sh -m evbarm -a earmv6hf -u release ./build.sh -m evbarm -a earmv7hf -u release ---- With etc/etc.evbarm/Makefile.inc r1.97 the command completes. I only have to fix the build of groff (PR #53314) by removing/commenting out the following lines in obj/tools/groff/build/src/include/config.h: #define NEED_DECLARATION_GETTIMEOFDAY 1 #define NEED_DECLARATION_PUTENV 1 #define NEED_DECLARATION_SRAND 1 #define NEED_DECLARATION_STRNCASECMP 1 My Raspberry boots, grows /, reboots and then panics. This happens for several days now. :-( -- Herbert
