public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "markus.schoepflin at comsoft dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/40986] [4.6 regression] Assert_Failure sinfo.adb:360, error detected at a-unccon.ads:23:27
Date: Wed, 17 Apr 2013 09:15:00 -0000	[thread overview]
Message-ID: <bug-40986-4-JjUhwTTFIb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-40986-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #15 from Markus Schöpflin <markus.schoepflin at comsoft dot de> 2013-04-17 09:15:22 UTC ---
I have bisected the problem using the git gcc repository, unfortunately 121
commits are left after bisecting, as in between the last known good and the
first known bad commit the gcc tree does not compile for a lot of commits.

Anyway, this is the last known good commit:

commit 244de65defd519a1245551886fce58113a4b7b2a
Author: charlet <charlet@138bc75d-0d04-0410-961f-82ee72b054a4>
Date:   Wed Jun 6 10:13:25 2007 +0000

This is the first known bad commit:

commit 7b29e7de1cf940343eeeb25058b7870877d15524
Author: charlet <charlet@138bc75d-0d04-0410-961f-82ee72b054a4>
Date:   Wed Jun 6 10:54:04 2007 +0000

The 120 commits in between do not compile, and all do massive changes in the
Ada part of gcc.
>From gcc-bugs-return-420448-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Apr 17 09:18:08 2013
Return-Path: <gcc-bugs-return-420448-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13052 invoked by alias); 17 Apr 2013 09:18:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 12840 invoked by uid 48); 17 Apr 2013 09:17:36 -0000
From: "meisenmann.lba@fh-salzburg.ac.at" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/56644] --disable-nls requires symbols from libintl
Date: Wed, 17 Apr 2013 09:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: meisenmann.lba@fh-salzburg.ac.at
X-Bugzilla-Status: WAITING
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-56644-4-H3GgtR4T4h@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-56644-4@http.gcc.gnu.org/bugzilla/>
References: <bug-56644-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
X-SW-Source: 2013-04/txt/msg01593.txt.bz2
Content-length: 1059


http://gcc.gnu.org/bugzilla/show_bug.cgi?idV644

--- Comment #7 from Markus Eisenmann <meisenmann.lba@fh-salzburg.ac.at> 2013-04-17 09:17:36 UTC ---
At least this error is based on some libintl-macros, which will "redirect" some
stdio-functions (like vsnprintf ...) to their libintl-version(s); I.e. the
header-file libintl.h is available and included, but NLS/libintl isn't
requested.

Solution (as be possible by processing the attached patch/diff-file):

Add following undef's in the #else-region of gcc/intl.h (of #ifdef ENABLE_NLS),
for example after line #54:

#undef    fprintf
#undef    vfprintf
#undef    printf
#undef    vprintf
#undef    sprintf
#undef    vsprintf
#undef    snprintf
#undef    vsnprintf
#undef    asprintf
#undef    vasprintf
#undef    setlocale

Additional comment:
The header-file gcc/intl.h does already contain undef's to prevent using
libintl if not requested or configured. But not for the affected "stdio-funcs"
as vsnprintf [...], which may cause linker-errors (I.e. unresolved externals).


  parent reply	other threads:[~2013-04-17  9:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-40986-4@http.gcc.gnu.org/bugzilla/>
2011-04-08 12:33 ` [Bug ada/40986] [4.3/4.4 " markus.schoepflin at comsoft dot de
2011-06-27 15:08 ` rguenth at gcc dot gnu.org
2011-06-27 16:58 ` [Bug ada/40986] [4.4 " Markus.Schoepflin at comsoft dot aero
2011-09-01  0:29 ` nicolas.boulenguez at free dot fr
2012-03-13 16:43 ` jakub at gcc dot gnu.org
2012-03-14  8:31 ` markus.schoepflin at comsoft dot de
2012-03-19 21:50 ` [Bug ada/40986] [4.5/4.6 " nicolas.boulenguez at free dot fr
2012-07-02 13:49 ` [Bug ada/40986] [4.6 " rguenth at gcc dot gnu.org
2012-07-02 13:50 ` Markus.Schoepflin at comsoft dot aero
2013-04-12 16:11 ` jakub at gcc dot gnu.org
2013-04-12 17:17 ` ludovic@ludovic-brenta.org
2013-04-16 13:38 ` markus.schoepflin at comsoft dot de
2013-04-16 13:45 ` markus.schoepflin at comsoft dot de
2013-04-17  9:15 ` markus.schoepflin at comsoft dot de [this message]
2013-04-17 18:30 ` ludovic@ludovic-brenta.org
2013-11-10  8:09 ` [Bug ada/40986] [4.7/4.8/4.9 " pinskia at gcc dot gnu.org
2014-06-12 13:49 ` [Bug ada/40986] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-08-13 15:36 ` [Bug ada/40986] [4.8/4.9/5 " nicolas.boulenguez at free dot fr
2014-08-14 13:18 ` markus.schoepflin at comsoft dot de

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-40986-4-JjUhwTTFIb@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).