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 7946] New: libglib2-2.42.2 fails to build for sparc-buildroot-linux-gnu
Date: Tue, 17 Mar 2015 23:35:20 +0000 (UTC)	[thread overview]
Message-ID: <bug-7946-163@https.bugs.busybox.net/> (raw)

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

              Host: x86_64
            Target: sparc-buildroot-linux-gnu
           Summary: libglib2-2.42.2 fails to build for
                    sparc-buildroot-linux-gnu
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: uwe at hermann-uwe.de
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


This is buildroot git HEAD as of today, with glibc 2.21 and gcc-4.8.

make[5]: Entering directory
'/home/jenkins_slave/buildroot-sparc-buildroot-linux-gnu/output/build/libglib2-2.42.2/glib'
  CCLD     gtester
./.libs/libglib-2.0.so: undefined reference to `__atomic_compare_exchange_4'
collect2: error: ld returned 1 exit status
Makefile:1446: recipe for target 'gtester' failed
make[5]: *** [gtester] Error 1

-- 
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:[~2015-03-17 23:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17 23:35 bugzilla at busybox.net [this message]
2015-07-30 10:08 ` [Buildroot] [Bug 7946] libglib2-2.42.2 fails to build for sparc-buildroot-linux-gnu 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-7946-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