From: klink@clouddancer.com (Colonel)
To: linux-kernel@vger.kernel.org
Subject: Re: compile error 2.4.4pre6: inconsistent operand constraints in an
Date: Tue, 24 Apr 2001 16:07:42 -0700 (PDT) [thread overview]
Message-ID: <20010424230742.0C1906808@mail.clouddancer.com> (raw)
In-Reply-To: <9c3pgm$u0$1@ns1.clouddancer.com>
In-Reply-To: <Pine.LNX.4.21.0104241350230.8659-100000@neon.rayfun.org> <E14rpIA-0000iK-00@the-village.bc.nu> <9c3pgm$u0$1@ns1.clouddancer.com>
In list.kernel, axel <axel@rayfun.org> wrote:
>
>How about correcting the needed gcc version in Documentation/Changes?
Linux, with up to date documention?? In your dreams perhaps.
>On Mon, 23 Apr 2001, Alan Cox wrote:
>
>> > after having had trouble with compilation due to old gcc version, i have
>> > updated to gcc 3.0 and received the following error:
>>
>> 2.4.4pre6 only builds with gcc 2.96. If you apply the __builtin_expect fixes
>> it builds and runs fine with 2.95. Not tried egcs. The gcc 3.0 asm constraints
>> one I've yet to see a fix for.
BTW. The above attitude was fostered by informing the Changes
maintainer that the recommended NFS userspace server was on the
exploits list (back in the 2.0 kernel days when knfs was new) and
getting a "I don't use that, so what" response.
...and the documentation continued to recommend an exploitable NFS
server... in short: you must cross-check to be sure, at least in linux
you have a few more options.
next prev parent reply other threads:[~2001-04-24 23:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-23 21:11 compile error 2.4.4pre6: inconsistent operand constraints in an `asm' axel
2001-04-23 21:44 ` Erik Mouw
2001-04-23 22:58 ` compile error 2.4.4pre6: inconsistent operand constraints in an Alan Cox
2001-04-24 0:25 ` Jeff Chua
2001-04-24 11:51 ` axel
[not found] ` <9c3pgm$u0$1@ns1.clouddancer.com>
2001-04-24 23:07 ` Colonel [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-24 19:54 Wayne.Brown
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=20010424230742.0C1906808@mail.clouddancer.com \
--to=klink@clouddancer.com \
--cc=linux-kernel@vger.kernel.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