From: Daniel Jacobowitz <dan@debian.org>
To: linux-mips@linux-mips.org
Subject: Re: undefined reference to `__lshrdi3' error with GCC 4.0
Date: Tue, 17 Jan 2006 15:11:08 -0500 [thread overview]
Message-ID: <20060117201108.GA11011@nevyn.them.org> (raw)
In-Reply-To: <20060117193836.GJ18336@lug-owl.de>
On Tue, Jan 17, 2006 at 08:38:36PM +0100, Jan-Benedict Glaw wrote:
> > +#else
> > +#error I feel sick.
> > +#endif
>
> No, you feel PDP11ish. Though you'd put quotes about the warning
> message.
No, you wouldn't.
drow@nevyn:~% echo '#error A B' | gcc -E -
# 1 "<stdin>"
# 1 "<built-in>"
# 1 "<command line>"
# 1 "<stdin>"
<stdin>:1:2: error: #error A B
drow@nevyn:~% echo '#error "A B"' | gcc -E -
# 1 "<stdin>"
# 1 "<built-in>"
# 1 "<command line>"
# 1 "<stdin>"
<stdin>:1:2: error: #error "A B"
drow@nevyn:~%
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-01-17 20:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 13:48 undefined reference to `__lshrdi3' error with GCC 4.0 Martin Michlmayr
2006-01-17 14:17 ` P. Christeas
2006-01-17 15:14 ` Ralf Baechle
2006-01-17 15:50 ` P. Christeas
2006-01-17 16:21 ` Ralf Baechle
2006-01-17 19:08 ` Ralf Baechle
2006-01-17 19:38 ` Jan-Benedict Glaw
2006-01-17 20:11 ` Daniel Jacobowitz [this message]
2006-02-17 13:57 ` Martin Michlmayr
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=20060117201108.GA11011@nevyn.them.org \
--to=dan@debian.org \
--cc=linux-mips@linux-mips.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