All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Runte <marcel.runte@web.de>
To: chris.mason@oracle.com, Yan Zheng <zheng.yan@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Re: Kernel oops after compile error
Date: Wed, 06 Aug 2008 00:21:27 +0200	[thread overview]
Message-ID: <1908993894@web.de> (raw)

Hi YZ, hi Chris,

I tried the whole build process on Kubuntu Hardy Heron (kernel 2.6.24-1=
9-generic) and there ist was OK, so I think it has something to do with=
 the difference in include of kernel-headers-2.6.22-15 on Gutsy...

Unfortunately new release leads to same error... But for testing purpos=
e for me its enough that this working on a higher kernel version...

Best regards, Marcel

> -----Urspr=FCngliche Nachricht-----
> Von: "Yan Zheng" <zheng.yan@oracle.com>
> Gesendet: 01.08.08 05:01:13
> An: "Marcel Runte" <marcel.runte@web.de>
> CC: linux-btrfs@vger.kernel.org
> Betreff: Re: Kernel oops after compile error


> 2008/8/1 Marcel Runte <marcel.runte@web.de>:
> > patch described in your link is included in http://www.kernel.org/h=
g/index.cgi/btrfs/kernel/rev/9da425337329, which I used for compilation=
=2E Even putting an alias like "alias gcc =3D 'gcc -DREMOVE_SUID_PATH'"=
 or doing a "CC=3D'gcc -DREMOVE_SUID_PATH'; make"leads to same error me=
ssage when compiling file.c
> >
>=20
> Linux kernel uses its own building system, putting alias has no
> effect. Please try modify the code directly.
>=20
> YZ
>=20


--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2008-08-05 22:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-05 22:21 Marcel Runte [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-07-31 18:31 Re: Kernel oops after compile error Marcel Runte

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=1908993894@web.de \
    --to=marcel.runte@web.de \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=zheng.yan@oracle.com \
    /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.