Re: Running makedist on a machine w/o midgard installed failes when making apache2 tarball.

On søn, 2006-02-12 at 20:29 +0100, Piotras wrote:
> > Reason: in makedist, ./configure is run, and it doesn't find
> > midgard-config if there isn't another midgard-config in the path
> > allready.
> >
> > Question: a) Why is ./configure run at all?
> 
> Because is called when 'make dist' is running.
You mean that it generates the makefile make dist uses?
> > b) What is the best solution? Add
> > --with-midgard-configure=../../core/midgard/midgard-configure
> 
> Bad , but I think you have no other choice :/
Well, I will run configure again later anyhow and then reset it. This solution worked for me. Patch below.
Tarjei

===================================================================
RCS file: /cvs/midgard/src/makedist,v
retrieving revision 1.92
diff -u -r1.92 makedist
--- makedist    28 Jan 2006 10:57:37 -0000      1.92
+++ makedist    12 Feb 2006 20:09:45 -0000
@@ -197,7 +197,7 @@
        chmod +x configure

        # Make tarball
-       ./configure
+       ./configure
--with-midgard-config=../../core/midgard/midgard-config
        make dist

        # Copy midgard-data to monster file
@@ -234,7 +234,7 @@
        chmod +x configure

        # Make tarball
-       ./configure
+       ./configure --with-midgard-config=../core/midgard/midgard-config
        make dist

        # Copy midgard-data to monster file

> This is even worst. You can not have midgard then ;)
> 
> What could be done is to move midgard-config functionality to header files.
> But the question is, how to define headers location then?
> 
> I have the same problem with makedist for nightly builds.



> Piotras
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe-b5ZhpPVuLA+tlBvVaVFjCkB+6BGkLq7r@public.gmane.org
> For additional commands, e-mail: [email protected]
> 
-- 
Tarjei Huse <tarjei-y/[email protected]>