All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: kevin@lacqui.com
Subject: Re: [PATCH] Build issues with parallel make
Date: Tue, 28 Aug 2007 12:06:05 +0200	[thread overview]
Message-ID: <20070828100605.GA8000@thorin> (raw)
In-Reply-To: <20070826213601.af4c80b6.dn.tlp@gmx.net>

On Sun, Aug 26, 2007 at 09:36:01PM +0200, Simon Peter wrote:
> Hi!
> 
> > > Making this work properly might be a bit trickier.  I myself don't
> > > understand it (plus, I'm ruby illiterate), so I'm afraid I can't be
> > > of help on this.
> > Thank you for your response.  As I said, it's pretty much a band-aid
> > response. I'll take deeper look at the build process.
> 
> I encountered the same problem and fixed it by allowing finer-grained
> dependency control in the rmk-file (source files are allowed to have
> dependencies now)

Great!

> and correcting the two header file dependencies (not
> the binaries depend on the headers, but one of the source files,
> respectively).

This doesn't sound right.  Since the source files (grub-setup.c, grub-probe.c)
are not dynamicaly generated, make doesn't need a rule to "build" them.  Why
did you need to change this?

Though, if the rmk needs to be modified, take into account there are other
targets which probably share the same problem (powerpc-ieee1275, i386-efi).

Btw, could you please include a ChangeLog entry with your patch?

> On a whole, I would like to encourage the grub folks to move to
> Automake. Automake has automatic dependency tracking, so problems like
> this cannot arise. Plus it's one of your own tools (it's GNU)! And I'm
> sure you could drop that awkward Ruby build-dependency by using some
> Autoconf magic for the rest. I hope I did not offend anyone. ;)

You should take this up with Okuji.  I don't think you offended him, but
I assume he had his own reasons to put it this way :-)

Thank you,

-- 
Robert Millan

<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call, if you are unable to speak?
(as seen on /.)



  reply	other threads:[~2007-08-28 10:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17  9:29 [PATCH] Build issues with parallel make Kevin Lacquement
2007-07-20 17:21 ` Robert Millan
2007-07-21 17:25   ` Kevin Lacquement
2007-08-26 19:36     ` Simon Peter
2007-08-28 10:06       ` Robert Millan [this message]
2007-08-28 15:54         ` Simon Peter
2007-08-29 10:41           ` Robert Millan

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=20070828100605.GA8000@thorin \
    --to=rmh@aybabtu.com \
    --cc=grub-devel@gnu.org \
    --cc=kevin@lacqui.com \
    /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.