From: Wayne.Brown@altec.com
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: axel@rayfun.org (axel), linux-kernel@vger.kernel.org
Subject: Re: compile error 2.4.4pre6: inconsistent operand constraints in an
Date: Tue, 24 Apr 2001 14:54:17 -0500 [thread overview]
Message-ID: <86256A38.006D51DB.00@smtpnotes.altec.com> (raw)
With the __builtin_expect patch junio@siamese.dhis.twinsun.com posted, both
2.4.4-pre6 and 2.4.3-ac12 compile with egcs-2.91.66. Also, 2.4.3-ac13 builds
without any further patches needed.
Wayne
Alan Cox <alan@lxorguk.ukuu.org.uk> on 04/23/2001 05:58:47 PM
To: axel@rayfun.org (axel)
cc: linux-kernel@vger.kernel.org (bcc: Wayne Brown/Corporate/Altec)
Subject: Re: compile error 2.4.4pre6: inconsistent operand constraints in an
> 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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-04-24 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-24 19:54 Wayne.Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-23 21:11 compile error 2.4.4pre6: inconsistent operand constraints in an `asm' axel
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
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=86256A38.006D51DB.00@smtpnotes.altec.com \
--to=wayne.brown@altec.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=axel@rayfun.org \
--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 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.