Re: [Fink-users] libogdi3 and fink

2012-04-03 Thread Kurt Schwehr
I have changed the 10.5-10.6 proj package to force it to go back to 4.7.0 even though it says 4.8.0. Ugly, but it will get us around this incompatible API change. So proj 4.8.0-2 is really 4.7.0 under the hood. -kurt On Mar 28, 2012, at 6:32 AM, Dany Plouffe wrote: I used the first

Re: [Fink-users] libogdi3 and fink

2012-04-03 Thread Alexander Hansen
On 4/3/12 9:38 AM, Kurt Schwehr wrote: I have changed the 10.5-10.6 proj package to force it to go back to 4.7.0 even though it says 4.8.0. Ugly, but it will get us around this incompatible API change. So proj 4.8.0-2 is really 4.7.0 under the hood. -kurt Is there any reason you didn't

Re: [Fink-users] libogdi3 and fink

2012-03-28 Thread Dany Plouffe
I used the first option. It works now. Thank you very much for your help! Dany On 2012-03-27, at 6:40 PM, Alexander Hansen wrote: On 3/27/12 2:50 PM, Dany Plouffe wrote: I installed proj-4.7.0 about 1 month ago on another computer. I still have the file proj-4.7.0.tar.gz on this computer.

[Fink-users] libogdi3 and fink

2012-03-27 Thread Dany Plouffe
Hi, I am trying to install libogdi3 using fink. However, I get an error message (I put it at the end of this message). I ran fink selfupdate, I put only 1 simultaneous build job, and I also tried to reboot the computer. Here are extra informations, included with the error messages I got:

Re: [Fink-users] libogdi3 and fink

2012-03-27 Thread Peter Dyballa
Am 27.3.2012 um 16:36 schrieb Dany Plouffe: /sw/src/fink.build/libogdi3-3.1.5-1007/ogdi-3.1.5/ogdi/include/ecs_util.h:90:22: error: projects.h: No such file or directory Presumingly this is the cause that triggers the next error... Are you able to list the contents of the libogdi3 sources

Re: [Fink-users] libogdi3 and fink

2012-03-27 Thread Alexander Hansen
On 3/27/12 7:36 AM, Dany Plouffe wrote: Hi, I am trying to install libogdi3 using fink. However, I get an error message (I put it at the end of this message). I ran fink selfupdate, I put only 1 simultaneous build job, and I also tried to reboot the computer Here are extra informations,

Re: [Fink-users] libogdi3 and fink

2012-03-27 Thread Peter Dyballa
Am 27.3.2012 um 19:30 schrieb Alexander Hansen: gcc -I.. -I/sw/src/fink.build/libogdi3-3.1.5-1007/ogdi-3.1.5/include/darwin -I/sw/src/fink.build/libogdi3-3.1.5-1007/ogdi-3.1.5/ogdi/include -I/sw/include -I/sw/include -O -fno-common -I/sw/include -c -o ecs_dyna.o ../ecs_dyna.c In file

Re: [Fink-users] libogdi3 and fink

2012-03-27 Thread Alexander Hansen
On 3/27/12 10:25 AM, Peter Dyballa wrote: Am 27.3.2012 um 16:36 schrieb Dany Plouffe: /sw/src/fink.build/libogdi3-3.1.5-1007/ogdi-3.1.5/ogdi/include/ecs_util.h:90:22: error: projects.h: No such file or directory Presumingly this is the cause that triggers the next error... Are you able to

Re: [Fink-users] libogdi3 and fink

2012-03-27 Thread Alexander Hansen
On 3/27/12 2:50 PM, Dany Plouffe wrote: I installed proj-4.7.0 about 1 month ago on another computer. I still have the file proj-4.7.0.tar.gz on this computer. Is there a way to install it without having any conflict with fink? Is there a way fink can pick this file? That would work, and you

Re: [Fink-users] libogdi3 and fink

2012-03-27 Thread Dany Plouffe
I installed proj-4.7.0 about 1 month ago on another computer. I still have the file proj-4.7.0.tar.gz on this computer. Is there a way to install it without having any conflict with fink? Is there a way fink can pick this file? Does it take time to correct the packages on fink usually?

Re: [Fink-users] libogdi3 and fink

2012-03-27 Thread BABA Yoshihiko
Hi, I remember the same problem happened when I tried to update r-cran-rgdal. So, the problem may occur with any package that uses proj. Does this mean like we should keep proj4-4.7.0 as proj4.7? Thanks -- BABA Yoshihiko

Re: [Fink-users] libogdi3 and fink

2012-03-27 Thread Alexander Hansen
On 3/27/12 7:09 PM, BABA Yoshihiko wrote: Hi, I remember the same problem happened when I tried to update r-cran-rgdal. So, the problem may occur with any package that uses proj. Does this mean like we should keep proj4-4.7.0 as proj4.7? Thanks -- BABA Yoshihiko That's an option. Or