I would like to compile Grass with freetype support, but the configure fails:
checking for location of FreeType includes...
checking for ft2build.h... no
configure: error: *** Unable to locate FreeType includes.
I'm using Gentoo and I have installed freetype package, and the ft2build.h
file is in the /usr/include directory, so I don't understand why Grass
doesn't find it, even if I add --with-freetype-includes=/usr/include to the
configure script.
I would like to compile Grass with freetype support, but the configure fails:
checking for location of FreeType includes...
checking for ft2build.h... no
configure: error: *** Unable to locate FreeType includes.
I'm using Gentoo and I have installed freetype package, and the ft2build.h
file is in the /usr/include directory, so I don't understand why Grass
doesn't find it, even if I add --with-freetype-includes=/usr/include to the
configure script.
You need --with-freetype-includes=/usr/include/freetype2.
ft2build.h simply includes <freetype/config/ftheader.h>. In order to
be able to find that header, /usr/include/freetype2 has to be added to
the compiler's include path.
Note that header checks don't simply try to locate a file with a given
name, they try to use it (i.e. preprocess a test program which
includes the specified header).
More generally, if a configure test fails, the contents of the
config.log file will provide an indication of exactly what the test
did and any error messages which it generated.
péntek 19 május 2006 11.43 dátummal Glynn Clements ezt írta:
Stefe-Bán István wrote:e-A
> I would like to compile Grass with freetype support, but the configure
fails:
> checking for location of FreeType includes...
> checking for ft2build.h... no
> configure: error: *** Unable to locate FreeType includes.
>
> I'm using Gentoo and I have installed freetype package, and the ft2build.h
> file is in the /usr/include directory, so I don't understand why Grass
> doesn't find it, even if I add --with-freetype-includes=/usr/include to
the
> configure script.
You need --with-freetype-includes=/usr/include/freetype2.
ft2build.h simply includes <freetype/config/ftheader.h>. In order to
be able to find that header, /usr/include/freetype2 has to be added to
the compiler's include path.
Note that header checks don't simply try to locate a file with a given
name, they try to use it (i.e. preprocess a test program which
includes the specified header).
More generally, if a configure test fails, the contents of the
config.log file will provide an indication of exactly what the test
did and any error messages which it generated.
why You dont use ebuilds? GRASS ebuild on Gentoo system contains all
information for sucessfull compilation on Genoo boxes. If You wish to compile
GRASS from CVS, You still can look for Gentoo specific workarounds in ebuild
file. Look at something
like /usr/portage/sci-geosciences/grass/grass-X.Y.Z.ebuild
WBR,
Maris, GRASS 5.7.x, 6.0 ebuild author.
On Friday 19 May 2006 14:07, Stefán István wrote:
péntek 19 május 2006 11.43 dátummal Glynn Clements ezt írta:
> Stefe-Bán István wrote:e-A
>
> > I would like to compile Grass with freetype support, but the configure
hétfő 22 május 2006 12.44 dátummal Māris Nartišs ezt írta:
Hi,
why You dont use ebuilds? GRASS ebuild on Gentoo system contains all
information for sucessfull compilation on Genoo boxes. If You wish to
compile
GRASS from CVS, You still can look for Gentoo specific workarounds in ebuild
file. Look at something
like /usr/portage/sci-geosciences/grass/grass-X.Y.Z.ebuild
Because I want to use opendwg support, and in the ebuild there is no use flag
for it.
Or is there any way to compile the ebuild with opendwg support?
hétfő 22 május 2006 12.44 dátummal Māris Nartišs ezt írta:
Hi,
why You dont use ebuilds? GRASS ebuild on Gentoo system contains all information for sucessfull compilation on Genoo boxes. If You wish to
compile
GRASS from CVS, You still can look for Gentoo specific workarounds in ebuild file. Look at something like /usr/portage/sci-geosciences/grass/grass-X.Y.Z.ebuild
Because I want to use opendwg support, and in the ebuild there is no use flag for it.
Or is there any way to compile the ebuild with opendwg support?
Thanks,
Istvan
ps: sorry for answering a _little bit_ late
Hi, have you tried using "--with-freetype-includes=/usr/include/freetype2"?
Because You can't just emerge opendwg, there is no opendwg use flag for GRASS
ebuild. I don't think this would change in future until there will be some
easyer way to get opendwg.
To get opendwg support You must take same steps as in other disrtos to get
unsupported feature - download source, ./configure && make && make install.
Maris.
On Wednesday 23 August 2006 15:14, Stefán István wrote:
Because I want to use opendwg support, and in the ebuild there is no use
flag for it.
Or is there any way to compile the ebuild with opendwg support?
szerda 23 augusztus 2006 17.12 dátummal Pericles S. Nacionales ezt írta:
Stefán István wrote:
> hétfő 22 május 2006 12.44 dátummal Māris Nartišs ezt írta:
>> Hi,
>>
>> why You dont use ebuilds? GRASS ebuild on Gentoo system contains all
>> information for sucessfull compilation on Genoo boxes. If You wish to
> compile
>> GRASS from CVS, You still can look for Gentoo specific workarounds in
ebuild
>> file. Look at something
>> like /usr/portage/sci-geosciences/grass/grass-X.Y.Z.ebuild
>
> Because I want to use opendwg support, and in the ebuild there is no use
flag
> for it.
> Or is there any way to compile the ebuild with opendwg support?
>
> Thanks,
> Istvan
>
> ps: sorry for answering a _little bit_ late
Hi, have you tried using "--with-freetype-includes=/usr/include/freetype2"?
szerda 23 augusztus 2006 17.17 dátummal Māris Nartišs ezt írta:
Because You can't just emerge opendwg, there is no opendwg use flag for
GRASS
ebuild. I don't think this would change in future until there will be some
easyer way to get opendwg.
To get opendwg support You must take same steps as in other disrtos to get
unsupported feature - download source, ./configure && make && make install.
Hello,
I understand this, but I think an ebuild for opendwg could be made. There are
ebuilds for other commercial stuffs also, with the fetch restricted flag.
I understand this, but I think an ebuild for opendwg could be made. There are
ebuilds for other commercial stuffs also, with the fetch restricted flag.
I don't think it's possible. Please look at Open Design site for license
details. Each eventuall user must *sign* an agreement with Open Design
Alliance to be allowed to use their software and nobody is allowed to
re-distribute their software in either source or binary form. The only
"free" thing about OpenDWG/DGN is that it costs no money, in it's
Associate Membership form.
csütörtök 24 augusztus 2006 10.39 dátummal Maciej Sieczka ezt írta:
Stefán István napisa?(a):
> I understand this, but I think an ebuild for opendwg could be made. There
are
> ebuilds for other commercial stuffs also, with the fetch restricted flag.
I don't think it's possible. Please look at Open Design site for license
details. Each eventuall user must *sign* an agreement with Open Design
Alliance to be allowed to use their software and nobody is allowed to
re-distribute their software in either source or binary form. The only
"free" thing about OpenDWG/DGN is that it costs no money, in it's
Associate Membership form.
Yes, but making an ebuild which install the libraries only if the user has
downloaded it before (and downloading means also signing the agreement)
doesn't mean re-distributing the software. It only makes simplier to install
it, and makes possible for other ebuilds to know if these libraries are
installed or not.
But I think that adding an opendwg use flag for grass ebuild doesn't even mean
to have to be an ebuild for opendwg too. Can't it work so that if the user
specifies the opendwg useflag for the grass ebuild, you simply add the
appropriate switchies to the configure script, assuming that the libraries
are installed on the system already?
csütörtök 24 augusztus 2006 10.39 dátummal Maciej Sieczka ezt írta:
Stefán István napisa?(a):
I understand this, but I think an ebuild for opendwg could be made. There
are
ebuilds for other commercial stuffs also, with the fetch restricted flag.
I don't think it's possible. Please look at Open Design site for license
details. Each eventuall user must *sign* an agreement with Open Design
Alliance to be allowed to use their software and nobody is allowed to
re-distribute their software in either source or binary form. The only
"free" thing about OpenDWG/DGN is that it costs no money, in it's
Associate Membership form.
Yes, but making an ebuild which install the libraries only if the user has
downloaded it before (and downloading means also signing the agreement)
Not in case of Open Design software. See their site. You have to fax or
email them the agreement whith your hand-written signature. Then you get
a login+pass to download the software. Neat, isn't it?
doesn't mean re-distributing the software. It only makes simplier to install
it, and makes possible for other ebuilds to know if these libraries are
installed or not.
But I think that adding an opendwg use flag for grass ebuild doesn't even mean
to have to be an ebuild for opendwg too. Can't it work so that if the user
specifies the opendwg useflag for the grass ebuild, you simply add the
appropriate switchies to the configure script, assuming that the libraries
are installed on the system already?
I'm no Gentoo user, dunno. Just wanted to clearup details about Open
Design licensing.
csütörtök 24 augusztus 2006 11.46 dátummal Maciej Sieczka ezt írta:
Stefán István napisa?(a):
> csütörtök 24 augusztus 2006 10.39 dátummal Maciej Sieczka ezt írta:
>> Stefán István napisa?(a):
>>
>>> I understand this, but I think an ebuild for opendwg could be made.
There
> are
>>> ebuilds for other commercial stuffs also, with the fetch restricted
flag.
>> I don't think it's possible. Please look at Open Design site for license
>> details. Each eventuall user must *sign* an agreement with Open Design
>> Alliance to be allowed to use their software and nobody is allowed to
>> re-distribute their software in either source or binary form. The only
>> "free" thing about OpenDWG/DGN is that it costs no money, in it's
>> Associate Membership form.
>
> Yes, but making an ebuild which install the libraries only if the user has
> downloaded it before (and downloading means also signing the agreement)
Not in case of Open Design software. See their site. You have to fax or
email them the agreement whith your hand-written signature. Then you get
a login+pass to download the software. Neat, isn't it?
Yes, I know, I made this procedure also to get the libraries, but I think this
doesn't prevent the grass gentoo package to have an opendwg useflag.
> doesn't mean re-distributing the software. It only makes simplier to
install
> it, and makes possible for other ebuilds to know if these libraries are
> installed or not.
> But I think that adding an opendwg use flag for grass ebuild doesn't even
mean
> to have to be an ebuild for opendwg too. Can't it work so that if the
user
> specifies the opendwg useflag for the grass ebuild, you simply add the
> appropriate switchies to the configure script, assuming that the libraries
> are installed on the system already?
I'm no Gentoo user, dunno. Just wanted to clearup details about Open
Design licensing.
Does anyone know who makes the Grass Gentoo ebuild?
>>> I understand this, but I think an ebuild for opendwg could be made. There
> are
>>> ebuilds for other commercial stuffs also, with the fetch restricted flag.
>> I don't think it's possible. Please look at Open Design site for license
>> details. Each eventuall user must *sign* an agreement with Open Design
>> Alliance to be allowed to use their software and nobody is allowed to
>> re-distribute their software in either source or binary form. The only
>> "free" thing about OpenDWG/DGN is that it costs no money, in it's
>> Associate Membership form.
>
> Yes, but making an ebuild which install the libraries only if the user has
> downloaded it before (and downloading means also signing the agreement)
Not in case of Open Design software. See their site. You have to fax or
email them the agreement whith your hand-written signature. Then you get
a login+pass to download the software. Neat, isn't it?
That doesn't preclude the possibility of having an ebuild for it. E.g.
the quake4-data ebuild has an empty SRC_URI, and a src_install()
method which just copies files from the DVD.
Also, even if you don't have an ebuild for OpenDWG, you can still have
a USE flag for it in the GRASS ebuild; you just lose the dependency
management.
currently GRASS on Gentoo is almost unmaintained. First GRASS ebuild for
5.7/6.0 was made by me. Now ebuilds are submitted by community trough
bugzilla system, but current maintainer (nerdboy) is not very intrested in
GIS (and doesn't know OS GIS related problems) and strictly follows Gentoo
guidelines - I had problems with getting simple GRASS related fixes to ebuild
accepted.
I don't think that there will somebody push opendwg ebuild and related grass
flag.
currently GRASS on Gentoo is almost unmaintained. First GRASS ebuild for
5.7/6.0 was made by me. Now ebuilds are submitted by community trough
bugzilla system, but current maintainer (nerdboy) is not very intrested in
GIS (and doesn't know OS GIS related problems) and strictly follows Gentoo
guidelines - I had problems with getting simple GRASS related fixes to ebuild
accepted.
I don't think that there will somebody push opendwg ebuild and related grass
flag.
There's no reason we can't maintain our own ebuild.
@if [ `cat "$(GRASS_HOME)/error.log" | wc -l` -gt 8 ] ; then false ; else true ; fi
although it hasn't been acted upon.
It would be easy enough to add a similar check to the src_compile()
method in the ebuild.
However: the build system is currently missing some conditions in the
Makefiles, i.e. it attempts to compile certain modules regardless of
whether the corresponding dependencies were enabled. If the dependency
wasn't enabled, that module will fail to compile, resulting in an
error message.
Normally, this is harmless; if you use --without-tiff, then you don't
get r.out.tiff, and an entry for r.out.tiff in error.log isn't
particularly surprising. However, this will interfere with attempts to
determine success/failure of the build.
I'll try building with --disable-<everything> to see which modules
require conditional compilation.
On Fri, Aug 25, 2006 at 12:48:57PM +0100, Glynn Clements wrote:
Me-D?ris Nartie-B?s wrote:e-A
> What is more important for me - currently emerging GRASS can fail, but user
> will get no notification about this using current ebuild. See more:
> http://grass.itc.it/pipermail/grass-dev/2006-August/025129.html "Checking for
> compilation errors"
Paul Kelly recently proposed this fix:
@if [ `cat "$(GRASS_HOME)/error.log" | wc -l` -gt 8 ] ; then false ; else true ; fi
I'll try building with --disable-<everything> to see which modules
require conditional compilation.
Done; I've fixed a couple of cases where this was missed (v.digit,
r.out.tiff).
I haven't fixed the modules which fail when --without-curses is used;
the number of modules which require it is such that curses is
effectively mandatory (both libgrass_I and libgrass_Iortho require it,
thus so do all imagery modules).
These types of problems and needing to compile GRASS from scratch all the time has forced me to slowly slip back to the RH world ..... This time FC5... Nice RPM support.
Would be great is there was more enthusiasm for GRASS on GENTOO.
I started a mailing list that in retrospec failed miserably due to such a small group of users....
Please keep the world updated in GENTOO and GRASS becomes a reliable option... Too bad there was not an IDIOTS method of creating emerge files... Like a simple point and click GUI so that they would be easily maintained.
Maybe scripting some SQL for maintence.... Oh well...
Cheers
-----Original Message-----
From: grass-dev-bounces@grass.itc.it [mailto:grass-dev-bounces@grass.itc.it] On Behalf Of Maris Narti¹s
Sent: August 25, 2006 02:44
To: grass-dev@grass.itc.it
Subject: Re: [GRASS-dev] freetype on gentoo
Hi,
currently GRASS on Gentoo is almost unmaintained. First GRASS ebuild for 5.7/6.0 was made by me. Now ebuilds are submitted by community trough bugzilla system, but current maintainer (nerdboy) is not very intrested in GIS (and doesn't know OS GIS related problems) and strictly follows Gentoo guidelines - I had problems with getting simple GRASS related fixes to ebuild accepted. I don't think that there will somebody push opendwg ebuild and related grass flag.
On Mon, 2006-08-28 at 09:07 -0400, Sampson, David wrote:
These types of problems and needing to compile GRASS from scratch all the time has forced me to slowly slip back to the RH world ..... This time FC5... Nice RPM support.
Would be great is there was more enthusiasm for GRASS on GENTOO.
But now that you are on FC5, perhaps GRASS enthusiasm for that will be
good enough? I was surprised to find the most recent rpms for GRASS for
FC4, not FC5 [1].
