I downloaded the new beta4 source release, and attempted a
"configure ; make ; make install", but performing "make"
in the top level source directory does nothing. Is the
autoconf build process complete yet? Is anyone working on
fine tuning it? Are the Makefile.in/Makefile.am/etc. files
available for patches?
--
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+
| Eric B. Mitchell mailto:ricdude@toad.net |
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+
On Mon, 1 Nov 1999, Eric Mitchell wrote:
I downloaded the new beta4 source release, and attempted a
"configure ; make ; make install", but performing "make"
in the top level source directory does nothing. Is the
autoconf build process complete yet? Is anyone working on
I ran into the same problem this weekend. I looks like there needs to be
a bit more thought put into the process. I'm not too familiar with 'make'
(just use it) so my observations could be flawed. There appears to be
semi-colons missing between each of the commands on the lines in
'Makefile'. I tried running each line by hand but ran out of patience and
wetwear memory with all the substitutions. I'll have another look tonight
since it needs to be done with make to create a rpm file.
Any good online tutorials on make around?
Rod
--
Roderick A. Anderson
raanders@altoplanos.net Altoplanos Information Systems, Inc.
Voice: 208.765.6149 212 S. 11th Street, Suite 5
FAX: 208.664.5299 Coeur d'Alene, ID 83814
Eric Mitchell wrote:
I downloaded the new beta4 source release, and attempted a
"configure ; make ; make install", but performing "make"
in the top level source directory does nothing. Is the
autoconf build process complete yet?
Yes I would say it is quite complete now, I have compiled it on three
very different systems (i686 RedHat linux, i586 Debian and DU alpha)
and it works easy (yet not so straightforward for DU alpha )
Is anyone working on fine tuning it? Are the
Makefile.in/Makefile.am/etc. files
available for patches?
Yes, many people are working on this. Probably if you say something more
about your system's configuration we may be more helpfull 
Luca
--> Luca Palmeri - Dip. Proc. Chimici dell'Ingengeria
Universita' di Padova TEL: +390498275527 -------
------------------------- FAX: +390498275528 -------
--> Think holistic @ the end of the 2nd millenium <--
On Mon, 1 Nov 1999, Eric Mitchell wrote:
I downloaded the new beta4 source release, and attempted a
"configure ; make ; make install", but performing "make"
in the top level source directory does nothing.
'configure' is a local file and should be run as
./configure
otherwise no Makefile will be created
Hint: make by itself does nothing in grass5. Run these two commands
separately:
./configure
make install
Hint2: if you have RH, you may have to edit your Makefile after running
configure and change the line starting with ENV=
to
ENV = env
regards
Morten Hulden
On Mon, Nov 01, 1999 at 12:04:59PM -0800, Roderick A. Anderson wrote:
On Mon, 1 Nov 1999, Eric Mitchell wrote:
>
> I downloaded the new beta4 source release, and attempted a
> "configure ; make ; make install", but performing "make"
> in the top level source directory does nothing. Is the
> autoconf build process complete yet? Is anyone working on
I ran into the same problem this weekend. I looks like there needs to be
a bit more thought put into the process. I'm not too familiar with 'make'
(just use it) so my observations could be flawed. There appears to be
semi-colons missing between each of the commands on the lines in
'Makefile'. I tried running each line by hand but ran out of patience and
wetwear memory with all the substitutions. I'll have another look tonight
since it needs to be done with make to create a rpm file.
Any good online tutorials on make around?
Which version of make do you have?
I would recommend installing GNU make.
It comes with a resonable reference manual and should BTW. work.
Manual is also online at:
http://www.gnu.org/software/make/make.html
(Oh and you don't need make to make make.)
Bernhard
--
Research Assistant, Geog Dept UM-Milwaukee, USA. (www.uwm.edu/~bernhard)
Free Software Projects and Consulting (intevation.de)
Association for a Free Informational Infrastructure (ffii.org)
I think the original point was that "make" by itself doesn't do
anything, and it probably should. A typical set-up would have
./configure # configure environ...
make # compile the code
make install # compile, if not compiled, and install
make clean # remove all compiled code
make distclean # same as clean
It's nice to be able to "make" all of the objects, before actually
putting them in place. Then if errors come up, you don't have a broken
system installed.
--
+----------------------------------------------------+
| Eric G. Miller egm2@jps.net |
| GnuPG public key: http://www.jps.net/egm2/gpg.asc |
+----------------------------------------------------+