search for: snowleopard

Dears, I have a problem to install JRI on a Macintosh with Snowleopard OS. <configure> runs without error message but <make> gives the following error message: $ make make -C src JRI.jar gcc -arch i386 -arch ppc -c -o Rengine.o Rengine.c -g -Iinclude -fno-common -I/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/include -I/System/Librar...

Dear John Fox, I am using Snowleopard with a Intel Core 2 Duo processor. I have installed the R console and followed your steps at: http://socserv.mcmaster.ca/jfox/Misc/Rcmdr/installation-notes.html but every time I try "library(Rcmdr)" it loads Tcl/tk infinitely. I have tried loading "library(tcltk)" by itself...

...with the darwin unwinder. You cannot mix and match the two. One of the lines from the bugzilla comments shows: /sw/lib/gcc4.5/lib/libgcc_s.1.dylib (compatibility version 1.0.0, being used. That will not work. All of the libgcc_s.dylib functionality has been subsumed into libSystem.dylib on SnowLeopard (darwin10). The gcc compiler that shipped with SnowLeopard leaves the -lgcc_s off the link line when targeting SnowLeopard. If there is a newer libgcc_s with new functions added, then the link line needs to change to "-lSystem -lgcc_s", that way the linker will find the most...

I realize this is off-topic for the list, but I thought all the darwin developers here might want to be aware of this. The current regressions in gcc trunk regarding exception handling has been escalated to a P1 in order to attract darwin developers to the issue... http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41260#c31 If these regressions aren't fixed before gcc 4.5's release, it appears

...inder. You cannot mix and match the two. One of the lines > from the bugzilla comments shows: > /sw/lib/gcc4.5/lib/libgcc_s.1.dylib (compatibility version 1.0.0, > being used. That will not work. All of the libgcc_s.dylib > functionality has been subsumed into libSystem.dylib on SnowLeopard > (darwin10). The gcc compiler that shipped with SnowLeopard leaves the > -lgcc_s off the link line when targeting SnowLeopard. If there is a > newer libgcc_s with new functions added, then the link line needs to > change to "-lSystem -lgcc_s", that way the linker wil...

...ifferently from apple's and and therefore can interfere with other GUI applications' use of dfonts on Mac OS X. (that unfortunately means the most common typefaces like Time and Helvetica!). While doing that, I found that the official R-3.1.*-mavericks.pkg are crippled, compared to R-3.1.*-snowleopard.pkg. They have tiff functionality missing. Here are the sizes of the official binaries': 3918832 ./R-3.1.2-snowleopard/R.framework/Versions/3.1/Resources/library/grDevices/libs/cairo.so 3778144 ./R-3.0.3/R.framework/Versions/3.0/Resources/library/grDevices/libs/cairo.so 3170596 ./R-3.1.2-maver...

...on to darwin that might be confusing things. Darwin uses two-level-name-space. That means that at build time the linker records where it found each dylib (SO) symbol. (It records the path the dylib supplied as its "install name" - not just the leafname as SO_NEEDED does.) On a SnowLeopard system you *can* link against /usr/lib/libgcc_s. 10.5.dylib, but the linker will not record any symbols coming from it. In fact, the link order does not matter. That is because /usr/ lib/libgcc_s.10.5.dylib has magic symbols in it that say if you are targeting 10.6 then _Unwind_Resume (and...

Hello, all. I have a two Mac mini 4.1 (mid 2010: Intel Core 2 Duo P8600, 4Gb RAM, NVIDIA GeForce 320M, Intel HDA) One has Snowleopard 10.6.8 (32-bit) installed, another - Lion 10.7.2 (64-bit). I have installed Wine 1.3.31 from MacPorts repository on both of them and attempts to run Civilization 4 Complete Edition. I've made dll substitution specific for this game using winetrics (msxml3, vcrun2005). On Snowleopard install...

When is the R-3.2.5 binary for Mac OS X likely to show up? Mick Jordan

On 5/2/16 4:25 PM, David Winsemius wrote: >> On May 2, 2016, at 3:45 PM, Mick Jordan <mick.jordan at oracle.com> wrote: >> >> When is the R-3.2.5 binary for Mac OS X likely to show up? > Where did you look? I see both Mavericks and SnowLeopard fork binaries with or without r.app GUI at http://r.research.att.com/ > > I've been using the 3.3.0 RC for a while with only relative minor and mostly expected difficulties relating to packages that have external dependencies. > > I was looking at https://cran.r-project.org/ which o...

...pported). I am using the 1.1.29 source version.. I have been following the guide for building on Mac and 64-bit WINE at: http://wiki.winehq.org/MacOSX/Building http://wiki.winehq.org/Wine64 I get the following error when I try to make a build (see below). Has anyone successfully built WINE on SnowLeopard with both 32-bit and 64-bit runtime libraries. For that matter, has anyone gotten a 64-bit enabled build of WINE to take on SL? Cheers, Thomas gcc -m64 -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Ww...

...s to that folder via CIFS. I can still see the folder from its parent directory, but can't browse into it via CIFS. I can still browse the folder on the server's command line. The XP Pro client fails with the message: *"The data area passed to a system call is too small"* The OSX Snowleopard client just gives a silent fail. I click in, and nothing happens. When I mv the same "broken" folder to an EXT4 file system via the server's command line, I can repair the acls using: get acls: /usr/local/samba/bin/samba-tool ntacl get --as-sddl /${ZPOOL}/Lou/stuff/ returns: ?O:S-1-...

ralniv wrote: > Below are my instructions for getting a libgsm friendly version of Wine compiled on SnowLeopard. I assume that you already have wine-devel installed and configured to your liking. I also assume that you use MacPorts for package management. > > [1] Uninstall wine-devel > > Code: > sudo port uninstall wine-devel > > > > [2] Edit the portfile for wine-devel. It...

Works for me. Presumably #including <cassert> will fix it though? On Sep 26, 2008, at 4:30 PMPDT, Mike Stump wrote: > I'm seeing a build failure... > > In file included from /Volumes/mrs5/net/llvm/llvm/lib/VMCore/ > Attributes.cpp:14: > /Volumes/mrs5/net/llvm/llvm/include/llvm/Attributes.h: In member > function 'llvm::Attributes >

Are there any results for the SPEC2000 benchmarks using llvm with and without LTO? It would be interesting to know how the current LTO in llvm compares to the results being seen in current gcc trunk with their LTO... http://gcc.gnu.org/ml/gcc/2009-10/msg00155.html It would appear that the gcc LTO implementation is finally showing results (although with a lot of wrong code results). I assume we

Hi all, not sure if this is the right place to ask this but R not being such a "mainstream" app, can't find the answer anywhere. I plan to upgrade to Snow asap and just wondering if anyone else has already and has successfully used R on Mac OSX 10.6. If so, what version? and is it running in 64 bit mode? Thanks in advance, George.

Below are my instructions for getting a libgsm friendly version of Wine compiled on SnowLeopard. I assume that you already have wine-devel installed and configured to your liking. I also assume that you use MacPorts for package management. [1] Uninstall wine-devel Code: sudo port uninstall wine-devel [2] Edit the portfile for wine-devel. It is located at: /opt/local/var/macports/sourc...

I just tried the "qtgears" OpenGL demo from http://lab.bachem-it.com/opengl/qtgears (source is included) on my MacBook and I got this error: DIAG: apple_glx_create_context: ac 0x41931730 ac->context_obj 0x4104ce00 DIAG: apple_glx_drawable_create: new drawable 0x4088a000 DIAG: create_surface: created a surface for drawable 0x600010 with uid 153 DIAG: surface_make_current:

...while building Network UPS Tools. >> Full details are available at: >> http://buildbot.networkupstools.org/public/nut/builders/MacOSX-10.6-x86/builds/9 >> >> Buildbot URL: http://buildbot.networkupstools.org/public/nut/ >> >> Buildslave for this Build: minime-snowleopard >> >> Build Reason: scheduler >> Build Source Stamp: [branch trunk] 3447 >> Blamelist: aquette,clepple-guest >> >> BUILD FAILED: failed configure > > Charles, > > configuration is staling on the very first autogen step (Ie, Augeas > ups.conf le...

On Monday 15 February 2010 20:46:52 Daniel Dunbar wrote: > > BTW, how sure are we that all these are gcc issues and not some incorrect > > code somewhere that triggers undefined behavior? > > Medium sure? :) > > I spent a little while hunting this particular bug, and it acted very > much like a compiler bug. I never narrowed it down to a test case, > though. Is there