On Sat, Jan 28, 2006 at 09:35:08AM -0500, I wrote:
> On Sat, Sep 10, 2005 at 11:01:22PM +0200, I wrote:
> > [...]
> > Fixing that issue properly isn't quite easy: GNU Mach's build system
> > needs to be reordered a bit.
> [...]
> Is this ok for everyone to be applied?
I just committed the follo
> ./configure --prefix='$(libexecdir)/foo' --libexecdir=/foo
Do you really consider that as a valid use case? Putting
libexecdir's files into `/foo/' and everything else into
`/foo/foo/{bin,share,...}/'?
Yes, I have ended up using similar hacks on several occassions.
If this real
On Sun, Jan 29, 2006 at 06:46:35PM +0100, Alfred M. Szmidt wrote:
>Yes, as long as we don't let the build system create Makefiles in
>subdirectories, which we don't at the moment. Changed.
>
> Would be better to simply stop using manually maintained .in's, and
> use automake, then one won
On Sun, Jan 29, 2006 at 06:46:35PM +0100, Alfred M. Szmidt wrote:
> ./configure --prefix='$(libexecdir)/foo' --libexecdir=/foo
Do you really consider that as a valid use case? Putting libexecdir's
files into `/foo/' and everything else into `/foo/foo/{bin,share,...}/'?
If this really bothers you
> You removed libexecdir (and maybe some other variables), why?
> Doing something like `--prefix=$(libexecdir)/foo' is always OK.
> All variables that can be substituted should be listed. The
> variables also get partially expanded, so that is one more reason
> to list all of them (
On Sun, Jan 29, 2006 at 12:39:57PM +0100, Alfred M. Szmidt wrote:
>2006-01-28 Thomas Schwinge <[EMAIL PROTECTED]>
>
> * Makefile.in: Various cleanups. Do not include $(sysdep)/Makefrag
> anymore. Move shared and system dependent stuff out of this file.
> Include
2006-01-28 Thomas Schwinge <[EMAIL PROTECTED]>
* Makefile.in: Various cleanups. Do not include $(sysdep)/Makefrag
anymore. Move shared and system dependent stuff out of this file.
Include Makerules.
This says nothing about what actually changed. `Did stuff
