From: "Yan Zheng" <zheng.yan@oracle.com>
To: "Marcel Runte" <marcel.runte@web.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Kernel oops after compile error
Date: Fri, 1 Aug 2008 11:01:09 +0800 [thread overview]
Message-ID: <3d0408630807312001r773281afm87fff466444d2b3d@mail.gmail.com> (raw)
In-Reply-To: <1905891602@web.de>
2008/8/1 Marcel Runte <marcel.runte@web.de>:
> patch described in your link is included in http://www.kernel.org/hg/index.cgi/btrfs/kernel/rev/9da425337329, which I used for compilation. Even putting an alias like "alias gcc = 'gcc -DREMOVE_SUID_PATH'" or doing a "CC='gcc -DREMOVE_SUID_PATH'; make"leads to same error message when compiling file.c
>
Linux kernel uses its own building system, putting alias has no
effect. Please try modify the code directly.
YZ
next prev parent reply other threads:[~2008-08-01 3:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 18:53 Kernel oops after compile error Marcel Runte
2008-08-01 3:01 ` Yan Zheng [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-30 22:44 Marcel Runte
2008-07-31 1:11 ` Yan Zheng
2008-07-31 13:43 ` Chris Mason
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=3d0408630807312001r773281afm87fff466444d2b3d@mail.gmail.com \
--to=zheng.yan@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=marcel.runte@web.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox