All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Eisele <konrad@gaisler.com>
To: buildroot@busybox.net
Subject: [Buildroot] sparc gdb-targetserver and sparc-v7 shared library generation
Date: Thu, 18 Nov 2010 15:03:08 +0100	[thread overview]
Message-ID: <4CE5321C.8010202@gaisler.com> (raw)

Hello,
2 additional patches:
 + 0005-gdb-Add-sparc-support-to-gdbserver.patch
   adds SPARC support to gdb target server
   (gdb-6.8/gdb/gdbserver/*)
 + 0006-config-Remove-automatic-disable-of-shared-library-fo.patch
   disables the automatic disable of shared library for
   sparc-v7. I dont see a dependency between shared library and v7.
   The difference between v7 and v8 is that in v8 you have
   the added math asm-insns: smul/umul/udiv/sdiv/urem.
   It shouldnt affect shared libraries creation.

One effect of 0006-config-Remove-automatic-disable-of-shared-library-fo.patch
is that you dont need BR2_EXTRA_GCC_CONFIG_OPTIONS="--disable-libgomp"
for the default build because libgomp's build needs shared libraries to succeed.

-- Greetings Konrad
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0005-gdb-Add-sparc-support-to-gdbserver.patch
Type: text/x-patch
Size: 13971 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20101118/77256409/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0006-config-Remove-automatic-disable-of-shared-library-fo.patch
Type: text/x-patch
Size: 1230 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20101118/77256409/attachment-0003.bin>

                 reply	other threads:[~2010-11-18 14:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4CE5321C.8010202@gaisler.com \
    --to=konrad@gaisler.com \
    --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.