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:
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
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,
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
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
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
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?
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
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
