From: "Alexander Stohr" <Alexander.Stohr@gmx.de>
To: linux-kernel@vger.kernel.org
Cc: sam@ravnborg.org, pluto@pld-linux.org
Subject: Re: confirmed: kernel build for 2.6.8-rc3 is broken for at least i386
Date: Mon, 9 Aug 2004 17:04:58 +0200 (MEST) [thread overview]
Message-ID: <13013.1092063898@www53.gmx.net> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 1280 bytes --]
hello Sam,
i think i reached the root cause of my problem:
bash# export AFLAGS_vmlinux.lds.o=123
export: AFLAGS_vmlinux.lds.o=123: not a legal variable name
the problem seems to be raised by dots beeing part of the variable name.
my version of bash is reported like shown here in the environment:
BASH_VERSION=1.14.5(1)
unfortunately the whole build process, including GNU Make 3.80,
fails absolutely silently for this specific point of system error.
sorry that i am feeling unable right now to provide a fix.
maybe some more research is needed to find a viable solution.
in worst case the whole makefile system has to be patched
for any such variable construct.
on the other side it does look like the normal recursive call sheme
of make is immune to such bash habits, is it? (supposed it launches
itselves directyl and not embedded in a few other shell commands...)
i am not totally sure about that all - especially because i tried
a newer shell which exposed the very same limitation, but there must
be something in that area because i could fiddle out that the var
setting gets lost all the time when calling "scripts/Makefile.build".
-Alex.
--
NEU: WLAN-Router für 0,- EUR* - auch für DSL-Wechsler!
GMX DSL = supergünstig & kabellos http://www.gmx.net/de/go/dsl
next reply other threads:[~2004-08-09 15:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 15:04 Alexander Stohr [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-05 14:17 confirmed: kernel build for 2.6.8-rc3 is broken for at least i386 Alexander Stohr
2004-08-05 20:33 ` Sam Ravnborg
2004-08-07 16:21 ` Paweł Sikora
2004-08-07 17:39 ` Sam Ravnborg
2004-08-07 18:54 ` Paweł Sikora
2004-08-04 9:50 Alexander Stohr
2004-08-04 16:07 ` Sam Ravnborg
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=13013.1092063898@www53.gmx.net \
--to=alexander.stohr@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pluto@pld-linux.org \
--cc=sam@ravnborg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox