Date: Sun, 11 Jun 2017 17:37:20 -0500 From: "A. Wilcox" <awilfox@...lielinux.org> To: musl@...ts.openwall.com Subject: Re: Issues building gdbserver with musl -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 10/06/17 21:46, Rich Felker wrote: > In order to provide an API matching what glibc exposes, musl > defines pt_regs etc. in the powerpc sys/user.h. (Compare this to > something like the arm version, which has non-overlapping names.) > But this breaks if you also include the kernel header that defines > pt_regs. > > I'm not sure what the right solution is; there really is no good > one. Ideally musl and glibc would agree the problem needs to be > fixed and change user.h to provide definitions with new names that > don't clash with the kernel, and fix glibc's use of kernel headers. > But then applications (basically just gdb) would need to be fixed > to use the new names. Have they been contacted to see if they'd be willing to do that? They seem to be doing a lot of cleanups and breaking changes in their current dev cycle, so this would be the time to ask if I'm reading their lists correctly. > Another possible solution would be removing sys/user.h and other > "just for gdb cruft" from musl and providing it in a separate > package that depends (for some archs) on kernel headers. Or we > could do something really nasty and just say "on broken archs X, Y, > and Z, sys/user.h and other cruft headers depend on kernel headers, > just like on glibc". Is <sys/user.h> really only used by gdb? There are no other users? I might actually put a #warning or #error in the file when I do the Adélie mass tree rebuild to see if that really is the only package. If that is the case, then this really seems like a problem that should be solved out-of-tree (i.e. with a musl-gdb-support package or similar). Do you have a list of the so-called "other just for gdb cruft" headers? I can put #warning / #error in them too, and we can test the feasibility of moving these headers out of musl. > I'm not really sure what's best to do; that's why there's been no > progress on this issue, despite it being known and longstanding. As you might be able to tell, I am highly motivated to find a way to fix it :) That may be because I'm one of a few actually developing for musl on ppc32... > > Rich > Best, - --arw - -- A. Wilcox (awilfox) Project Lead, Adélie Linux http://adelielinux.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJZPcYeAAoJEMspy1GSK50UC/QP/RjMtCnB983w+t9qiNZydKrY dP9GZtd/3HeAZy88Fkgm9VpSCsO4/ztqnLLi9m/nOUHGuLIEEUB+4mYMc4IdEpLZ /mV52NZqIIN/iUDH/KFAb/ejYXLreXw4LXTz3SfcsVAVT9V6fZ7CLFUdy0OPV/VA CYz10bMZTNJJ4pRJiZuoE+mZxxkZUTMzedPvMlpicJ8bfSDKokwXHudLrM/8PiTb i2hDyYTEKypuqOHSYxufba2yie/03EWrKWl6O9K3KbEW9MHiTo/MrpmEQGpRM/gt /3wV6nW5Dv4YEekgg77L25HF3Q4kA7p0REoFlSppr4PvM7VvR2QbWx17inDgNV3m vR9uT9vJE1+uxVOThZb9DAqhRzZ0PMTptf7Lyumui/5O+X5WTUzH/Xv/hdkUNJud ol3C0Orq3wCGWf23JQJ43vhAB+RyLgMseUv802i60FCEYA1ybCg0pnON/WaQJ1x6 NCa5upvnAnQgopFAQFtxy7e2cvo+Er50IP68Lys+wiISoK4kCSEHOvtZB3Vwukrz /sMWM8gIlT7h49sBPgh7f963TvGkHAXKWGShuKXfG/GKOb8zEq9nuaD0eGPa84Et moVK2y7Gx4HDcXtMPba6ng5mVwEpp00W5YDjRQB66PQPeVQ9P6qAyhXMiqtE1vCl 4n04tUPD98XgQ+apO3ln =/ktx -----END PGP SIGNATURE-----
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.