Skip to contentSkip to conversation

ARC: bump tools to 2014.08 release

PATCH Superseded Alexey Brodkin 3 participants 11 messages Aug 21, 2014 – Sep 1, 2014

lore
Share & tools
lore
#0 lore raw

PATCH v2 1/1 ARC: bump tools to 2014.08 release

Now when new shiny tools are released by Synopsys we're ready for version update in Buildroot.

Important change in this release is switching to combined "binutils-gdb" repo in accordance to upstream move.

Following patch now is a part of the most recent relese:
https://github.com/foss-for-synopsys-dwc-arc-processors/binutils-gdb/commit/e6ab8cac627a44a7594aeb907a579d8d2f066ba5

So dropping it. package/binutils/arc-4.8-R3/0001-arc-Honor-DESTDIR-in-custom-Makefile.patch

Since arc-2014.08 tools are still based on GCC 4.8 following patch is still relevant so moving to the new folder to matxh ARC gcc bump. package/gcc/arc-4.8-R3/100-libstdcxx-uclibc-c99.patch -> package/gcc/arc-2014.08/100-libstdcxx-uclibc-c99.patch

Cc Anton Kolesov <[email protected]>
Cc Thomas Petazzoni <[email protected]>
Cc Peter Korsgaard <[email protected]>

---
Compared to v1 obsolete patch was removed and another one for gcc moved to another location to match new arc gcc version.

Thanks to Thomas for his attention.

---
 package/binutils/Config.in.host                    |   2 +-
 ...0001-arc-Honor-DESTDIR-in-custom-Makefile.patch |  47 ----
 package/binutils/binutils.mk                       |   2 +-
 package/gcc/Config.in.host                         |   2 +-
 .../gcc/arc-2014.08/100-libstdcxx-uclibc-c99.patch | 273 +++++++++++++++++++++
 .../gcc/arc-4.8-R3/100-libstdcxx-uclibc-c99.patch  | 273 ---------------------
 package/gdb/Config.in.host                         |   2 +-
 package/gdb/gdb.mk                                 |   2 +-
 package/uclibc/Config.in                           |   2 +-
 9 files changed, 279 insertions(+), 326 deletions(-)
 delete mode 100644 package/binutils/arc-4.8-R3/0001-arc-Honor-DESTDIR-in-custom-Makefile.patch
 create mode 100644 package/gcc/arc-2014.08/100-libstdcxx-uclibc-c99.patch
 delete mode 100644 package/gcc/arc-4.8-R3/100-libstdcxx-uclibc-c99.patch
package/binutils/Config.in.host +1 -1
index de8b780..826db6d 100644
@@ -29,7 +29,7 @@ endchoice
 config BR2_BINUTILS_VERSION
 	string
 	default "2.18-avr32-1.0.1" if BR2_BINUTILS_VERSION_2_18_AVR32_1_0_1
-	default "arc-4.8-R3"	if BR2_arc
+	default "arc-2014.08"	if BR2_arc
 	default "2.22"		if BR2_BINUTILS_VERSION_2_22
 	default "2.23.2"	if BR2_BINUTILS_VERSION_2_23_2
 	default "2.24"		if BR2_BINUTILS_VERSION_2_24
package/binutils/arc-4.8-R3/0001-arc-Honor-DESTDIR-in-custom-Makefile.patch deleted +0 -47

47 lines not on this page · raw message

package/binutils/binutils.mk +1 -1
index 4888eeb..5ec420a 100644
@@ -24,7 +24,7 @@ ifeq ($(ARCH),avr32)
 BINUTILS_SITE = ftp://www.at91.com/pub/buildroot
 endif
 ifeq ($(BR2_arc),y)
-BINUTILS_SITE = $(call github,foss-for-synopsys-dwc-arc-processors,binutils,$(BINUTILS_VERSION))
+BINUTILS_SITE = $(call github,foss-for-synopsys-dwc-arc-processors,binutils-gdb,$(BINUTILS_VERSION))
 BINUTILS_SOURCE = binutils-$(BINUTILS_VERSION).tar.gz
 BINUTILS_FROM_GIT = y
 endif
package/gcc/Config.in.host +1 -1
index b29bacb..b536a66 100644
@@ -99,7 +99,7 @@ config BR2_GCC_VERSION
 	default "4.7.4"     if BR2_GCC_VERSION_4_7_X
 	default "4.8.3"     if BR2_GCC_VERSION_4_8_X
 	default "4.9.1"     if BR2_GCC_VERSION_4_9_X
