Re: [Patches] Phasing out the separate EGLIBC source tree

2013-07-20 Thread Joseph S. Myers
On Sat, 20 Jul 2013, Ryan S Arnold wrote: > Immediately I'll probably move libdfp development to github and then > work on glibc integration (round 2) when I have the time. The > intricacies of the build system will need to be very closely monitored > during migration. (I should also note that I

Re: [Patches] Phasing out the separate EGLIBC source tree

2013-07-20 Thread Joseph S. Myers
On Sat, 20 Jul 2013, Ryan S Arnold wrote: > Libdfp still lacks integration of the libbid backend (to make libdfp > work on x86), and I suspect that might be a prereq for glibc > integration. Tthe libdecnumber back end can be used (with some work) I don't see why that should be needed, as long as

Re: Phasing out the separate EGLIBC source tree

2013-07-20 Thread Ryan S Arnold
On Sat, 2013-07-20 at 11:53 +, Joseph S. Myers wrote: > Following up on discussions in another thread, here is the plan I propose > for phasing out the separate EGLIBC source tree so that all glibc > development for embedded systems goes directly in the main FSF glibc git >

Phasing out the separate EGLIBC source tree

2013-07-20 Thread Joseph S. Myers
Following up on discussions in another thread, here is the plan I propose for phasing out the separate EGLIBC source tree so that all glibc development for embedded systems goes directly in the main FSF glibc git tree. I propose the goal that 2.19, in about six months' time, is the