Re: "struct user" conflicts on arm
On 17 December 2011 09:17, peter green
<peter.green@postgrad.manchester.ac.uk> wrote:
> While we are talking about modifying sys/ucontext.h David Given
> raised another issue with that header (for those reading on the linaro list
> his
> post can be found at
> http://lists.debian.org/debian-arm/2011/12/msg00048.html)
> David Given>This might be a good time to mention that on ARM, sys/ucontext.h
> defines
> David Given>both symbols and preprocessor macros called R0, R1, R2, etc in
> the
> David Given>global namespace; this is causing one of my packages to fail to
> build
> David Given>due to symbol collision.
> David Given>
> David Given>I'm fixing the package, but naming symbols stuff like that is
> still
> David Given>pretty antisocial...
> Does anyone know what the impact of renaming these to use a REG_ prefix like
> i386, amd64 and sparc do* would be?
at worst the packages that had to be workaround on arm* for this, can
have the workaround removed.
Since you're in the process of fixing things for glibc/arm, would you
mind also looking at WCHAR_MIN/MAX undefined for arm?
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598937
Thanks
Konstantinos
Reply to: