All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: autogen.sh warnings
Date: Fri, 01 Jan 2010 10:57:08 -0600	[thread overview]
Message-ID: <4B3E2964.8000002@gmail.com> (raw)
In-Reply-To: <20100101113333.GB3692@thorin>

Robert Millan wrote:
> On Mon, Dec 28, 2009 at 09:50:47PM -0600, Bruce Dubbs wrote:
>> Robert Millan wrote:
>>> What is exactly the problem?  
>> Using automake without Makefile.am is non-standard and not provided for  
>> within automake.  The only thing we use automake for is to copy  
>> config.{guess,sub} to the root of the root of the source.
>>
>> Also, building as one large monolithic Makefile with includes built via  
>> scripts is probably not optimal from a comprehension point of view.
> 
> That's a long-standing problem, with no easy solution. 

That's for sure.

> But as for automake,
> I don't think it'd be a bad idea to migrate Makefile.in to Makefile.am.  We
> already have kludges in Makefile.in (e.g. docs/version.texi generation) which
> would completely disappear if this file was automake'd.
> 
> Any takers?

I thought about it, but I really don't have much experience writing for 
autotools.  AFAICT, it would require getting rid of all the ruby and 
gen*.sh scripts and generally be very invasive.

As you know, GRUB supports many OSes, file systems, and BIOSes.  The 
nature of the process is closer to an operating system than a standard 
program.  The more I look at it, the more impressed I am that you guys 
get as much as you do working.

I think it would take many iterations to get an autotooled build system 
right.

   -- Bruce



  reply	other threads:[~2010-01-01 16:57 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-07 17:38 autogen.sh warnings Bruce Dubbs
2009-12-07 19:21 ` Colin Watson
2009-12-07 20:28   ` Bruce Dubbs
2009-12-07 22:12     ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-07 23:07       ` Bruce Dubbs
2009-12-07 22:40     ` Colin Watson
2009-12-07 23:26       ` Bruce Dubbs
2009-12-09 21:52   ` Robert Millan
2009-12-09 22:19     ` Bruce Dubbs
2009-12-09 22:34       ` Felix Zielcke
2009-12-09 23:28         ` Bruce Dubbs
2009-12-10  0:25           ` Felix Zielcke
2009-12-10  6:05             ` Bruce Dubbs
2009-12-10 10:15               ` Felix Zielcke
2009-12-10 16:20                 ` Bruce Dubbs
2009-12-24 21:13                   ` Robert Millan
2009-12-29  3:50                     ` Bruce Dubbs
2010-01-01 11:33                       ` Robert Millan
2010-01-01 16:57                         ` Bruce Dubbs [this message]
2010-01-03 16:25                           ` Robert Millan
2009-12-10  0:49           ` Robert Millan
2009-12-09 22:56       ` Robert Millan
2009-12-07 19:50 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-07 20:51   ` Bruce Dubbs
2009-12-07 22:16     ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-07 22:49     ` Bruce Dubbs
2009-12-07 23:54       ` Colin Watson
2009-12-08  0:01         ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-08  0:13           ` Bruce Dubbs
2010-01-07 19:14             ` Robert Millan
2009-12-08  0:16           ` Colin Watson
2009-12-08  0:34             ` Building system (Re: autogen.sh warnings) Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-08  3:40               ` Bruce Dubbs
2009-12-08 10:20         ` autogen.sh warnings Felix Zielcke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B3E2964.8000002@gmail.com \
    --to=bruce.dubbs@gmail.com \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.