-	default "arc-4.8-R3" if BR2_GCC_VERSION_4_8_ARC
+	default "arc-2014.08" if BR2_GCC_VERSION_4_8_ARC
 	default BR2_GCC_SNAP_DATE if BR2_GCC_VERSION_SNAP
 
 config BR2_EXTRA_GCC_CONFIG_OPTIONS
package/gcc/arc-2014.08/100-libstdcxx-uclibc-c99.patch new file +273 -0

273 lines not on this page · raw message

package/gcc/arc-4.8-R3/100-libstdcxx-uclibc-c99.patch deleted +0 -273

273 lines not on this page · raw message

package/gdb/Config.in.host +1 -1
index cbc1361..1ce8573 100644
@@ -44,7 +44,7 @@ config BR2_GDB_VERSION
 	depends on BR2_PACKAGE_GDB || BR2_PACKAGE_HOST_GDB
 	default "6.7.1-avr32-2.1.5" if BR2_GDB_VERSION_6_7_1_AVR32_2_1_5 || \
                                    (!BR2_PACKAGE_HOST_GDB && BR2_avr32)
-	default "arc-4.8-R3" if BR2_arc
+	default "arc-2014.08-gdb" if BR2_arc
 	default "6be65fb56ea6694a9260733a536a023a1e2d4d57" if BR2_microblaze
 	default "7.6.2"    if BR2_GDB_VERSION_7_6 || !BR2_PACKAGE_HOST_GDB
 	default "7.7.1"    if BR2_GDB_VERSION_7_7 || BR2_powerpc64le
package/gdb/gdb.mk +1 -1
index 8ab264b..80d8f60 100644
@@ -8,7 +8,7 @@ GDB_VERSION = $(call qstrip,$(BR2_GDB_VERSION))
 GDB_SITE    = $(BR2_GNU_MIRROR)/gdb
 
 ifeq ($(BR2_arc),y)
-GDB_SITE = $(call github,foss-for-synopsys-dwc-arc-processors,gdb,$(GDB_VERSION))
+GDB_SITE = $(call github,foss-for-synopsys-dwc-arc-processors,binutils-gdb,$(GDB_VERSION))
 GDB_SOURCE = gdb-$(GDB_VERSION).tar.gz
 GDB_FROM_GIT = y
 endif
package/uclibc/Config.in +1 -1
index 851ad1e..d319ae7 100644
@@ -42,7 +42,7 @@ config BR2_UCLIBC_VERSION_STRING
 	string
 	default 0.9.31.1	if BR2_UCLIBC_VERSION_0_9_31
 	default 0.9.33.2	if BR2_UCLIBC_VERSION_0_9_33
-	default "8af9dc8f714d20a68df034f6ed1ededc2d752f5b" if BR2_arc
+	default "arc-2014.08" if BR2_arc
 	default "7bf35c8b7d4a1f97174eb49f47f33946b282114c" if BR2_UCLIBC_VERSION_XTENSA_GIT
 	default BR2_USE_UCLIBC_SNAPSHOT	if BR2_UCLIBC_VERSION_SNAPSHOT
 
Signature · 1 line
1.9.3
#1 lore raw

PATCH v2 1/1 ARC: bump tools to 2014.08 release

Hi Peter, Thomas,

Quoted 17 lines · Alexey Brodkin

Now when new shiny tools are released by Synopsys we're ready for version update in Buildroot.

Important change in this release is switching to combined "binutils-gdb" repo in accordance to upstream move.

Following patch now is a part of the most recent relese:
https://github.com/foss-for-synopsys-dwc-arc-processors/binutils-gdb/commit/e6ab8cac627a44a7594aeb907a579d8d2f066ba5

So dropping it. package/binutils/arc-4.8-R3/0001-arc-Honor-DESTDIR-in-custom-Makefile.patch

Since arc-2014.08 tools are still based on GCC 4.8 following patch is still relevant so moving to the new folder to matxh ARC gcc bump. package/gcc/arc-4.8-R3/100-libstdcxx-uclibc-c99.patch -> package/gcc/arc-2014.08/100-libstdcxx-uclibc-c99.patch

Quoted 8 lines
Cc Anton Kolesov <[email protected]>
Cc Thomas Petazzoni <[email protected]>
Cc Peter Korsgaard <[email protected]>

---
Compared to v1 obsolete patch was removed and another one for gcc moved to another location to match new arc gcc version.

I'm wondering if there's still a chance to get this patch applied before 2014.08 release?

Regards,
Alexey

#2 lore raw

PATCH v2 1/1 ARC: bump tools to 2014.08 release

Dear Alexey Brodkin,

Quoted 2 lines · Alexey Brodkin

I'm wondering if there's still a chance to get this patch applied before 2014.08 release?

My feeling is that it was submitted too late to get applied to 2014.08. Generally speaking, we don't merge any version bump after -rc1 has been tagged, unless those bumps are known to fix important issues.

Therefore, I believe this change qualifies for the next branch, and will therefore be part of the 2014.11 Buildroot release.

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
#3 lore raw

PATCH v2 1/1 ARC: bump tools to 2014.08 release

Hi Thomas,

Quoted 7 lines · Thomas Petazzoni

Dear Alexey Brodkin,

Quoted 2 lines · Alexey Brodkin

I'm wondering if there's still a chance to get this patch applied before 2014.08 release?

Quoted 6 lines

My feeling is that it was submitted too late to get applied to 2014.08. Generally speaking, we don't merge any version bump after -rc1 has been tagged, unless those bumps are known to fix important issues.

Therefore, I believe this change qualifies for the next branch, and will therefore be part of the 2014.11 Buildroot release.

Sure, makes perfect sense!

Unfortunately we were a bit late with our release so yes let's apply it to the next.

Regards,
Alexey

#4 lore raw

PATCH v2 1/1 ARC: bump tools to 2014.08 release

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Alexey" == Alexey Brodkin <[email protected]> writes:

Hi,

Quoted 7 lines
Quoted 7 lines
Quoted 2 lines

I'm wondering if there's still a chance to get this patch applied before 2014.08 release?

My feeling is that it was submitted too late to get applied to 2014.08. Generally speaking, we don't merge any version bump after -rc1 has been tagged, unless those bumps are known to fix important issues.

Quoted 7 lines
Quoted 2 lines

Therefore, I believe this change qualifies for the next branch, and will therefore be part of the 2014.11 Buildroot release.

Sure, makes perfect sense!

Unfortunately we were a bit late with our release so yes let's apply it to the next.

I agree. The current patch doesn't apply to next. Care to rebase and resend?

Signature · 1 line
Bye, Peter Korsgaard 
#5 lore raw

PATCH v2 1/1 ARC: bump tools to 2014.08 release

Hi Peter,

Quoted 14 lines · Peter Korsgaard
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Alexey" == Alexey Brodkin <[email protected]> writes:

Hi,

Quoted 9 lines
Quoted 9 lines
Quoted 2 lines

I'm wondering if there's still a chance to get this patch applied before 2014.08 release?

My feeling is that it was submitted too late to get applied to 2014.08. Generally speaking, we don't merge any version bump after -rc1 has been tagged, unless those bumps are known to fix important issues.

Therefore, I believe this change qualifies for the next branch, and will therefore be part of the 2014.11 Buildroot release.

Quoted 7 lines
Quoted 4 lines

Sure, makes perfect sense!

Unfortunately we were a bit late with our release so yes let's apply it to the next.

I agree. The current patch doesn't apply to next. Care to rebase and resend?

Do I have any options? :)

I mean anyway after you guys cut final 2014.08 release "next" branch will be merged with current master, right?

If so I have no other choice other than rebase and resend. Correct me if I'm wrong.

-Alexey

#6 lore raw

PATCH v2 1/1 ARC: bump tools to 2014.08 release

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Alexey" == Alexey Brodkin <[email protected]> writes:

Hi,

Quoted 10 lines
Quoted 2 lines

I agree. The current patch doesn't apply to next. Care to rebase and resend?

Do I have any options? :)

I mean anyway after you guys cut final 2014.08 release "next" branch will be merged with current master, right?

If so I have no other choice other than rebase and resend. Correct me if I'm wrong.

Well, you can let me do the rebase myself, but it will probably go faster if you do it.

Thanks.

Signature · 1 line
Bye, Peter Korsgaard 
#7 lore raw

PATCH v2 1/1 ARC: bump tools to 2014.08 release

Hi Peter,

Quoted 12 lines · Peter Korsgaard
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Alexey" == Alexey Brodkin <[email protected]> writes:

Hi,

Quoted 7 lines
Quoted 2 lines

I agree. The current patch doesn't apply to next. Care to rebase and resend?

Do I have any options? :)

I mean anyway after you guys cut final 2014.08 release "next" branch will be merged with current master, right?

Quoted 7 lines
Quoted 2 lines

If so I have no other choice other than rebase and resend. Correct me if I'm wrong.

