public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "remy.garrigue at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/51330] New: Compiling issue that seems specific to i586 with gcc 4.6
Date: Mon, 28 Nov 2011 10:08:00 -0000	[thread overview]
Message-ID: <bug-51330-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 51330
           Summary: Compiling issue that seems specific to i586 with gcc
                    4.6
    Classification: Unclassified
           Product: gcc
           Version: 4.6.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: remy.garrigue@gmail.com


I'm currently in charge of packaging some sources code, and I've an issue that
SEEMS to be related to gcc 4.6. Not sure thou, I'm not an expert either in the
code nor c/c++

You can find the packaging here:
https://build.opensuse.org/package/show?package=xtreemfs-1.2.3&project=home%3Axtreemfs

As you can see there, packaging for latest opensuse (12.1, factory,
tumbleweed), ubuntu 11.10 and fedora (15, 16) fails under i586 arch. Clic on
the red "failed" or the green "succeeded", then "download log file" and you'll
have the full log, with environment (and gcc) installation plus compilation. 

My point is, with gcc 4.5 older distro packaging is doing fine. With gcc 4.6,
latest one fails on i586. It may be something else, but this is as far as I can
diagnose.

I'm available to give a hand to set up an environment to reproduce my issue and
will be glad of any further information to solve my issue.

Regards,
Rémy


             reply	other threads:[~2011-11-28  9:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-28 10:08 remy.garrigue at gmail dot com [this message]
2011-11-28 10:25 ` [Bug target/51330] " pinskia at gcc dot gnu.org
2011-11-28 11:51 ` remy.garrigue at gmail dot com
2011-11-28 12:06 ` redi at gcc dot gnu.org
2011-11-29  9:54 ` remy.garrigue at gmail dot com
2012-01-10 15:13 ` rguenth 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-51330-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).