Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 4928] New: internal compiler error in varasm.c
Date: Thu, 15 Mar 2012 14:58:39 +0000 (UTC)	[thread overview]
Message-ID: <bug-4928-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=4928

           Summary: internal compiler error in varasm.c
           Product: buildroot
           Version: 2012.02
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: blocker
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: erland at lewin.nu
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Building buildroot 2012.02 form arm / arm7tdmi, EABI, buildroot toolchain,
Linux 2.6.24, uClibc 0.9.33.x, binutils 2.22, gcc 4.6.x, elf2flt enabled,
enable large files.

Error building uClibC: 

libc/misc/internals/errno.c:8:1: internal compiler error: in do_assemble_alias,
at varasm.c:5444
Please submit a full bug report,
with preprocessed source if appropriate.

Host is 64 bit Ubuntu 10.10 I think.

I can repeat error by doing make clean and then make again.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2012-03-15 14:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15 14:58 bugzilla at busybox.net [this message]
2012-05-07 12:30 ` [Buildroot] [Bug 4928] internal compiler error in varasm.c bugzilla at busybox.net
2013-05-26 13:56 ` bugzilla at busybox.net

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-4928-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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