Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

issue with Apple's "C" headers #7

Closed
GoogleCodeExporter opened this issue Mar 13, 2015 · 1 comment
Closed

issue with Apple's "C" headers #7

GoogleCodeExporter opened this issue Mar 13, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. download and install grass dependence for osx [1]
2. checkout grass source code from SVN repository [2]
3. configure [3] & make (you'll need fftw (in /usr/local/) and tcltk.framework) 
[4]


What is the expected output? What do you see instead?

this is the ctypsgen  log errors during the build [5]
i tried to patch ctypesgen with this patch [6] 

What version of the product are you using? On what operating system?
i'm using the lates ctypsgen SVN revision on Mac OS X 10.6.3

Please provide any additional information below.

Recently GRASS GIS switched from swig to ctype+ctypsgen
unluky the build ends with error (see logs) 
looks like an issue with Apple's "C" headers being incompatible
with anything other than Apple's version of gcc. 

[1] Unix Compatibility Frameworks http://www.kyngchaos.com/software/frameworks 
[2] svn checkout https://svn.osgeo.org/grass/grass/trunk grass_trunk
[3] http://www.geofemengineering.it/data/grass_configure
[4] http://www.geofemengineering.it/data/ext_dep.7z
[5] http://www.geofemengineering.it/data/grass_lib_python_osx_log.txt
[6] http://www.geofemengineering.it/data/preprocessor.py

please contact me directly i will be happy to test patch
or to provide any kind of test and detailed log
i'm sure this fix will be usefull for all the Ctypsgen OSX users

thanks!

Original issue reported on code.google.com by massimod...@gmail.com on 3 Jun 2010 at 7:07

@olsonse
Copy link
Collaborator

olsonse commented Dec 5, 2019

I'm going to close this because there is way too little detail here to do anything with and the wayback machine did not archive the content of any of the issues (and I'm not sure where to find it otherwise).

@olsonse olsonse closed this as completed Dec 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants