Am 02.05.21 um 19:55 schrieb LuMiWa via freebsd-ports:
> Hi!
>
> I have a problem to build graphics/gdal on FreeBSD-13.0-RELEASE:
> m::seekp' declared here: type mismatch at 1st parameter ('uint64_t'
> (aka 'unsigned long') vs 'GInt64' (aka
On Mon, 3 May 2021 12:42:00 +0200
Matthieu Volat wrote:
> On Sun, 2 May 2021 13:55:45 -0400
> LuMiWa via freebsd-ports wrote:
>
> > Hi!
> >
> > I have a problem to build graphics/gdal on FreeBSD-13.0-RELEASE:
> > m::seekp' declared here: type mismatch
On 03/05/2021 12:42, Matthieu Volat wrote:
Hi, this happens indeed when you build gdal*without* the EXR option when
openexr is present at build time. I guess the off option is not passed
correctly to the configure script?
Hi Mathieu, LuMiWa,
I ran in the very same problem, with the
On Sun, 2 May 2021 13:55:45 -0400
LuMiWa via freebsd-ports wrote:
> Hi!
>
> I have a problem to build graphics/gdal on FreeBSD-13.0-RELEASE:
> m::seekp' declared here: type mismatch at 1st parameter ('uint64_t'
> (aka 'unsigned long') vs 'GIn
On Sun, 2 May 2021 20:14:12 +0200
Loïc Bartoletti wrote:
> Hi,
>
> What's your options? How do you build it?
>
> Thanks.
>
> Loïc
>
I built with the default options. I am using portmaster and I try cd
/usr/oprts/graphics/gdal and make but the same result
--
Hi,
What's your options? How do you build it?
Thanks.
Loïc
Le 02/05/2021 à 19:55, LuMiWa via freebsd-ports a écrit :
Hi!
I have a problem to build graphics/gdal on FreeBSD-13.0-RELEASE:
m::seekp' declared here: type mismatch at 1st parameter ('uint64_t'
(aka 'u
Hi!
I have a problem to build graphics/gdal on FreeBSD-13.0-RELEASE:
m::seekp' declared here: type mismatch at 1st parameter ('uint64_t'
(aka 'unsigned long') vs 'GInt64' (aka 'long long')) virtual void
seekp (uint64_t pos) = 0; ^
exrdataset.cpp:495
On 19/01/2018 09:01, L.Bartoletti wrote:
Hi,
A dummy question, but, I haven't be able to make a simple patch to a
port (graphics/py-gdal).
My patch (using diff -u) is:
--- swig/include/gdal_array.i.orig 2018-01-19
06:46:50.571482000 +0100
+++ swig/include/gdal_array.i
Hi,
A dummy question, but, I haven't be able to make a simple patch to a
port (graphics/py-gdal).
My patch (using diff -u) is:
--- swig/include/gdal_array.i.orig 2018-01-19
06:46:50.571482000 +0100
+++ swig/include/gdal_array.i 2018-01-19 06:46:50.571393000
For some time now, I get the following message, when I use some of the
GDAL tools (graphics/gdal) on FreeBSD HEAD (11.0-CURRENT r278036). For
example, if I try:
#gdalinfo --version
ERROR 1: /lib/libgcc_s.so.1: version GCC_4.6.0 required by
/usr/local/lib/gcc48/libgfortran.so.3 not found
Nobody else seeing this error on recent 10.0-CURRENT (amd64, clang)?
Thanks in advance for any help,
Rainer Hurling
#make -DMAKE_JOBS_UNSAFE=yes
===> License MIT accepted by the user
===> Fetching all distfiles required by p5-Geo-GDAL-1.10.1 for building
===> Extracting for p5-Geo-GD
Am 2013-09-03 16:54, schrieb Rainer Hurling:
Am 03.09.2013 15:11, schrieb Frank Broniewski:
Hi all,
I tried updating Gdal to the latest version on my FreeBSD system
(9.1-RELEASE-p6), but the build fails:
c postgisrasterdataset.cpp -fPIC -DPIC -o
../o/.libs/postgisrasterdataset.o
Am 03.09.2013 15:11, schrieb Frank Broniewski:
> Hi all,
>
> I tried updating Gdal to the latest version on my FreeBSD system
> (9.1-RELEASE-p6), but the build fails:
>
>
> c postgisrasterdataset.cpp -fPIC -DPIC -o
> ../o/.libs/postgisrasterdataset.o
> postgisras
Hi all,
I tried updating Gdal to the latest version on my FreeBSD system
(9.1-RELEASE-p6), but the build fails:
c postgisrasterdataset.cpp -fPIC -DPIC -o ../o/.libs/postgisrasterdataset.o
postgisrasterdataset.cpp: In function 'void GDALRegister_PostGISRaster()':
postgisrasterd
ct: Re: FreeBSD Port: gdal-1.10.0
Am 27.08.2013 23:31 (UTC+1) schrieb Hacker, Benjamin T - GS:
> Dear Sir,
>
> I have attempted to update my Installed Ports. I am having an issue with the
> GDAL port as listed below. Any assistance you can provide would be greatly
> appreciated
Am 27.08.2013 23:31 (UTC+1) schrieb Hacker, Benjamin T - GS:
> Dear Sir,
>
> I have attempted to update my Installed Ports. I am having an issue with the
> GDAL port as listed below. Any assistance you can provide would be greatly
> appreciated!
>
> Thanks!
>
> {
Dear Sir,
I have attempted to update my Installed Ports. I am having an issue with the
GDAL port as listed below. Any assistance you can provide would be greatly
appreciated!
Thanks!
{root@FreeBSD-OSM:/usr/ports/graphics/gdal # make install
. . .
gmake[2]: Entering directory
`/usr/ports
Hi,
I got an error today while I tried to compile py-gdal in a jail where
the ports dir is mounted as read-only. I don't know if that's really the
reason for the compilation failure, but I can't think of anything else.
The error is:
make: don't know how to make sanity-c
Le 09.06.2012 08:49, coder.tuxfamily a écrit :
Le 07.06.2012 15:52, Frank Broniewski a écrit :
Yes, that worked.
I tested it with py-gdal. First I had some problems because there were
some other programs depending gdal-grass (QGIS, Grass GIS) which linked
to the older gdal libs, but after
Le 07.06.2012 15:52, Frank Broniewski a écrit :
Yes, that worked.
I tested it with py-gdal. First I had some problems because there were
some other programs depending gdal-grass (QGIS, Grass GIS) which linked
to the older gdal libs, but after deleting gdal-grass, I could import
the module into
On 8-6-2012 4:43, Sunpoet Hsieh wrote:
> On Thu, Jun 7, 2012 at 2:25 PM, Rainer Hurling wrote:
>> Am 07.06.2012 05:30 (UTC+1) schrieb Sunpoet Po-Chuan Hsieh:
>>>
>>> Hi,
>>
>>
>> Many thanks for this update. What I observed so far:
>>
>>
* Sunpoet Po-Chuan Hsieh (sunp...@freebsd.org) wrote:
> GDAL 1.9.1 was released several days ago.
>
> Please test if it works for you.
> If I don't receive critical feedback, I plan to commit them this
> weekend or next Monday.
I don't use gdal directly so I can'
On Thu, Jun 7, 2012 at 2:25 PM, Rainer Hurling wrote:
> Am 07.06.2012 05:30 (UTC+1) schrieb Sunpoet Po-Chuan Hsieh:
>>
>> Hi,
>
>
> Many thanks for this update. What I observed so far:
>
>
> (1) graphics/gdal builds and installs fine. There is a minor problem:
&g
Yes, that worked.
I tested it with py-gdal. First I had some problems because there were
some other programs depending gdal-grass (QGIS, Grass GIS) which linked
to the older gdal libs, but after deleting gdal-grass, I could import
the module into python and run successfully some tests against
Am 07.06.2012 14:38 (UTC+1) schrieb Frank Broniewski:
Hi,
I can confirm Rainers observation with swig13 and libkml, otherwise gdal
builds and installs fine.
Since I'm new to FreeBSD I still need to figure out what I need to do
with those .shar files, so I can't give an update
Hi,
I can confirm Rainers observation with swig13 and libkml, otherwise gdal
builds and installs fine.
Since I'm new to FreeBSD I still need to figure out what I need to do
with those .shar files, so I can't give an update yet on the language
packages
Frank
Am 07.06.2012 08:2
Am 07.06.2012 05:30 (UTC+1) schrieb Sunpoet Po-Chuan Hsieh:
Hi,
Many thanks for this update. What I observed so far:
(1) graphics/gdal builds and installs fine. There is a minor problem:
dependend port science/libkml (as option) does not configure, if
devel/swig13 is installed.
(2
Hi,
GDAL 1.9.1 was released several days ago.
I'd like to make some changes along with this update [1].
The most important one is about the language bindings.
I decide to move them to separate ports:
- Perl binding: graphics/p5-Geo-GDAL [2]
- Python binding: graphics/py-gdal [3]
- PHP bi
On Mon, 4 Jun 2012, O. Hartmann wrote:
Since the last port update, I get this sticky error in gdal:
PrintGifError() was removed from giflib resulting in libraries that used
it to cause the error. I temp-hack a fix in my set-up by adding a line of
code to one of the files that form giflib
On 06/04/12 21:47, Rainer Hurling wrote:
> On 04.06.2012 21:34 (UTC+2), O. Hartmann wrote:
>> Since the last port update, I get this sticky error in gdal:
>>
>> libtool: compile: g++46 -O3 -pipe -fno-strict-aliasing -march=native
>> -Wl,-rpath=/usr/local/lib/gcc46 -Wa
On 04.06.2012 21:34 (UTC+2), O. Hartmann wrote:
Since the last port update, I get this sticky error in gdal:
libtool: compile: g++46 -O3 -pipe -fno-strict-aliasing -march=native
-Wl,-rpath=/usr/local/lib/gcc46 -Wall
-I/usr/ports/graphics/gdal/work/gdal-1.9.0/port
-I/usr/ports/graphics/gdal
Hi!
> Since the last port update, I get this sticky error in gdal:
It's in graphics/giflib, the latest update to 4.2.0 dropped
the symbol PrintGifError. All the dependent packages need
to be recompiled 8-(
Yes, I know. This is messy.
> libtool: compile: g++46 -O3 -pipe -fno-stri
Since the last port update, I get this sticky error in gdal:
libtool: compile: g++46 -O3 -pipe -fno-strict-aliasing -march=native
-Wl,-rpath=/usr/local/lib/gcc46 -Wall
-I/usr/ports/graphics/gdal/work/gdal-1.9.0/port
-I/usr/ports/graphics/gdal/work/gdal-1.9.0/gcore
-I/usr/ports/graphics/gdal/work
On 04.06.2012 16:47 (UTC+2), Rainer Hurling wrote:
After big update session from weekend, when trying to build
graphics/gdal, I get the following messages:
[...]
gmake[2]: Entering directory
`/usr/ports/graphics/gdal/work/gdal-1.9.0/frmts/gif'
/bin/sh /usr/local/bin/libtool --mode=compile
After big update session from weekend, when trying to build
graphics/gdal, I get the following messages:
[...]
gmake[2]: Entering directory
`/usr/ports/graphics/gdal/work/gdal-1.9.0/frmts/gif'
/bin/sh /usr/local/bin/libtool --mode=compile --tag=CXX c++ -O2 -pipe
-O2 -fno-strict-aliasing
Le 28.05.2012 18:37, Rainer Hurling a écrit :
On 28.05.2012 18:18 (UTC+1), Sunpoet Po-Chuan Hsieh wrote:
Hi,
Here's just a status update.
I'm working on GDAL 1.9.1 update.
That's nice to hear.
I agree.
I plan to move perl/php/python/ruby bindings to separate ports.
On 28.05.2012 18:18 (UTC+1), Sunpoet Po-Chuan Hsieh wrote:
Hi,
Here's just a status update.
I'm working on GDAL 1.9.1 update.
That's nice to hear.
I plan to move perl/php/python/ruby bindings to separate ports.
It also removes dirty python hacks from the master port.
Hi,
Here's just a status update.
I'm working on GDAL 1.9.1 update.
I plan to move perl/php/python/ruby bindings to separate ports.
It also removes dirty python hacks from the master port.
BTW, it seems swig 1.3.40 is enough for GDAL 1.9.1.
I can build ruby-gdal successfully with swig
:
Le 25.05.2012 22:49, Rainer Hurling a écrit :
On 25.05.2012 21:51 (UTC+1), coder.tuxfamily wrote:
Can you try to build the "new" port of gdal ?
I have the same problem with swig for php...
Thanks for the update. It builds and installs fine here on two boxes
with 10.0-CURRENT (am
:
On 25.05.2012 21:51 (UTC+1), coder.tuxfamily wrote:
Can you try to build the "new" port of gdal ?
I have the same problem with swig for php...
Thanks for the update. It builds and installs fine here on two boxes
with 10.0-CURRENT (amd64).
One issue which should be thought ab
:
Can you try to build the "new" port of gdal ?
I have the same problem with swig for php...
Thanks for the update. It builds and installs fine here on two boxes
with 10.0-CURRENT (amd64).
One issue which should be thought about before updating gdal in the
ports:
Does gdal-1.9.1 re
Le 27.05.2012 09:17, Rainer Hurling a écrit :
On 26.05.2012 18:41 (UTC+1), Rainer Hurling wrote:
On 26.05.2012 17:49 (UTC+2), coder.tuxfamily wrote:
Le 25.05.2012 22:49, Rainer Hurling a écrit :
On 25.05.2012 21:51 (UTC+1), coder.tuxfamily wrote:
Can you try to build the "new" po
Le 26.05.2012 18:41, Rainer Hurling a écrit :
On 26.05.2012 17:49 (UTC+2), coder.tuxfamily wrote:
Le 25.05.2012 22:49, Rainer Hurling a écrit :
On 25.05.2012 21:51 (UTC+1), coder.tuxfamily wrote:
Can you try to build the "new" port of gdal ?
I have the same problem with sw
On 26.05.2012 17:49 (UTC+2), coder.tuxfamily wrote:
Le 25.05.2012 22:49, Rainer Hurling a écrit :
On 25.05.2012 21:51 (UTC+1), coder.tuxfamily wrote:
Can you try to build the "new" port of gdal ?
I have the same problem with swig for php...
Thanks for the update. It builds and ins
Le 25.05.2012 22:49, Rainer Hurling a écrit :
On 25.05.2012 21:51 (UTC+1), coder.tuxfamily wrote:
Can you try to build the "new" port of gdal ?
I have the same problem with swig for php...
Thanks for the update. It builds and installs fine here on two boxes
with 10.0-CURRENT (am
On 25.05.2012 21:51 (UTC+1), coder.tuxfamily wrote:
Can you try to build the "new" port of gdal ?
I have the same problem with swig for php...
Thanks for the update. It builds and installs fine here on two boxes
with 10.0-CURRENT (amd64).
One issue which should be thought ab
Can you try to build the "new" port of gdal ?
I have the same problem with swig for php...
Le 25.05.2012 10:29, Rainer Hurling a écrit :
On 23.05.2012 18:37 (UTC+1), Rainer Hurling wrote:
On 23.05.2012 18:22 (UTC+1), coder.tuxfamily wrote:
OK, I think I get it. This failur
On 23.05.2012 18:37 (UTC+1), Rainer Hurling wrote:
On 23.05.2012 18:22 (UTC+1), coder.tuxfamily wrote:
OK, I think I get it. This failure does not happen, if swig is not
installed. Then it builds and installs fine.
I tried to install gdal-1.9.0 on another 10.0-CURRENT box and it fails
tested three cases:
(1) No swig installed -> gdal 1.9.0 builds and installs fine
(2) swig 1.3.40 installed -> the build breaks, see older mails
(3) swig 2.0.4 installed -> gdal 1.9.0 builds and installs fine
So we only have to take care that swig 1.3.40 is not installed.
/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
OK. Maybe inclue the swig dependancy into the Makefile.
I try to port gdal 1.9.1
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.o
-pipe -O2 -fno-strict-aliasing -pipe -msse3 -Wall
-Wdeclaration-after-statement -DOGR_ENABLED -I/usr/local/include
-I/usr/ports/graphics/gdal/work/gdal-1.9.0/port -I/usr/local/include
-I/usr/local -I/usr/local/include -I/usr/local/include -I/usr/local
-I/usr/local/include -I/usr/local -I/usr/local
-pipe -O2 -fno-strict-aliasing -pipe -msse3 -Wall
-Wdeclaration-after-statement -DOGR_ENABLED -I/usr/local/include
-I/usr/ports/graphics/gdal/work/gdal-1.9.0/port -I/usr/local/include
-I/usr/local -I/usr/local/include -I/usr/local/include -I/usr/local
-I/usr/local/include -I/usr/local -I/usr/local
-Wdeclaration-after-statement -DOGR_ENABLED -I/usr/local/include
-I/usr/ports/graphics/gdal/work/gdal-1.9.0/port -I/usr/local/include
-I/usr/local -I/usr/local/include -I/usr/local/include -I/usr/local
-I/usr/local/include -I/usr/local -I/usr/local/include
-I/usr/local/include -I/usr/local/include
I have rewrote the patch.
Maybe with this new patch...
diff -ruN /usr/ports/graphics/gdal/files/patch-configure
gdal/files/patch-configure
--- /usr/ports/graphics/gdal/files/patch-configure 2012-05-19
12:04:43.0 +0200
+++ gdal/files/patch-configure 2012-05-22 19:48:35.0
On 22.05.2012 18:50 (UTC+1), coder.tuxfamily wrote:
What's your make config ?
#make showconfig
===> The following configuration options are available for gdal-1.9.0:
CFITSIO=off "FITS support"
CURL=off "Curl support"
ECW=on "ECW & JPEG2000
What's your make config ?
What's your "uname -a" ?
Thank you
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
21.05.2012 22:13, Rainer Hurling a écrit :
On 21.05.2012 21:37 (UTC+1), coder.tuxfamily wrote:
Hello,
It's a problem know by GDAL.
In the 1.9.0 with PGSQL, gdal don't build because of include in
cpl_recode_iconv.cpp.
You can corrige this with include "${CPPFLAGS}" in confi
Seems to be a problem with python.
Here the diff that i made yesterday.
Courtesly.
Le 21.05.2012 22:13, Rainer Hurling a écrit :
On 21.05.2012 21:37 (UTC+1), coder.tuxfamily wrote:
Hello,
It's a problem know by GDAL.
In the 1.9.0 with PGSQL, gdal don't build because of
On 21.05.2012 21:37 (UTC+1), coder.tuxfamily wrote:
Hello,
It's a problem know by GDAL.
In the 1.9.0 with PGSQL, gdal don't build because of include in
cpl_recode_iconv.cpp.
You can corrige this with include "${CPPFLAGS}" in configure files.
You can see the
Hello,
It's a problem know by GDAL.
In the 1.9.0 with PGSQL, gdal don't build because of include in
cpl_recode_iconv.cpp.
You can corrige this with include "${CPPFLAGS}" in configure files.
You can see the trac on OSGeo : http://trac.osgeo.org/gdal/ticket/4525
That
Thanks for the update of graphics/gdal to version 1.9.0.
It builds fine on 9.0 (amd64), but fails on 10.0-CURRENT (amd64):
[..snip..]
libtool: compile: c++ -O2 -pipe -O2 -fno-strict-aliasing -pipe -msse3
-Wall -DOGR_ENABLED -I/usr/local/include
-I/usr/ports/graphics/gdal/work/gdal-1.9.0/port
On 22.02.2012 22:37 (UTC+1), Rainer Hurling wrote:
On 22.02.2012 22:27 (UTC+1), Peter Jeremy wrote:
On 2012-Feb-21 14:51:50 -0500, Steve Wills wrote:
Is it correct to use portmaster -o graphics/giflib graphics/libungif
Looks OK to me.
And then rebuild all ports that used libungif.
And the
On Wednesday 22 February 2012 15:27:09 Peter Jeremy wrote:
> On 2012-Feb-21 14:51:50 -0500, Steve Wills wrote:
> >> Is it correct to use portmaster -o graphics/giflib graphics/libungif
> >
> >Looks OK to me.
>
> And then rebuild all ports that used libungif.
>
> >> And thew next question is I ha
On 22.02.2012 22:27 (UTC+1), Peter Jeremy wrote:
On 2012-Feb-21 14:51:50 -0500, Steve Wills wrote:
Is it correct to use portmaster -o graphics/giflib graphics/libungif
Looks OK to me.
And then rebuild all ports that used libungif.
And thew next question is I have in /var/db/pgs bot giflib
On 2012-Feb-21 14:51:50 -0500, Steve Wills wrote:
>> Is it correct to use portmaster -o graphics/giflib graphics/libungif
>
>Looks OK to me.
And then rebuild all ports that used libungif.
>> And thew next question is I have in /var/db/pgs bot giflib and libingif.
>> How can I find whic one is in
> I saw new gdal in ports...
>
Yes, the graphics/gdal port was updated to use giflib.
> My question is: in the /usr/ports/UPDATING is first uninstall libungif and
> than install giflib and reinstall all ports.
> Is it correct to use portmaster -o graphics/giflib graphics/libungif
I saw new gdal in ports...
My question is: in the /usr/ports/UPDATING is first uninstall libungif and
than install giflib and reinstall all ports.
Is it correct to use portmaster -o graphics/giflib graphics/libungif
And thew next question is I have in /var/db/pgs bot giflib and libingif.
How can
Am 21.02.2012 14:40 (UTC+1) schrieb Jerry:
On Tue, 21 Feb 2012 08:39:38 +0100
Rainer Hurling articulated:
Dear list,
after changing from graphics/ungif to graphics/giflib there is a
problem with building graphics/gdal. Because other ports depending on
it, this should be corrected as soon as
On Tue, 21 Feb 2012 08:39:38 +0100
Rainer Hurling articulated:
> Dear list,
>
> after changing from graphics/ungif to graphics/giflib there is a
> problem with building graphics/gdal. Because other ports depending on
> it, this should be corrected as soon as possible, I think.
Dear list,
after changing from graphics/ungif to graphics/giflib there is a problem
with building graphics/gdal. Because other ports depending on it, this
should be corrected as soon as possible, I think.
The patch could be something like this:
--- Makefile.orig 2012-02-08 07:52
"coder.tuxfamily" writes:
> There is a new version of Gdal (graphics/gdal) 1.9.0.
> Here the diff, seems works but don't have time to make all tests.
[...]
> @@ -17,7 +16,7 @@
> COMMENT= A translator library for geospatial data formats
>
> CONFIGURE_ARGS=
coder.tuxfamily wrote on 13.01.2012 23:02:
Hi,
There is a new version of Gdal (graphics/gdal) 1.9.0.
Here the diff, seems works but don't have time to make all tests.
best regards
1. the diff is inverted.
2. this port has it's maintainer
3. please submit corrected patch a
On 19.07.2010 11:51 (UTC+1), Rainer Hurling wrote:
gdal version 1.7.2 was released on April, 23th. There are many
improvements against version 1.6.0 (from December 2008) which we found
in the ports.
Are there any plans to update graphics/gdal in the next time?
Thanks for updating :-)
Rainer
Because of getting no response on the first posting until now, I tried
to make a suggestion for a patch. Sorry for answering to myself.
On 19.07.2010 11:51 (UTC+1), Rainer Hurling wrote:
gdal version 1.7.2 was released on April, 23th. There are many
improvements against version 1.6.0 (from
graphics/gdal can be configured with many options.
When option 'python' is checked ON, the PORTREVISION will be hardcoded
to 4, see line 192 of Makefile (instead of 9 for the most recent version
from today).
On side-effect is, that then this port will not be seen by portupgrade
e
gdal version 1.7.2 was released on April, 23th. There are many
improvements against version 1.6.0 (from December 2008) which we found
in the ports.
Are there any plans to update graphics/gdal in the next time?
If I could help (like testing) in some way please let me know.
Thanks in advance
76 matches
Mail list logo
