Comments (19)
I have not encountered this before. What version of c2hs are you using?
from cuda.
Right, I knew I forgot something! :)
-bash-4.1$ c2hs --version
C->Haskell Compiler, version 0.18.2 The shapeless maps, 31 Oct 2014
build platform is "x86_64-linux" <1, True, True, 1>
from cuda.
Okay, I was using c2hs-0.17.2. It appears something changed with the newer c2hs. I'll see if I can get a workaround/fix.
from cuda.
By the way what platform are you running on?
from cuda.
I would suggest just using the older 1.17.2 version of c2hs
so that you can continue working until we sort this problem out.
Thanks for bringing the issue to my attention!
from cuda.
Thanks Trevor, that fixed the problem.
I'm not really running on platform... I partly installed the newest one and just used cabal to install whatever I needed.
I'll shoot you an email by the early next week with some results from our benchmarks and thoughts on Accelerate.
Keep up the good work :)
from cuda.
Thanks! Yes, please do let us know how we can improve Accelerate in any way (and sorry the installation was not as smooth as it should have been).
from cuda.
Submitted as NV Bug ID #1557230
from cuda.
I'll just say that I had similar problems installing accelerate-cuda, where cuda-0.5.1.1 couldn't finish installing. Depending on the c2hs version I would get the OP's error or
c2hs: Errors during expansion of binding hooks:
./Foreign/CUDA/Driver/Marshal.chs:151: (column 15) [ERROR] >>> Unknown identifier!
Cannot find a definition for `cuMemHostRegister' in the header file.
After seeing the nvcc --version
line up there, by installing nvidia-cuda-toolkit everything started working fine.
from cuda.
@vjeranc Do you happen to know which version of nvcc you had installed when you got the error you posted? I try to keep the bindings mostly backwards compatible with old CUDA releases.
from cuda.
@tmcdonell 331.38 was the version of the binary driver I was using, I'm not sure which version of nvcc was present then, currently it's 340.29. nvcc --> 5.5.
I'll try to recreate the issue again.
I hit a wall somewhere and didn't manage to resolve the dependency issues surrounding the accelerate package, so, I'll try again soon.
Although, if it is possible that these errors show up if there's no presence of the nvcc (be it missing installation or missing path) that also might be the reason.
from cuda.
The oldest version of the CUDA toolkit I have on hand is 4.2, which includes cuMemHostRegister
. This is already pretty old, so I wouldn't worry too much about installing very old versions in order to get this information, unless you actually need to use them.
Certainly we should fix the accelerate issues though.
from cuda.
When I use c2hs 0.18.2
I get the error
Preprocessing library cuda-0.6.5.0...
In file included from <built-in>:170:
<command line>:5:29: error: expected comma in macro parameter list
#define C2HS_MIN_VERSION(mj 1
^
<command line>:7:11: warning: ISO C99 requires whitespace after the macro name [-Wc99-extensions]
#define rv) (mj<=0&&mn<=18&&rv<=2)
^
1 warning and 1 error generated.
c2hs: Error during preprocessing custom header file
When I use c2hs 0.17.2
I get the error
Preprocessing library cuda-0.6.5.0...
c2hs: C header contains errors:
/usr/include/stdlib.h:177: (column 46) [ERROR] >>> Syntax error !
The symbol `__OSX_AVAILABLE_BUT_DEPRECATED_MSG' does not fit here.
cabal: Error: some packages failed to install:
cuda-0.6.5.0 failed during the building phase. The exception was:
ExitFailure 1
I am running OS X 10.10 and CUDA 6.5.14.
from cuda.
I haven't upgraded to Yosemite yet.
If you can find the definition of the __OSX_AVAILABLE_BUT_DEPRECATED_MSG
macro that would help. Presumably it has changed since 10.9 and we need to update the dummy implementation here: https://github.com/tmcdonell/cuda/blob/master/cbits/stubs.h#L21
from cuda.
Can't really find a definition, the closest is this (look at the bottom of the file): http://www.opensource.apple.com/source/xnu/xnu-2422.1.72/EXTERNAL_HEADERS/Availability.h
There is a newer Availability.h
on my local computer, but I can't find it online. It looks the same in terms of __OSX_AVAILABLE_BUT_DEPRECATED_MSG
, though.
It seems like what's needed is just a message argument. I am not confident enough with compiler macros to make a pull request, though.
from cuda.
Okay, thanks for chasing that! I should get a change to upgrade to yosemite in the next few days and try it out (hopefully).
from cuda.
Hi,
any progress on this issue yet?
I'm having the same problem as @pnutus.
/usr/include/stdlib.h:177: (column 46) [ERROR] >>> Syntax error ! The symbol
__OSX_AVAILABLE_BUT_DEPRECATED_MSG' does not fit here.`
I'm running osx 10.10, nvcc 6.5, and c2hs 0.17.2.
Thanks,
from cuda.
Hi all,
Sorry I haven't gotten around to this yet, lots of deadlines recently. I'm downloading the Yosemite installer as we speak though, so hopefully will have a fix soon.
from cuda.
Version 0.6.5.1 has been uploaded that fixes compilation on Yosemite.
c2hs has been fixed so that this package will compile c2hs HEAD; that version is currently unreleased, but I can edit the comment on Hackage later. For the time being, the documentation header still advises to use version 0.17.
from cuda.
Related Issues (20)
- Build fails with library profiling HOT 4
- Compilation fails for CUDA-8 [was: ghc 7.10.3 fail to install] HOT 2
- On Windows, the Cabal installer is looking in the wrong place. HOT 5
- Problem with module `Foreign.CUDA.Path' when installing on Windows 8.1 with CUDA-8.0 HOT 38
- Issues with dynamic parallelism? HOT 3
- GHCi only works with Stack with a custom cabal.buildinfo file. HOT 1
- Structure of nvidia-cuda-toolkit seems to have changed in Ubuntu 18.04 HOT 3
- Driver failure on AWS p3.2xlarge instance HOT 18
- Build failure in cuda-0.10.0.0 HOT 3
- Won't compile on Arch Linux HOT 3
- Ubuntu 16.04 + nvidia-cuda-toolkit "Found CUDA toolkit at: /usr" but 'Could not find path: ["/usr/lib64"]' HOT 7
- package revision to restrict Cabal to <3.0 HOT 1
- Compile issues for Cabal 2? HOT 2
- Cannot find a definition for `cuDevicePrimaryCtxRelease' in the header file. HOT 3
- CUDA 11.3 compatibility HOT 4
- rpath linking to cuda toolkit HOT 2
- This Library isn't Compatible with Windows HOT 4
- Porting to CUDA 12.2. HOT 1
- Compilation broken on windows
- Unknown CUDA device compute capability: 8.7 HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cuda.