Well, you can let me do the rebase myself, but it will probably go faster if you do it.

Thanks.

Sure I'll do it myself shortly :)

-Alexey

#8 lore raw

PATCH v2 1/1 ARC: bump tools to 2014.08 release

In reply to Peter Korsgaard

Hi Peter,

Quoted 9 lines · Peter Korsgaard
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Alexey" == Alexey Brodkin <[email protected]> writes:

Hi,

Quoted 4 lines
Quoted 2 lines

I agree. The current patch doesn't apply to next. Care to rebase and resend?

Do I have any options? :)

Quoted 8 lines
Quoted 5 lines

I mean anyway after you guys cut final 2014.08 release "next" branch will be merged with current master, right?

If so I have no other choice other than rebase and resend. Correct me if I'm wrong.

Well, you can let me do the rebase myself, but it will probably go faster if you do it.

I've just checked what's the difference between master and next that causes problems on patch application.

And it looks the reason is in "next" there's a commit missing:
--->---
gcc/arc-4.8-R3: add patch to enable more C++ features with uClibc
http://git.buildroot.net/buildroot/commit/package/gcc/arc-4.8-R3?id=4bb2a05e8133f2f553b8e0cd6af53dfa8b8208b1
https://patchwork.ozlabs.org/patch/379707/
--->---

And since this patch
(package/binutils/arc-4.8-R3/0001-arc-Honor-DESTDIR-in-custom-Makefile.patch) should be moved to "arc-2014.08" (and my current v2 change does it) I'm not sure if there's a reason to do changes to "next" or just wait before "master" is open to new submissions.

Otherwise we may whether lose history or Thomas' patch.

Let me know if that's fine for this v2 to be applied later directly on "master".

-Alexey

#9 lore raw

PATCH v2 1/1 ARC: bump tools to 2014.08 release

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Alexey" == Alexey Brodkin <[email protected]> writes:

Hi,

Quoted 7 lines
Quoted 2 lines

Well, you can let me do the rebase myself, but it will probably go faster if you do it.

I've just checked what's the difference between master and next that causes problems on patch application.

And it looks the reason is in "next" there's a commit missing:

---> ---

Quoted 3 lines

gcc/arc-4.8-R3: add patch to enable more C++ features with uClibc
http://git.buildroot.net/buildroot/commit/package/gcc/arc-4.8-R3?id=4bb2a05e8133f2f553b8e0cd6af53dfa8b8208b1
https://patchwork.ozlabs.org/patch/379707/

---> ---

Quoted 7 lines

And since this patch
(package/binutils/arc-4.8-R3/0001-arc-Honor-DESTDIR-in-custom-Makefile.patch) should be moved to "arc-2014.08" (and my current v2 change does it) I'm not sure if there's a reason to do changes to "next" or just wait before "master" is open to new submissions.

Otherwise we may whether lose history or Thomas' patch.

Let me know if that's fine for this v2 to be applied later directly on "master".

Yes, I will apply v2 now that next has been merged into master. Thanks.

Signature · 1 line
Bye, Peter Korsgaard 
#10 lore raw

PATCH v2 1/1 ARC: bump tools to 2014.08 release

In reply to Alexey Brodkin
Quoted 19 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Alexey" == Alexey Brodkin <[email protected]> writes:

Now when new shiny tools are released by Synopsys we're ready for version update in Buildroot.

Important change in this release is switching to combined "binutils-gdb" repo in accordance to upstream move.

Following patch now is a part of the most recent relese:
https://github.com/foss-for-synopsys-dwc-arc-processors/binutils-gdb/commit/e6ab8cac627a44a7594aeb907a579d8d2f066ba5

So dropping it. package/binutils/arc-4.8-R3/0001-arc-Honor-DESTDIR-in-custom-Makefile.patch

Since arc-2014.08 tools are still based on GCC 4.8 following patch is still relevant so moving to the new folder to matxh ARC gcc bump. package/gcc/arc-4.8-R3/100-libstdcxx-uclibc-c99.patch -> package/gcc/arc-2014.08/100-libstdcxx-uclibc-c99.patch

Quoted 8 lines
Cc Anton Kolesov <[email protected]>
Cc Thomas Petazzoni <[email protected]>
Cc Peter Korsgaard <[email protected]>

---
Compared to v1 obsolete patch was removed and another one for gcc moved to another location to match new arc gcc version.

Committed, thanks.

Signature · 2 lines
Venlig hilsen,
Peter Korsgaard