From: Rob Landley <rob@landley.net>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Ian McDonald <imcdnzl@gmail.com>
Subject: Re: [uml-devel] Broken compiling under 2.6.12-rc2 on my machine
Date: Thu, 7 Apr 2005 02:50:10 -0400 [thread overview]
Message-ID: <200504070250.10873.rob@landley.net> (raw)
In-Reply-To: <200504062136.26895.blaisorblade@yahoo.it>
On Wednesday 06 April 2005 03:36 pm, Blaisorblade wrote:
> Anyway, from looking at what you quote, it's identical to the code in
> arch/um/kernel/Makefile. Quoting the correct code:
>
> quiet_cmd_quote2 = QUOTE $@
> cmd_quote2 = sed -e '/CONFIG/{' \
> -e 's/"CONFIG"\;/""/' \
> -e 'r $(obj)/config.tmp' \
> -e 'a""\;' \
> -e '}' \
> $< > $@
>
> As you see, there is a fourth expression, *here*. But it's -e '}'.
>
> This patch went in after 2.6.11, I'm noticing - wow, are releases getting
> so slow?
>
> > > System is Debian Woody,
>
> Can you post your sed version? and Rob, can you then test it and fix the
> code? Please save the correct config.c currently created and check it for
> reference.
I enabled SKAS mode and the build finished. The sed bit didn't break for me:
CHK usr/initramfs_list
QUOTE arch/um/kernel/config.tmp
QUOTE arch/um/kernel/config.c
CC arch/um/kernel/config.o
And I'm using knoppix, which is based on debian.
From the error message, it seems to be complaining about the "a" command. If
you're using a really really really old version of sed, it might insist on a
gratuitous line break before the line to be added. (I know it did back in
the 1970's, but I didn't think anything remotely modern had that limitation.)
So try splitting the command in half like this:
cmd_quote2 = sed -e '/CONFIG/{' \
-e 's/"CONFIG"\;/""/' \
-e 'r $(obj)/config.tmp' \
-e 'a \' \
-e '""\;' \
-e '}' \
$< > $@
I just tried that here and it behaved the same way as the other version, for
me...
Rob
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&opÌk
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-04-07 8:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-06 3:51 [uml-devel] Broken compiling under 2.6.12-rc2 on my machine Ian McDonald
2005-04-06 5:45 ` Rob Landley
2005-04-06 17:59 ` Ian McDonald
2005-04-06 19:36 ` Blaisorblade
2005-04-06 23:55 ` Ian McDonald
2005-04-07 8:08 ` Rob Landley
2005-04-07 10:57 ` Adrian Phillips
2005-04-07 18:20 ` Blaisorblade
2005-04-07 6:50 ` Rob Landley [this message]
2005-04-07 18:19 ` Blaisorblade
2005-04-08 4:57 ` Rob Landley
2005-04-07 18:22 ` Blaisorblade
2005-04-07 23:21 ` Ian McDonald
2005-04-08 5:15 ` Blaisorblade
2005-04-08 5:26 ` [uml-devel] [patch] Fix broken compiling under 2.6.12-rc2 with sed 3.02 Rob Landley
2005-04-08 6:56 ` Blaisorblade
2005-04-08 7:21 ` Rob Landley
2005-04-08 4:59 ` [uml-devel] Broken compiling under 2.6.12-rc2 on my machine Rob Landley
2005-04-08 5:46 ` Rob Landley
2005-04-08 6:59 ` Blaisorblade
2005-04-08 7:23 ` Rob Landley
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=200504070250.10873.rob@landley.net \
--to=rob@landley.net \
--cc=blaisorblade@yahoo.it \
--cc=imcdnzl@gmail.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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.