All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 1153] New: Buildroot fails to build packages if BR2_GCC_SHARED_LIBGCC=y
Date: Fri, 19 Feb 2010 15:58:59 +0000 (UTC)	[thread overview]
Message-ID: <bug-1153-163@https.bugs.busybox.net/> (raw)

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

              Host: i686
            Target: ARM
           Summary: Buildroot fails to build packages if
                    BR2_GCC_SHARED_LIBGCC=y
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Keywords: link-failure
          Severity: major
          Priority: P2
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: akennedy at drs-tem.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created an attachment (id=1153)
 --> (https://bugs.busybox.net/attachment.cgi?id=1153)
Config file for building an NFS buildroot for development purposes.

The config file attached has left off these two, but these were giving me
errors as well:

docker
xstroke

These would NOT compile unless BR2_GCC_SHARED_LIBGCC is not set:
uemacs
nano
vim

The error was undefined hidden symbol in libgcc.a(xxxxxxx.o)  '__xxxxx()'
referenced by DSO.

The xxx was different for each of these (I attempted to compile each with a
shared libgcc) but seemed to center on references to g_printerr, g_print,
g_slist_length, g_malloc0, g_free, g_slist_append, g_slist_Remove_link, and
g_strdup_printf.  These seem to be calling functions from the EABI as some were
like ul_div32_helper() -- though some were not referred to as EABI but AABI,
which greatly confuse me.

It appeared that the source of the problem was in glib2, but I cannot verify
this and could not locate any way around this issue.

My gut tells me that linking libgcc.a in statically is "bad" and I prefer not
to do that, but I'm in a bit over my head with where the problem is.


-- 
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:[~2010-02-19 15:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-19 15:58 bugzilla at busybox.net [this message]
2010-02-19 16:50 ` [Buildroot] [Bug 1153] Buildroot fails to build packages if BR2_GCC_SHARED_LIBGCC=y bugzilla at busybox.net
2010-02-21 18:51 ` bugzilla at busybox.net
2010-02-24 18:11 ` bugzilla at busybox.net
2013-09-23 10:06 ` bugzilla at busybox.net
2013-09-23 13:17 ` 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-1153-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.