public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "andreast at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65535] powerpc64-freebsd build failure
Date: Sat, 04 Apr 2015 20:20:00 -0000	[thread overview]
Message-ID: <bug-65535-4-cSLQY2soS9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65535-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65535

--- Comment #1 from Andreas Tobler <andreast at gcc dot gnu.org> ---
Here a native build seems to succeed, right now in stage three with sources
from today.

[tritium:head/objdir/gcc] andreast% grep -i fbsd_major *
Makefile:tm_defines= LIBC_GLIBC=1 LIBC_UCLIBC=2 LIBC_BIONIC=3 FBSD_MAJOR=11
config.log:tm_defines=' LIBC_GLIBC=1 LIBC_UCLIBC=2 LIBC_BIONIC=3 FBSD_MAJOR=11'
config.status:S["tm_defines"]=" LIBC_GLIBC=1 LIBC_UCLIBC=2 LIBC_BIONIC=3
FBSD_MAJOR=11"
tm.h:#ifndef FBSD_MAJOR
tm.h:# define FBSD_MAJOR 11

FBSD_MAJOR is defined during configure time:

config.gcc:line 666

  fbsd_major=`echo ${target} | sed -e 's/.*freebsd//g' | sed -e 's/\..*//g'`
  tm_defines="${tm_defines} FBSD_MAJOR=${fbsd_major}"

Can you give me some details about your setup/build?


  reply	other threads:[~2015-04-04 20:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24  7:39 [Bug target/65535] New: " msebor at gcc dot gnu.org
2015-04-04 20:20 ` andreast at gcc dot gnu.org [this message]
2015-04-04 20:23 ` [Bug target/65535] " andreast at gcc dot gnu.org
2015-04-04 20:35 ` andreast at gcc dot gnu.org
2015-04-05 17:51 ` msebor at gcc dot gnu.org
2015-04-05 17:52 ` msebor at gcc dot gnu.org
2015-04-16 20:48 ` andreast at gcc dot gnu.org
2015-04-17 17:51 ` andreast at gcc dot gnu.org
2015-04-17 20:21 ` andreast at gcc dot gnu.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=bug-65535-4-cSLQY2soS9@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).