From: Martin Guy <martinwguy@gmail.com>
To: crossgcc@sourceware.org
Subject: Re: [PATCH] Fixes for avr32 target
Date: Thu, 29 Dec 2011 00:16:00 -0000 [thread overview]
Message-ID: <CAL4-wQovHC7f=y9QsLpbuQRiwdhJ3DkMXNr9mmT7ieTy=fr=5w@mail.gmail.com> (raw)
In-Reply-To: <CAL4-wQojmzQz+Cb2dVaQEOHqS7YF-H=B7f4myWTnx9pLYcCPRA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 55 bytes --]
I guess it would help if I attached the patch...
M
[-- Attachment #2: crosstool-ng-fix-avr32.patch --]
[-- Type: text/x-patch, Size: 2951 bytes --]
diff -r 43a3cb39a786 scripts/build/libc/newlib.sh
--- a/scripts/build/libc/newlib.sh Wed Dec 14 19:57:47 2011 +0100
+++ b/scripts/build/libc/newlib.sh Wed Dec 28 23:37:38 2011 +0100
@@ -15,10 +15,11 @@
do_libc_get() {
local libc_src
- local avr32headers_src
+ local avr32headers_src="http://www.atmel.com/dyn/resources/prod_documents"
+ avr32headers_base="avr32-headers-3.2.3.258" # used below
+ local avr32headers_ext=".zip"
libc_src="ftp://sources.redhat.com/pub/newlib"
- avr32headers_src="http://dev.doredevelopment.dk/avr32-toolchain/sources"
if [ -z "${CT_LIBC_NEWLIB_CVS}" ]; then
CT_GetFile "newlib-${CT_LIBC_VERSION}" ${libc_src}
@@ -31,7 +32,7 @@
fi
if [ "${CT_ATMEL_AVR32_HEADERS}" = "y" ]; then
- CT_GetFile "avr32headers" ${avr32headers_src}
+ CT_GetFile ${avr32headers_base} ${avr32_headers_ext} ${avr32headers_src}
fi
}
@@ -40,7 +41,9 @@
CT_Patch "newlib" "$(libc_newlib_version)"
if [ "${CT_ATMEL_AVR32_HEADERS}" = "y" ]; then
- CT_Extract "avr32headers"
+ # The avr32header zip file extracts to avr32/*.h
+ # Put that in its directory, the same as normal tarballs
+ CT_Extract ${avr32headers_base} -d ${CT_SRC_DIR}/${avr32headers_base}
fi
}
@@ -137,7 +140,7 @@
if [ "${CT_ATMEL_AVR32_HEADERS}" = "y" ]; then
CT_DoLog EXTRA "Installing Atmel's AVR32 headers"
- CT_DoExecLog ALL cp -r ${CT_SRC_DIR}/avr32headers "${CT_PREFIX_DIR}/${CT_TARGET}/include/avr32"
+ CT_DoExecLog ALL cp -r ${CT_SRC_DIR}/${avr32headers_base}/avr32 "${CT_PREFIX_DIR}/${CT_TARGET}/include/"
fi
CT_EndStep
diff -r 43a3cb39a786 scripts/functions
--- a/scripts/functions Wed Dec 14 19:57:47 2011 +0100
+++ b/scripts/functions Wed Dec 28 23:37:38 2011 +0100
@@ -410,6 +410,7 @@
printf ".tar.bz2\n"
printf ".tar.gz\n.tgz\n"
printf ".tar\n"
+ printf ".zip\n"
}
# Get the file name extension of a component
@@ -705,7 +706,7 @@
# by the caller, that did a 'cd' into the correct path before calling us
# and sets nochdir to 'nochdir'.
# Note also that this function handles the git trees!
-# Usage: CT_Extract <basename> [nochdir] [options]
+# Usage: CT_Extract [nochdir] <basename> [options]
# where 'options' are dependent on the source (eg. git branch/tag...)
CT_Extract() {
local nochdir="$1"
@@ -770,6 +771,7 @@
.tar.bz2) bzip2 -dc "${full_file}" | CT_DoExecLog FILE tar "${tar_opts[@]}" -f -;;
.tar.gz|.tgz) gzip -dc "${full_file}" | CT_DoExecLog FILE tar "${tar_opts[@]}" -f -;;
.tar) CT_DoExecLog FILE tar "${tar_opts[@]}" -f "${full_file}";;
+ .zip) CT_DoExecLog FILE unzip "${@}" "${full_file}";;
/.git) CT_ExtractGit "${basename}" "${@}";;
*) CT_DoLog WARN "Don't know how to handle '${basename}${ext}': unknown extension"
return 1
[-- Attachment #3: Type: text/plain, Size: 71 bytes --]
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2011-12-29 0:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-28 22:50 Martin Guy
2011-12-29 0:16 ` Martin Guy [this message]
2011-12-31 18:17 ` Yann E. MORIN
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='CAL4-wQovHC7f=y9QsLpbuQRiwdhJ3DkMXNr9mmT7ieTy=fr=5w@mail.gmail.com' \
--to=martinwguy@gmail.com \
--cc=crossgcc@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).