Displaying 20 results from an estimated 200 matches similar to: "Problem with psignal.c for Windows builds"
2015 Aug 24
0
Problem with psignal.c for Windows builds
One thing I forgot in my previous message about problems with
psignal.c on Rtools for Windows...
One also needs to change src/gnuwin32/fixed/h/psignal.h
At a minimum, one needs the following changes:
@@ -122,8 +129,8 @@ typedef struct
/* Prototype stuff ***********************************************************/
-int sigsetmask(int signal_Block_MaskNew);
-int
2007 Jan 24
2
[LLVMdev] patch - update libiberty/psignal to latest prototypes.
Hi ,
I needed to apply this patch to get the GCC frontend building on an FC5
x86 box .
[ramana at venglathur gcc]$ svn diff
Index: libiberty/strsignal.c
===================================================================
--- libiberty/strsignal.c (revision 254)
+++ libiberty/strsignal.c (working copy)
@@ -557,8 +557,8 @@
void
psignal (signo, message)
- unsigned signo;
-
2020 Mar 28
0
[klibc:update-dash] dash: system: Disable glibc warning on sigsetmask
Commit-ID: 5c65fe97c9c00feb5ed10598dcd51ef7399be7ff
Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=5c65fe97c9c00feb5ed10598dcd51ef7399be7ff
Author: Herbert Xu <herbert at gondor.apana.org.au>
AuthorDate: Wed, 21 Nov 2018 11:45:04 +0800
Committer: Ben Hutchings <ben at decadent.org.uk>
CommitDate: Sat, 28 Mar 2020 21:42:55 +0000
[klibc] dash: system: Disable
2007 Jan 24
0
[LLVMdev] patch - update libiberty/psignal to latest prototypes.
On Jan 24, 2007, at 4:14 AM, Ramana Radhakrishnan wrote:
> Hi ,
>
> I needed to apply this patch to get the GCC frontend building on an
> FC5
> x86 box .
I am curious, what kind of failure are you seeing ?
Thanks,
-
Devang
2007 Jan 24
1
[LLVMdev] patch - update libiberty/psignal to latest prototypes.
Devang,
On Wed, 2007-01-24 at 10:28 -0800, Devang Patel wrote:
> On Jan 24, 2007, at 4:14 AM, Ramana Radhakrishnan wrote:
>
> > Hi ,
> >
> > I needed to apply this patch to get the GCC frontend building on an
> > FC5
> > x86 box .
>
> I am curious, what kind of failure are you seeing ?
I should have mentioned in the email : Here's my earlier post
2007 Jan 22
0
[LLVMdev] more llvmgcc build issues.
Hi,
Last night's attempt to build llvmgcc4 with svn head ends in this .
This is on an x86 FC5 environment.
/home/ramana/llvm/llvmgccfrontend/llvmgcc4-source/build-llvmgcc/gcc/xgcc
-B/home/ramana/llvm/llvmgccfrontend/llvmgcc4-source/build-llvmgcc/gcc/
-B/home/ramana/llvm/install-llvm/i686-pc-linux-gnu/bin/
-B/home/ramana/llvm/install-llvm/i686-pc-linux-gnu/lib/
-isystem
2007 Feb 06
1
R from SVN fails to build on win32
I get the following error when building R from the subversion server as
well as the latest tarball. I am on Windows XP, and I recently updated
my MinGW installation. It's quite possible I am doing something wrong,
but I am not sure what that might be.
making console.d from console.c
making dataentry.d from dataentry.c
making dynload.d from dynload.c
making edit.d from edit.c
making editor.d
2023 Nov 12
1
Segmentation fault early in compilation of revision 85514
When trying to compile R on Windows 10 64-bit using LTO as I always do, I
encountered a segmentation fault early in the compilation. I am uncertain
as to what it means (please see below for error extract). I am using the
most recent version of Rtools43 (5863) and updated its libraries prior to
starting the build. My EOPTS is " -march=native -pipe -mno-rtm" and my
2024 Jun 30
0
Making use of win32_segv
Hello R-devel,
When checking packages on Windows, a crash of the process looks like a
sudden stop in the output of the child process, which can be very
perplexing for package maintainers (e.g. [1,2]), especially if the
stars are only right on Win-Builder but not on the maintainer's PC.
On Unix-like systems, we get a loud message from the SIGSEGV handler
and (if we're lucky and the memory
2005 Apr 07
1
build rpvm under cygwin
I tried ot build rpvm in my own makefile.
But runs into some linker errors like e.g.
undefined reference to `_R_alloc'
My enviornment looks like this:
CYGWIN
pvm 3.4 compiled under cygwin myself
R installed from the rw2001.exe setup file.
I guess that the R under rw2001.exe was build with
some other compiler?
I then tried to compile R myself under CYGWIN but runs
into the following
1998 Aug 10
0
AFS compilation problems
Hi
I hope this isn't a FAQ, but i've scoured and found nothing.
When compiling samba 1.9.18p8 with AFS 3.4a on solaris 2.6, when I go to
link the binary (smbd) with the stock makefiles, i get:
Undefined first referenced
symbol in file
sigvec /usr/afsws/lib/liblwp.a(iomgr.o)
sigsetmask
2009 Jan 16
1
interrupting R from a GUI
list(...),
I am looking for a way to interrupt R from a callback: specifically,
to interrupt plotting (typically on a cairoDevice, but would be good
if it worked with other devices too). Of course, one can interrupt R
nicely from the console with Ctrl-C (or Esc in Rgui), but I need to do
it from a GUI. Callbacks run in a new thread, so obviously stop() etc
will not work. I tried to look into how
2018 Feb 13
2
R Compilation gets stuck on Windows 64
On Tue, Feb 13, 2018 at 12:22 PM, Indrajit Sen Gupta
<indrajitsg at gmail.com> wrote:
> Hi Avraham,
>
> I tried with the patched version. The same error message.
>
> gcc -std=gnu99 -m64 -shared -s -mwindows -o R.dll R.def console.o dynload.o
> editor.o embeddedR.o extra.o malloc.o opt.o pager.o preferences.o psignal.o
> rhome.o rt_complete.o rui.o run.o shext.o
2010 May 06
2
help on compile r-2.10.0 on 64 bit window
Hi,
I tried to compile R-2.10.0 src on 64 bit window. After install Rtools and wingw-w64 compiler and put it the first of my PATH variable, but i got the following error when i tried to compile. Anything I missed? thank you.
x86_64-w64-mingw32-gcc -std=gnu99 -I../include -I. -I../extra -DHAVE_CONFIG_H -D
R_DLL_BUILD -O3 -Wall -pedantic -DR_ARCH='"x64"' -c malloc.c -o
2018 Feb 13
0
R Compilation gets stuck on Windows 64
I was able to compile the R from the github by running build-r-devel.bat!
Now need to see how to compile it with BLAS.
Regard,
Indrajit
On Tue, Feb 13, 2018 at 5:45 PM, Jeroen Ooms <jeroenooms at gmail.com> wrote:
> On Tue, Feb 13, 2018 at 12:22 PM, Indrajit Sen Gupta
> <indrajitsg at gmail.com> wrote:
> > Hi Avraham,
> >
> > I tried with the patched
2010 Apr 20
0
Building Rblas.dll failing on Windows 7 (64-bit)
I'm currently attempting to build R-2.10.1 from the source on Windows
7 (64-bit version). I've downloaded the latest Rtools (Rtools211.exe)
from the Murdoch-Sutherland site and have done a full install. I've
also downloaded the HTML Help Workshop, MikTeX, and the InnoSetup
installer.
I am not using any 64-bit versions of the tools, such as the
MinGW-w64, or a 64-bit version of TCL
2018 Feb 13
0
R Compilation gets stuck on Windows 64
Hi Avraham,
I tried with the patched version. The same error message.
gcc -std=gnu99 -m64 -shared -s -mwindows -o R.dll R.def console.o dynload.o
editor.o embeddedR.o extra.o malloc.o opt.o pager.o preferences.o psignal.o
rhome.o rt_complete.o rui.o run.o shext.o sys-win32.o system.o dos_wglob.o
dllversion.o ../main/libmain.a ../appl/libappl.a ../nmath/libnmath.a
getline/gl.a
2018 Feb 13
2
R Compilation gets stuck on Windows 64
In the file MkRules.local.in, I see the line: USE_ATLAS = NO which I
believe needs to be changed to YES. But how do I specify the BLAS file
*libopenblas_haswell-r0.2.20.a
*and its location?
Regards,
Indrajit
On Tue, Feb 13, 2018 at 6:41 PM, Indrajit Sen Gupta <indrajitsg at gmail.com>
wrote:
> I was able to compile the R from the github by running build-r-devel.bat!
>
> Now need
2007 Jan 08
1
Cross-compilation of R and ld bug ?
Hello list,
I would like to cross-compile R packages using R 2.4.0. I am working on
Linux Debian and cross-compiled (windows binaries) without problems with
older R version.
I have used the doc of Yan and Rossini in the contributed section of the
R documentation (same version of MinGW...).
When I try to cross-compile R (make R), the procedure stopped and returns :
2012 Mar 31
1
trouble compiling on Windows
Dear R People:
I'm trying to compile R-2.15.0 on a 64 bit Windows machine.
However, I'm getting the following error:
c:\R64\R-2.15.0\src\gnuwin32>set TMPDIR=c:\temp
set TMPDIR=c:\temp
c:\R64\R-2.15.0\src\gnuwin32>make all recommended
make all recommended
make[1]: `MkRules' is up to date.
make[4]: Nothing to be done for `svnonly'.
installing C headers
make[2]: Nothing to