On 1/28/06, Huidae Cho <grass4u@gmail.com> wrote:
Hi,
Since G_asprintf() function is now defined as a macro on some platforms having
asprintf(), test for G_asprintf() in GDAL configure fails. Open the GDAL
configure script and change all G_asprintf strings to G_version.
Hope it helps.
Huidae Cho
Sorry. I was noit aware of G_asprintf use in GDAL configure.
I have changed GRASS library to implement G_asprintf instead of
macro. We can reintroduce the macro when a stable version of GDAL
using a different function will become widely used.
G_version probably is not the best because it is buggy, it is
using pointers instead of pointers to pointers.
What about G_gisinit?
Radim
On Fri, Dec 09, 2005 at 10:51:55AM +0100, Maik Trömel wrote:
> I have forgotten to write which versions I'm running:
> proj: 4.4.9
> geos: 2.1.4
> gdal: 1.3.1
> grass: 6.0.1
> gdal-grass: 1.3.1
> Georg Lösel wrote:
>
> >Hello Maik,
> >
> >>I have installed grass-6.0.1 and now i want to run "./configure
> >configure for GDAL ! Right?
> >
> Right!
>
> >
> >>--with-grass='/.../grass-6.0.1/lib/'
> >>
> >try --with-grass=/usr/local/grass-6.0.1/
> >
> Same problem. Is it possible that I've got the wrong version of one package?
>
> >HTH Georg
> >
>
> Greetings Maik
>
Hi,
Radim Blazek schrieb:
On 1/28/06, Huidae Cho <grass4u@gmail.com> wrote:
Hi,
Since G_asprintf() function is now defined as a macro on some platforms having
asprintf(), test for G_asprintf() in GDAL configure fails. Open the GDAL
configure script and change all G_asprintf strings to G_version.
Hope it helps.
Huidae Cho
Sorry. I was noit aware of G_asprintf use in GDAL configure.
I have changed GRASS library to implement G_asprintf instead of
macro. We can reintroduce the macro when a stable version of GDAL
using a different function will become widely used.
G_version probably is not the best because it is buggy, it is
using pointers instead of pointers to pointers.
What about G_gisinit?
Radim
I had the same problem with gdal and gdal-grass. I
replaced G_asprintf with G_malloc in booth programms
and it worked.
But since the grass-imgaing and gdal issues, i only get segfaults
when using r.in.gdal. The segfaults appear's in a gdal method.
Greets
Soeren
On Fri, Dec 09, 2005 at 10:51:55AM +0100, Maik Trömel wrote:
I have forgotten to write which versions I'm running:
proj: 4.4.9
geos: 2.1.4
gdal: 1.3.1
grass: 6.0.1
gdal-grass: 1.3.1
Georg Lösel wrote:
Hello Maik,
I have installed grass-6.0.1 and now i want to run "./configure
configure for GDAL ! Right?
Right!
--with-grass='/.../grass-6.0.1/lib/'
try --with-grass=/usr/local/grass-6.0.1/
Same problem. Is it possible that I've got the wrong version of one package?
HTH Georg
Greetings Maik
On Mon, Jan 30, 2006 at 10:14:21AM +0100, Radim Blazek wrote:
On 1/28/06, Huidae Cho <grass4u@gmail.com> wrote:
> Hi,
>
> Since G_asprintf() function is now defined as a macro on some platforms having
> asprintf(), test for G_asprintf() in GDAL configure fails. Open the GDAL
> configure script and change all G_asprintf strings to G_version.
>
> Hope it helps.
> Huidae Cho
Sorry. I was noit aware of G_asprintf use in GDAL configure.
I have changed GRASS library to implement G_asprintf instead of
macro. We can reintroduce the macro when a stable version of GDAL
using a different function will become widely used.
G_version probably is not the best because it is buggy, it is
using pointers instead of pointers to pointers.
What about G_gisinit?
I've fixed the bug in CVS. G_gisinit also looks good to me.
Huidae Cho
Radim
> On Fri, Dec 09, 2005 at 10:51:55AM +0100, Maik Trömel wrote:
> > I have forgotten to write which versions I'm running:
> > proj: 4.4.9
> > geos: 2.1.4
> > gdal: 1.3.1
> > grass: 6.0.1
> > gdal-grass: 1.3.1
> > Georg Lösel wrote:
> >
> > >Hello Maik,
> > >
> > >>I have installed grass-6.0.1 and now i want to run "./configure
> > >configure for GDAL ! Right?
> > >
> > Right!
> >
> > >
> > >>--with-grass='/.../grass-6.0.1/lib/'
> > >>
> > >try --with-grass=/usr/local/grass-6.0.1/
> > >
> > Same problem. Is it possible that I've got the wrong version of one package?
> >
> > >HTH Georg
> > >
> >
> > Greetings Maik
> >
>
>
Radim Blazek wrote:
> Since G_asprintf() function is now defined as a macro on some platforms having
> asprintf(), test for G_asprintf() in GDAL configure fails. Open the GDAL
> configure script and change all G_asprintf strings to G_version.
Sorry. I was noit aware of G_asprintf use in GDAL configure.
I have changed GRASS library to implement G_asprintf instead of
macro. We can reintroduce the macro when a stable version of GDAL
using a different function will become widely used.
As G_asprintf() is variadic, a macro probably isn't such a great idea;
variadic macros aren't particularly portable.
Are there any systems out there which provide asprintf() but which
don't provide vasprintf()?
Assuming that vasprintf() is available, it would be better to use the
current G_asprintf() implementation even if there weren't any problems
with using a macro.
--
Glynn Clements <glynn@gclements.plus.com>