Re: [Bug-glpk] patch for glpk-4.8

[Mike Castle]

On Mon, Jan 17, 2005 at 09:29:39PM +0300, Andrew Makhorin wrote:
> > Since this is a patch that I use locally, it patches both Makefile.am and
> > Makefile.in (why regen if I don't have to?)
> > 
> > * Enable building outside of srcdir.
> 
> You don't need that; see section "A.4 Compiling and checking the package"
> in the reference manual. Besides, it is not a good idea to modify
> Makefile.in, because it is generated (by GNU Automake) from Makefile.am.

I followed the convention suggested in INSTALL.  Particularly:

To compile the package in a different directory from the one containing
the source code, you must use a version of 'make' that supports 'VPATH'
variable, such as GNU 'make'. 'cd' to the directory where you want the
object files and executables to go and run the 'configure' script. 
'configure' automatically checks for the source code in the directory
that 'configure' is in and in '..'. If for some reason 'configure' is
not in the source code directory that you are configuring, then it will
report that it can't find the source code. In that case, run 'configure'
with the option '--srcdir=DIR', where DIR is the directory that contains
the source code.

Also, since this is part of the GNU coding standards, and glpk claims to be
a GNU program, it should work.  Without my patch, it does not work.

Also, you'll note my comment that said this is the patch that I use
locally.  Since I use it locally I patched the Makefile.in.  After all, why
would I want to rerun autoreconf -fiv if I can simply patch Makefile.in and
achieve the same results much faster?  But, you'll also note that I also
patched the Makefile.am for your convenience.  You're welcome.

mrc
-- 
     Mike Castle      address@hidden      www.netcom.com/~dalgoda/
    We are all of us living in the shadow of Manhattan.  -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc