All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Adrian Bunk <bunk@stusta.de>, Andrew Morton <akpm@osdl.org>,
	bcollins@debian.org, scjody@modernduck.com,
	linux-kernel@vger.kernel.org,
	linux1394-devel@lists.sourceforge.ne, sam@ravnborg.org
Subject: Re: 2.6.16-rc1-mm5: drivers/ieee1394/oui O=... builds broken
Date: Sat, 04 Feb 2006 10:31:03 +0100	[thread overview]
Message-ID: <1139045463.3602.1.camel@localhost> (raw)
In-Reply-To: <43E46F1F.9070503@s5r6.in-berlin.de>

[-- Attachment #1: Type: text/plain, Size: 792 bytes --]

On Sat, 2006-02-04 at 10:08 +0100, Stefan Richter wrote:
> Adrian Bunk wrote:
> > ...
> >   OUI2C   drivers/ieee1394/oui.c
> > /bin/sh: drivers/ieee1394/oui2c.sh: No such file or directory
> > make[3]: *** [drivers/ieee1394/oui.c] Error 127
> > 
> > <--  snip  -->
> > 
> > 
> > The change that broke it is:
> > 
> > 
> >  quiet_cmd_oui2c = OUI2C   $@
> > -      cmd_oui2c = $(CONFIG_SHELL) $(srctree)/$(src)/oui2c.sh < $< > $@
> > +      cmd_oui2c = $(CONFIG_SHELL) $(src)/oui2c.sh < $< > $@
> 
> How can this be reproduced? IOW which way of building the kernel is broken?

Looks like my mistake. I was pretty sure I tested the normal in-kernel
build way, sorry.

I did the change in order to build out of tree (with an absolute path as
a SUBDIRS value).

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  parent reply	other threads:[~2006-02-04  9:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-03  8:07 2.6.16-rc1-mm5 Andrew Morton
2006-02-03 10:17 ` 2.6.16-rc1-mm5 Benoit Boissinot
2006-02-03 20:13   ` 2.6.16-rc1-mm5 Benoit Boissinot
2006-02-03 20:36     ` 2.6.16-rc1-mm5 Andrew Morton
2006-02-03 11:51 ` [-mm patch] Makefile: remove a tab from an empty line Adrian Bunk
2006-02-03 20:57 ` [-mm patch] kernel/time/timeofday.c: make struct ts_interval static Adrian Bunk
2006-02-03 21:50   ` john stultz
2006-02-03 20:59 ` [-mm patch] kernel/timer.c: make some variables static Adrian Bunk
2006-02-03 21:02 ` [-mm patch] net/ipv4/fib_rules.c: make struct fib_rules static again Adrian Bunk
2006-02-04 23:51   ` David S. Miller
2006-02-03 21:09 ` [-mm patch] make some "struct clocksource" static Adrian Bunk
2006-02-03 21:12 ` [-mm patch] arch/i386/kernel/cpu/: make tons of functions static Adrian Bunk
2006-02-03 21:25 ` 2.6.16-rc1-mm5: drivers/ieee1394/oui O=... builds broken Adrian Bunk
2006-02-04  2:43   ` Jody McIntyre
2006-02-04  9:20     ` Sam Ravnborg
2006-02-04  9:08   ` Stefan Richter
2006-02-04  9:30     ` Stefan Richter
2006-02-04  9:31     ` Johannes Berg [this message]
2006-02-04  9:58       ` Stefan Richter
2006-02-06  4:31   ` Jody McIntyre
2006-02-04  7:59 ` 2.6.16-rc1-mm5 Matthias Urlichs
2006-02-04  9:29 ` 2.6.16-rc1-mm5 Sam Ravnborg
2006-02-04  9:36   ` 2.6.16-rc1-mm5 Andrew Morton

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=1139045463.3602.1.camel@localhost \
    --to=johannes@sipsolutions.net \
    --cc=akpm@osdl.org \
    --cc=bcollins@debian.org \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.ne \
    --cc=sam@ravnborg.org \
    --cc=scjody@modernduck.com \
    --cc=stefanr@s5r6.in-berlin.de \
    /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.