<feed xmlns='http://www.w3.org/2005/Atom'>
<title>staging/kaloz/toolchain, branch master</title>
<subtitle>Staging tree of Imre Kaloz</subtitle>
<id>https://git.openwrt.org/openwrt/staging/kaloz/atom?h=master</id>
<link rel='self' href='https://git.openwrt.org/openwrt/staging/kaloz/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/kaloz/'/>
<updated>2018-02-10T19:15:52Z</updated>
<entry>
<title>toolchain: gdb: activate on ARM64</title>
<updated>2018-02-10T19:15:52Z</updated>
<author>
<name>Hauke Mehrtens</name>
</author>
<published>2018-02-05T21:39:58Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/kaloz/commit/?id=e387a1b4e4f57ec6e436990bca3de5de8d840d80'/>
<id>urn:sha1:e387a1b4e4f57ec6e436990bca3de5de8d840d80</id>
<content type='text'>
gdb supports ARM64 since quite some time now, activate it there like on
other CPU architectures.

Signed-off-by: Hauke Mehrtens &lt;hauke@hauke-m.de&gt;
</content>
</entry>
<entry>
<title>binutils: assertion failure bfd/elfxx-mips.c:3860</title>
<updated>2018-01-27T21:51:59Z</updated>
<author>
<name>Hauke Mehrtens</name>
</author>
<published>2018-01-27T21:51:59Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/kaloz/commit/?id=bcd17ce9a3308accc30d99f4dd43f2062bb3fabc'/>
<id>urn:sha1:bcd17ce9a3308accc30d99f4dd43f2062bb3fabc</id>
<content type='text'>
With forced PIE and SSP support I ran into this assertion failure.
backport two patches to fix this problem from the binutils 2.28 branch.
This fix is already included in binutils 2.28.1 and 2.29.

Signed-off-by: Hauke Mehrtens &lt;hauke@hauke-m.de&gt;
</content>
</entry>
<entry>
<title>toolchain: gcc: update 7.x to 7.3.0</title>
<updated>2018-01-27T18:54:52Z</updated>
<author>
<name>Hauke Mehrtens</name>
</author>
<published>2018-01-27T13:28:46Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/kaloz/commit/?id=1a8523c83530fcfc2607723e803e347dd5c50ec4'/>
<id>urn:sha1:1a8523c83530fcfc2607723e803e347dd5c50ec4</id>
<content type='text'>
This version still generates broken code in our setup for MIPS.

Signed-off-by: Hauke Mehrtens &lt;hauke@hauke-m.de&gt;
</content>
</entry>
<entry>
<title>build: cleanup SSP_SUPPORT configure option</title>
<updated>2018-01-27T18:02:48Z</updated>
<author>
<name>Julien Dusser</name>
</author>
<published>2018-01-07T17:47:21Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/kaloz/commit/?id=241e6dd3e92c4f215b8ac75379a4b5aeaeb92171'/>
<id>urn:sha1:241e6dd3e92c4f215b8ac75379a4b5aeaeb92171</id>
<content type='text'>
Configure variable SSP_SUPPORT is ambiguous for packages (tor, openssh,
avahi, freeswitch). It means 'toolchain supporting SSP', but for toolchain
and depends it means 'build gcc with libssp'.

Musl no longer uses libssp (1877bc9d8f), it has internal support, so
SSP_SUPPORT was disabled leading some package to not use SSP.

No information why Glibc and uClibc use libssp, but they may also provide
their own SSP support. uClibc used it own with commit 933b588e25 but it was
reverted in f3cacb9e84 without details.

Create an new configure GCC_LIBSSP and automatically enable SSP_SUPPORT
if either USE_MUSL or GCC_LIBSSP.

Signed-off-by: Julien Dusser &lt;julien.dusser@free.fr&gt;
</content>
</entry>
<entry>
<title>toolchain: add gcc configure default PIE and SSP</title>
<updated>2018-01-27T18:02:47Z</updated>
<author>
<name>Julien Dusser</name>
</author>
<published>2018-01-07T16:41:35Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/kaloz/commit/?id=55779569eb817361222d653accd929a752b8327d'/>
<id>urn:sha1:55779569eb817361222d653accd929a752b8327d</id>
<content type='text'>
GCC supports starting version 5 --enable-default-ssp and starting version 6
--enable-default-pie.

It produces hardened binaries by default without dealing with package
compilation flags.

Signed-off-by: Julien Dusser &lt;julien.dusser@free.fr&gt;
</content>
</entry>
<entry>
<title>kernel-headers: adjust PKG_ variables when using git clone method</title>
<updated>2018-01-27T15:46:45Z</updated>
<author>
<name>Alexandru Ardelean</name>
</author>
<published>2018-01-17T10:55:15Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/kaloz/commit/?id=ca7e8627dbbbcae0d1bfacea51d9b564617195de'/>
<id>urn:sha1:ca7e8627dbbbcae0d1bfacea51d9b564617195de</id>
<content type='text'>
When using an external git clone for the kernel repo,
the build would fail because the build won't download
[via git] the kernel tarball.

