public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mexas at bristol dot ac.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug regression/53964] New: regression: sparc64 FreeBSD: /usr/ports/lang/gcc46/work/build/./prev-gcc/include/stddef.h:150:26: error: two or more data types n declaration specifiers
Date: Sat, 14 Jul 2012 16:18:00 -0000	[thread overview]
Message-ID: <bug-53964-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53964

             Bug #: 53964
           Summary: regression: sparc64 FreeBSD:
                    /usr/ports/lang/gcc46/work/build/./prev-gcc/include/st
                    ddef.h:150:26: error: two or more data types n
                    declaration specifiers
    Classification: Unclassified
           Product: gcc
           Version: 4.6.4
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: regression
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: mexas@bristol.ac.uk


FreeBSD 10.0-CURRENT #4 r235474 sparc64

# pkg info -xo gcc
gcc-4.6.4.20120413: lang/gcc46
gcc-4.7.1.20120414: lang/gcc47
#

Updating gcc46 gives:

gmake[3]: Entering directory `/usr/ports/lang/gcc46/work/build/libcpp'
/usr/ports/lang/gcc46/work/build/./prev-gcc/xgcc
-B/usr/ports/lang/gcc46/work/build/./prev-gcc/
-B/sr/local/sparc64-portbld-freebsd10.0/bin/
-B/usr/local/sparc64-portbld-freebsd10.0/bin/
-B/usr/loca/sparc64-portbld-freebsd10.0/lib/ -isystem
/usr/local/sparc64-portbld-freebsd10.0/include -isystem
usr/local/sparc64-portbld-freebsd10.0/sys-include    
-I.././../gcc-4.6-20120608/libcpp -I.
-I../././gcc-4.6-20120608/libcpp/../include
-I.././../gcc-4.6-20120608/libcpp/include  -g -O2 -gtoggle -W Wall
-Wwrite-strings -Wmissing-format-attribute -Wstrict-prototypes
-Wmissing-prototypes -Wold-styl-definition -Wc++-compat -pedantic
-Wno-long-long  -I.././../gcc-4.6-20120608/libcpp -I.
-I.././../cc-4.6-20120608/libcpp/../include
-I.././../gcc-4.6-20120608/libcpp/include  -c -o charset.o -MT chrset.o -MMD
-MP -MF .deps/charset.Tpo .././../gcc-4.6-20120608/libcpp/charset.c
In file included from .././../gcc-4.6-20120608/libcpp/system.h:30:0,
                 from .././../gcc-4.6-20120608/libcpp/charset.c:22:
/usr/ports/lang/gcc46/work/build/./prev-gcc/include/stddef.h:150:26: error: two
or more data types n declaration specifiers
gmake[3]: *** [charset.o] Error 1


             reply	other threads:[~2012-07-14 16:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-14 16:18 mexas at bristol dot ac.uk [this message]
2012-07-15 10:50 ` [Bug regression/53964] " mexas at bristol dot ac.uk
2012-07-15 11:00 ` mexas at bristol dot ac.uk
2012-07-15 13:23 ` gerald at pfeifer dot com
2012-07-15 13:58 ` mexas at bristol dot ac.uk
2012-09-04 16:09 ` mexas at bristol dot ac.uk
2012-09-05  8:44 ` mexas at bristol dot ac.uk
2013-01-23 10:15 ` mexas at bristol dot ac.uk
2013-06-06  8:52 ` mexas at bristol dot ac.uk
2013-06-10  7:59 ` mexas at bristol dot ac.uk

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=bug-53964-4@http.gcc.gnu.org/bugzilla/ \
    --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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).