public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/23356] New: FLT_EVAL_METHOD not defined on openbsd3.4 Date: Fri, 12 Aug 2005 17:08:00 -0000 [thread overview] Message-ID: <20050812170822.23356.fxcoudert@gcc.gnu.org> (raw) On openbsd3.4, there is no FLT_EVAL_METHOD in the standard includes, so we should think of something to do when it's not available: /tmp/debug/ibin/./gcc/xgcc -B/tmp/debug/ibin/./gcc -B/tmp/debug/irun/i386-unknown-openbsd3.4/bin/ -B/tmp/debug/irun/i386-unknown-openbsd3.4/lib/ -isystem /tmp/debug/irun/i386-unknown-openbsd3.4/include -isystem /tmp/debug/irun/i386-unknown-openbsd3.4/sys-include -DHAVE_CONFIG_H -I. -I../../../gcc/libgfortran -I. -iquote../../../gcc/libgfortran/io -std=gnu99 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -Wextra -Wwrite-strings -O2 -g -O2 -c ../../../gcc/libgfortran/generated/nearest_r4.c -fPIC -DPIC -o .libs/nearest_r4.o ../../../gcc/libgfortran/generated/nearest_r4.c: In function 'nearest_r4': ../../../gcc/libgfortran/generated/nearest_r4.c:42: error: 'FLT_EVAL_METHOD' undeclared (first use in this function) -- Summary: FLT_EVAL_METHOD not defined on openbsd3.4 Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: libfortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: fxcoudert at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org GCC target triplet: i386-unknown-openbsd3.4 OtherBugsDependingO 16991 nThis: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23356
next reply other threads:[~2005-08-12 17:08 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-12 17:08 fxcoudert at gcc dot gnu dot org [this message] 2005-08-12 22:13 ` [Bug libfortran/23356] " pinskia at gcc dot gnu dot org 2005-08-30 16:01 ` fxcoudert at gcc dot gnu dot org 2005-09-06 17:48 ` ian at airs dot com 2005-09-08 20:58 ` [Bug target/23356] " fxcoudert at gcc dot gnu dot org
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=20050812170822.23356.fxcoudert@gcc.gnu.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).