[Bug 937011] Re: configure test lin libgo fails on arm (setcontext)

2013-01-23 Thread Matthias Klose
now builds in 4.7 and trunk ** Changed in: gcc-snapshot (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/937011 Title: configure test lin libgo fails on arm

[Bug 937011] Re: configure test lin libgo fails on arm (setcontext)

2012-03-29 Thread Michael Hope
The makecontext() routines are now in glibc 2.16 and Ubuntu Precise eglibc 2.15. There's nothing to do on the Linaro GCC side. ** Changed in: gcc-linaro Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 937011] Re: configure test lin libgo fails on arm (setcontext)

2012-03-12 Thread Bug Watch Updater
** Changed in: gcc Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/937011 Title: configure test lin libgo fails on arm (setcontext) To manage notifications about

[Bug 937011] Re: configure test lin libgo fails on arm (setcontext)

2012-03-06 Thread Asa Sandahl
Thank you for the bug report. The comments above clarifies that the problem is that the functions getcontext and setcontext is not supported for ARM. I've set this ticket to medium priority for now. As stated by Peter above, getting the functions into eglibc has already been recognized as a

[Bug 937011] Re: configure test lin libgo fails on arm (setcontext)

2012-03-06 Thread Michael Hope
The getcontext() routines have now landed in glibc-ports and should be available in glibc 2.16. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/937011 Title: configure test lin libgo fails on arm

[Bug 937011] Re: configure test lin libgo fails on arm (setcontext)

2012-02-22 Thread Bug Watch Updater
** Changed in: gcc Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/937011 Title: configure test lin libgo fails on arm (setcontext) To manage notifications

[Bug 937011] Re: configure test lin libgo fails on arm (setcontext)

2012-02-20 Thread Matthias Klose
** Attachment added: test case https://bugs.launchpad.net/bugs/937011/+attachment/2762236/+files/config.c ** Also affects: gcc-linaro Importance: Undecided Status: New ** Bug watch added: GCC Bugzilla #52218 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52218 ** Also affects: gcc

[Bug 937011] Re: configure test lin libgo fails on arm (setcontext)

2012-02-20 Thread Jani Monoses
IIRC the setcontext co API is not implemented on ARM/Linux. Other packages with similar issues used setjmp/longjmp (I recall pth) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/937011 Title:

[Bug 937011] Re: configure test lin libgo fails on arm (setcontext)

2012-02-20 Thread Peter Maydell
Specifically the functions exist but return ENOSYS, which is why this: if (getcontext (c) 0) abort (); will abort. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/937011 Title: configure test

[Bug 937011] Re: configure test lin libgo fails on arm (setcontext)

2012-02-20 Thread Peter Maydell
Trying to get these functions into eglibc for ARM is kind of on the toolchain group's todo list, but (a) not at a hugely high priority and (b) it will take a little while for them to percolate through eglibc and back into distros anyway, so apps/configure scripts need to be prepared to handle the

[Bug 937011] Re: configure test lin libgo fails on arm (setcontext)

2012-02-20 Thread Bug Watch Updater
Launchpad has imported 4 comments from the remote bug at http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52218. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at