From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] patch for 2.6.6-rc1
Date: Mon, 10 May 2004 20:46:15 +0200 [thread overview]
Message-ID: <200405102046.15381.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <006f01c42fc1$d16b4bc0$2000000a@schlepptopp>
Alle 23:18, sabato 1 maggio 2004, roland ha scritto:
> Hi Paolo/Jeff,
>
> >Please post the arch/um/kernel/config.c file the build produced, which
> > gave the error. The change to the "QUOTE" line is to be analyzed.
>
> i think the change to $$config =~ s/\\n/\\\n"\\n"/g probably was a mistake
> (i`m not good in regexes, though). it seems, that all the quotes and \n`s
> are being stripped from that file and so it`s no correct "c-source"
> anymore, imho.
>
> before:
> ---snipp---
> static __initdata char *config = "#\n"
> "# Automatically generated make config: don`t edit\n"
> "#\n"
> "CONFIG_USERMODE=y\n"
> ---snipp---
>
> after applying patch.266rc1-1 and running make again, it is:
> ---snipp---
> static __initdata char *config = "#
> # Automatically generated make config: don`t edit
> #
> CONFIG_USERMODE=y
> ---snipp---
>
> i changed the line in the Makefile back to:
> $$config =~ s/\n/\\n"\n"/g
> which made things better again.
>
> the error i reported is gone, but now "make linux ARCH=um" fails with:
>
> -> see make.log
This is related with the changes by Jeff Chua - maybe you did not apply them
well...
> which doesn`t seem to be related to that change of the regex before.
> since this error looks "skas related" for me, i gave it a further try and
> disabled skas support in .config - after that, the compile for that
> "TT only"-UML runs fine for a while, but unfortunately it also fails in
> the end:
>
> -> see make_tt.log
Tried disabling gdb proxy/profiling? That is probably the source of the
problem.
> so still no 2.6.6-rc1 or 2.6.6-rc2 (tried both)
> err - i have a problem in understanding:
> why PERL code ?
> the statement is in arch/um/kernel/Makefile - is that being parsed by a
> perl interpreter during "make" - or does make just use similar language ?
> sorry if this sounds dumb - but i`m no developer and i never wrote a
> makefile myself.
Look in the lines nearby and you'll see that "perl" is invoked, and that line
of code is passed to it as the program to execute.
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2004-05-10 18:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 14:04 [uml-devel] patch for 2.6.6-rc1 Jeff Chua
2004-04-21 1:11 ` roland
2004-04-21 6:33 ` Jeff Chua
2004-04-21 23:51 ` roland
2004-04-22 0:07 ` Jeff Chua
2004-04-22 8:11 ` Primero
2004-04-30 15:01 ` [uml-user] " BlaisorBlade
2004-04-30 13:45 ` BlaisorBlade
2004-05-01 21:18 ` roland
2004-05-10 18:46 ` BlaisorBlade [this message]
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=200405102046.15381.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox