Re: how to distinguish armel and armhf at runtime?
Yeah, and cat /proc/cpuinfo doesn't really help much either. I don't
suppose it's kosher to look at some file names in
/var/cache/apt/archives. I had that problem with a phone I installed
Debian on a couple years ago. Finally gave up and left it armel when
I could have gone to armhf (I think).
There are some ideas at
https://www.raspberrypi.org/forums/viewtopic.php?t=20873 but I just
googled https://www.google.com/search?q=gcc+armhf+armel&ie=utf-8&oe=utf-8
On 9/22/17, Uwe Kleine-König <uwe@kleine-koenig.org> wrote:
> Hello,
>
> for the package sparse I have to distinguish armel and armhf. The reason
> is that sparse parses system headers and so has to know which cpp
> symbols to define. Usually it uses uname -m to distinguish platforms but
> that isn't suitable to tell armel and armhf apart.
>
> For armhf I need to define __ARM_PCS_VFP but that must be absent on armel.
>
> For upstreaming a fix it would be great if the test would not be Debian
> specific.
>
> Any ideas?
>
> Best regards
> Uwe
>
>
--
-------------
No, I won't call it "climate change", do you have a "reality problem"? - AB1JX
Impeach Impeach Impeach Impeach Impeach Impeach Impeach Impeach
Reply to: