Displaying 8 results from an estimated 8 matches for "r_cv_libc_stack_end".
2016 Feb 01
3
Wrong config check for __libc_stack_end
@Simon. Here's what I did.
I checked out R revision 70059.
Ran export r_cv_libc_stack_end=no. (otherwise it would give that error
we talked about before)
Ran ./configure --without-recommended-packages. (otherwise it would
complain of not finding ./src/library/Recommended/MASS_*.tar.gz)
Ran make.
Ran make check. Log is here - http://pastebin.com/raw/cGJgqB8p
What do you think? Is there...
2016 Jan 28
2
Abuse of a private glibc symbol in R 3.2.3
...),
perhaps because the test program does not actually *use* __libc_stack_end
so it gets optimized out. (See line 35500 or so in R-3.2.3/configure.)
Ideally, the test program would check that a pointer to __libc_stack_end
is non-null, but that's an autoconf bug.
A work around was to 'export r_cv_libc_stack_end=no' before configuring R.
However, there are a couple little issues with non-ASCII text and a
*lot* of math differences, many of which say "*no* convergence: NOTIFY
R-core!".
Until these are resolved, R can't be packaged for distributions that
use musl, such as Alpine Linux.
Tha...
2016 Feb 01
3
Wrong config check for __libc_stack_end
...familiar with that part of the code, neither
the configuration, nor the usage (in R/src/unix/system.c ).
However, that code seems to be using a a glibc "feature" widely
available which does help making R startup (a very tiny bit ??)
faster.
>> A work around was to 'export r_cv_libc_stack_end=no'
>> before configuring R.
which *does* solve that problem, right?
>> However, there are a couple little issues with non-ASCII
>> text and a *lot* of math differences, many of which say
>> "*no* convergence: NOTIFY R-core!".
Hmm, I may be...
2016 Feb 01
0
Wrong config check for __libc_stack_end
On Feb 1, 2016, at 9:56 AM, Alba Pompeo <albapompeo at gmail.com> wrote:
> @Simon. Here's what I did.
> I checked out R revision 70059.
> Ran export r_cv_libc_stack_end=no. (otherwise it would give that error
> we talked about before)
No, the whole point was to test this behavior. I see that the fix is in configure.ac but not configure so you'll need to run something like
aclocal -I m4 && autoconf
to update it.
Also please don't build in the s...
2016 Feb 01
3
Wrong config check for __libc_stack_end
...w/1qfjqQY2
On Mon, Feb 1, 2016 at 1:53 PM, Simon Urbanek
<simon.urbanek at r-project.org> wrote:
>
> On Feb 1, 2016, at 9:56 AM, Alba Pompeo <albapompeo at gmail.com> wrote:
>
>> @Simon. Here's what I did.
>> I checked out R revision 70059.
>> Ran export r_cv_libc_stack_end=no. (otherwise it would give that error
>> we talked about before)
>
> No, the whole point was to test this behavior. I see that the fix is in configure.ac but not configure so you'll need to run something like
> aclocal -I m4 && autoconf
> to update it.
>
> Also...
2008 Jun 07
1
Fail to call AC_CACHE_CHECK on R 2.7.0 for Solaris
....ac, I think AC_CACHE_CHECK is only called on Linux, and not
on Solaris. Obviously this could explain why this bit of Sage works on
Linux, but not Solaris.
## check for visible __libc_stack_end on Linux
case "${host_os}" in
linux*)
AC_CACHE_CHECK([for visible __lib_stack_end],
[r_cv_libc_stack_end],
[AC_RUN_IFELSE([AC_LANG_SOURCE([[
#include "confdefs.h"
#include <stdlib.h>
extern void * __libc_stack_end;
So it seems to me this will never work, as the the relevant macro is
not run on Solaris. It begs the obvious question why does this work
when I download the source of R...
2016 Jan 29
0
Abuse of a private glibc symbol in R 3.2.3
...est program does not actually *use* __libc_stack_end
> so it gets optimized out. (See line 35500 or so in R-3.2.3/configure.)
> Ideally, the test program would check that a pointer to __libc_stack_end
> is non-null, but that's an autoconf bug.
>
> A work around was to 'export r_cv_libc_stack_end=no' before configuring R.
> However, there are a couple little issues with non-ASCII text and a
> *lot* of math differences, many of which say "*no* convergence: NOTIFY
> R-core!".
>
> Until these are resolved, R can't be packaged for distributions that
> use mus...
2016 Feb 01
0
Wrong config check for __libc_stack_end
...ever, that code seems to be using a a glibc "feature" widely
> available which does help making R startup (a very tiny bit ??)
> faster.
>
No, it's actually very crucial as it is used to detect stack overflows.
Cheers,
Simon
>>> A work around was to 'export r_cv_libc_stack_end=no'
>>> before configuring R.
>
> which *does* solve that problem, right?
>
>>> However, there are a couple little issues with non-ASCII
>>> text and a *lot* of math differences, many of which say
>>> "*no* convergence: NOTIFY R-core!"....