This is because the `toolchain/kernel-headers` assumes
that the kernel would get downloaded via normal HTTP.
The reason for this is the `HostBuild` rule, which
calls the `Download/default` rule.

To use the `Download/default` we just need to conditionally
adjust some PKG_ vars.

We can safely use `LINUX_VERSION` as it was already adjusted
in the `kernel-version.mk` to avoid collisions with other tarballs.

Fixes:
 https://bugs.openwrt.org/index.php?do=details&amp;task_id=503

Signed-off-by: Alexandru Ardelean &lt;ardeleanalex@gmail.com&gt;
</content>
</entry>
<entry>
<title>toolchain/arc: update to the most recent release arc-2017.09</title>
<updated>2018-01-27T15:46:44Z</updated>
<author>
<name>Evgeniy Didin</name>
</author>
<published>2018-01-24T17:26:03Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/kaloz/commit/?id=e47fe3284f25c0d7354f239ea8424b96dfe5b36d'/>
<id>urn:sha1:e47fe3284f25c0d7354f239ea8424b96dfe5b36d</id>
<content type='text'>
This commit finally bumps ARC tools to the most recent arc-2017.09 release version.

ARC GNU tools of version arc-2017.09 bring some quite significant changes like:
 * Binutils v2.29 with additional ARC patches
 * GCC 7.1.1 with additional ARC patches

More information on this release could be found here:
  https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/releases/tag/arc-2017.09-release

Signed-off-by: Evgeniy Didin &lt;Evgeniy.Didin@synopsys.com&gt;
CC: Alexey Brodkin &lt;abrodkin@synopsys.com&gt;
CC: John Crispin &lt;john@phrozen.org&gt;
</content>
</entry>
<entry>
<title>uClibc-ng: update to 1.0.28</title>
<updated>2018-01-27T15:46:44Z</updated>
<author>
<name>Evgeniy Didin</name>
</author>
<published>2018-01-24T17:26:02Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/kaloz/commit/?id=53021ce7f24b0fd80a6f50517a25d762d783102b'/>
<id>urn:sha1:53021ce7f24b0fd80a6f50517a25d762d783102b</id>
<content type='text'>
Lets update uClibc-ng to 1.0.28 version for compatibility with gcc 7.x.

Since 1.0.22 there were significant patches for compatibility with gcc 7.x:
 https://cgit.uclibc-ng.org/cgi/cgit/uclibc-ng.git/commit/?id=5b0f49037e8ea8500b05c8f31ee88529ccac4cee
 https://cgit.uclibc-ng.org/cgi/cgit/uclibc-ng.git/commit/?id=cee0b058fa0b4501b289a2da365182d60314d746

Signed-off-by: Evgeniy Didin &lt;Evgeniy.Didin@synopsys.com&gt;
CC: Alexey Brodkin &lt;abrodkin@synopsys.com&gt;
CC: John Crispin &lt;john@phrozen.org&gt;
</content>
</entry>
<entry>
<title>musl: move BUILD_DIR_TOOLCHAIN/musl symlink to configure step</title>
<updated>2018-01-25T09:54:14Z</updated>
<author>
<name>Felix Fietkau</name>
</author>
<published>2018-01-24T15:46:22Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/kaloz/commit/?id=074fa8dfe42c525f4ac21e9f11e912d49ae1c5eb'/>
<id>urn:sha1:074fa8dfe42c525f4ac21e9f11e912d49ae1c5eb</id>
<content type='text'>
Avoids Build/Prepare quilt related hacks

Signed-off-by: Felix Fietkau &lt;nbd@nbd.name&gt;
</content>
</entry>
<entry>
<title>musl: allow autorebuild</title>
<updated>2018-01-25T09:54:14Z</updated>
<author>
<name>Felix Fietkau</name>
</author>
<published>2018-01-24T15:43:28Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/kaloz/commit/?id=13a5cb9d2b185a21b514af989a4fa607329a3df0'/>
<id>urn:sha1:13a5cb9d2b185a21b514af989a4fa607329a3df0</id>
<content type='text'>
Autorebuild is disabled for the toolchain to avoid build-order issues.
However, rebuilding musl is safe, so exclude it from that restriction.
Avoids the need for manual cleaning on kernel header &lt;-&gt; libc API
changes like the ones introduced recently

Signed-off-by: Felix Fietkau &lt;nbd@nbd.name&gt;
</content>
</entry>
</feed>
