| 1 |
September 22, 2018 5:36 PM, "Dan Johansson" <Dan.Johansson@×××.nu> wrote: |
| 2 |
|
| 3 |
> Hi, |
| 4 |
> |
| 5 |
> Today when I was preparing for a "emereg --update ..." on my Raspberry |
| 6 |
> PI 2B I saw that there was a news item regarding |
| 7 |
> "2018-09-07-arm-17-profile-migration" where it states (among other |
| 8 |
> things) "In short, the tuple will change from |
| 9 |
> armv7a-hardfloat-linux-gnueabi to |
| 10 |
> armv7a-unknown-linux-gnueabihf or similar.". |
| 11 |
> |
| 12 |
> Today I have the profile set to "default/linux/arm/13.0/armv7a (dev)" |
| 13 |
> and I have the following in make.conf |
| 14 |
> CFLAGS="-O2 -pipe -march=armv7-a -mfpu=vfpv3-d16 -mfloat-abi=hard" |
| 15 |
> CHOST="armv7a-hardfloat-linux-gnueabi" |
| 16 |
> |
| 17 |
> I am not 100% sure on what to set my profile & CHOST to for this Raspberry. |
| 18 |
> |
| 19 |
> So (some) of my questions are. |
| 20 |
> 1) Which new profile should a use for a Raspberry PI 2B which runs as a |
| 21 |
> headless "server" (i.e. now desktop environment running)? I suspect |
| 22 |
> "default/linux/arm/17.0/armv7a" would be a good idea? |
| 23 |
> 2) What would be the correct CFLAGS & CHOST in make.conf? |
| 24 |
|
| 25 |
Hi, |
| 26 |
|
| 27 |
The script linked in the news item should take care of that. |
| 28 |
Don't forget to backup your packages (quickpkg */*) before doing the migration, it will help in |
| 29 |
case you need to rollback. |
| 30 |
|
| 31 |
Best regards, |
| 32 |
Corentin “Nado” Pazdera |
Archives