[GRASS5] Linux binary builder wanted!

GRASS GRASS developer
1

Hi again,

as my machine is somewhat over-customized, I would like to
find a volunteer who builds the Linux binaries for GRASS 5.

First exercise is to check out the branch and build the
prestable1 package according to the rules in
documents/release_rules.txt
This package shall be put out for the binary testers then.

It's not that difficult. He/she needs a common machine fulfilling
the REQUIREMENTS to compile GRASS.

As my machine is not standard any more, it may cause more problems
than wanted (probably the reported NVIZ lib-dl ASSERTION problem
is related to this, here NVIZ runs well).

Please contact me,

Markus

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

2

Rich,

Can you help out with this?

Bruce

Markus Neteler wrote:

Hi again,

as my machine is somewhat over-customized, I would like to
find a volunteer who builds the Linux binaries for GRASS 5.

First exercise is to check out the branch and build the
prestable1 package according to the rules in
documents/release_rules.txt
This package shall be put out for the binary testers then.

It's not that difficult. He/she needs a common machine fulfilling
the REQUIREMENTS to compile GRASS.

As my machine is not standard any more, it may cause more problems
than wanted (probably the reported NVIZ lib-dl ASSERTION problem
is related to this, here NVIZ runs well).

Please contact me,

Markus

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

3

On Wed, 11 Apr 2001, B. Byars wrote:

> It's not that difficult. He/she needs a common machine
> fulfilling the REQUIREMENTS to compile GRASS.

I would certainly be willing (hell, I might even try to
build some rpms). But I am still having problems with nviz
(seg faults) on an almost clean suse install (7.1).
Every thing else seems to work (for some value of work).

If you guys need access to the box, that may be a problem,
as we are only on a lowly DSL connection.

In any event,
Let me know if I can help.

Thanks,
Matt Berglund

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

4

Hi Matt,

On Thu, Apr 12, 2001 at 01:59:24PM -0400, mberglund wrote:

> > It's not that difficult. He/she needs a common machine
> > fulfilling the REQUIREMENTS to compile GRASS.

I would certainly be willing (hell, I might even try to
build some rpms). But I am still having problems with nviz
(seg faults) on an almost clean suse install (7.1).
Every thing else seems to work (for some value of work).

thanks for your offer! So let's start (perhaps we communicate
personally later).

Do you have the new release_branch downloaded? To switch
your cvs code to the new release branch, simply enter:

cvs update -r releasebranch_11_april_2001_5_0_0

This will only transfer changes (as usual). Later on, you can
always update with
  
cvs up -dP

as in past.

If you guys need access to the box, that may be a problem,
as we are only on a lowly DSL connection.

Please make a fresh compile

rm config.cache
rm /usr/local/grass5/lib/libstdc* # we don't need it, see below
make distclean
configure
make
make install

and tell us, if the NVIZ problem is still there.

Concerning the libstdc: Please compile "gdal" also from GDAL-cvs,
then you don't need the /usr/local/grass5/lib/libstdc++ (which *may*
cause problems).

I would be glad if we could publish your binary package soon to
involve binary testers, too (any volunteers for this?).

Let me know if you need any assistance,

Markus

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

5

Hi all,

as time is passing by (no surprise), we should consider to
release GRASS 5.0.0pre1 now. I am not aware of further severe
problems, the package should reach the masses now.

Are there any objections? If not,
- I'll tag the release_branch
- ask for volunteers to build precompiles binaries

It would be great to get out the release this week.

Markus

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

6

Will handle Solaris binaries if needed. My Solaris intel box is down for
now, but I should have it back up by early next week.

Bruce

Markus Neteler wrote:

Hi all,

as time is passing by (no surprise), we should consider to
release GRASS 5.0.0pre1 now. I am not aware of further severe
problems, the package should reach the masses now.

Are there any objections? If not,
- I'll tag the release_branch
- ask for volunteers to build precompiles binaries

It would be great to get out the release this week.

Markus

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'