| 1 |
Hi, |
| 2 |
|
| 3 |
Today when I was preparing for a "emereg --update ..." on my Raspberry |
| 4 |
PI 2B I saw that there was a news item regarding |
| 5 |
"2018-09-07-arm-17-profile-migration" where it states (among other |
| 6 |
things) "In short, the tuple will change from |
| 7 |
armv7a-hardfloat-linux-gnueabi to |
| 8 |
armv7a-unknown-linux-gnueabihf or similar.". |
| 9 |
|
| 10 |
Today I have the profile set to "default/linux/arm/13.0/armv7a (dev)" |
| 11 |
and I have the following in make.conf |
| 12 |
CFLAGS="-O2 -pipe -march=armv7-a -mfpu=vfpv3-d16 -mfloat-abi=hard" |
| 13 |
CHOST="armv7a-hardfloat-linux-gnueabi" |
| 14 |
|
| 15 |
I am not 100% sure on what to set my profile & CHOST to for this Raspberry. |
| 16 |
|
| 17 |
So (some) of my questions are. |
| 18 |
1) Which new profile should a use for a Raspberry PI 2B which runs as a |
| 19 |
headless "server" (i.e. now desktop environment running)? I suspect |
| 20 |
"default/linux/arm/17.0/armv7a" would be a good idea? |
| 21 |
2) What would be the correct CFLAGS & CHOST in make.conf? |
| 22 |
|
| 23 |
Regards, |
| 24 |
-- |
| 25 |
Dan Johansson, |
| 26 |
*************************************************** |
| 27 |
This message is printed on 100% recycled electrons! |
| 28 |
*************************************************** |
Archives