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