Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: [patch review] uclibc-initial_0.9.30.bb and avr32
Date: Fri, 21 Nov 2008 17:04:37 +0100	[thread overview]
Message-ID: <4926DC15.5070206@dresearch.de> (raw)

Hello uclibc maintainers,

please approve or comment following patch of uclibc-initial_0.9.30.bb.

It fixes a compile problem for the avr32 machine in the same way like for the other arm architectures.

diff --git a/packages/uclibc/uclibc_0.9.30.bb b/packages/uclibc/uclibc_0.9.30.bb
index faeaeca..e6c2318 100644
--- a/packages/uclibc/uclibc_0.9.30.bb
+++ b/packages/uclibc/uclibc_0.9.30.bb
@@ -20,6 +20,7 @@ SRC_URI += "file://uClibc.machine file://uClibc.distro \
           "
 SRC_URI_append_arm = " file://ldso_hash_arm.patch;patch=1 "
 SRC_URI_append_armeb = " file://ldso_hash_arm.patch;patch=1 "
+SRC_URI_append_avr32 = " file://ldso_hash_arm.patch;patch=1 "
 
 #recent versions uclibc require real kernel headers
 PACKAGE_ARCH = "${MACHINE_ARCH}"




             reply	other threads:[~2008-11-21 16:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-21 16:04 Steffen Sledz [this message]
2008-11-21 16:40 ` [patch review] uclibc-initial_0.9.30.bb and avr32 Steffen Sledz

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=4926DC15.5070206@dresearch.de \
    --to=sledz@dresearch.de \
    --cc=openembedded-devel@lists.openembedded.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