<feed xmlns='http://www.w3.org/2005/Atom'>
<title>staging/chunkeey/toolchain/Config.in, branch v19.07.2</title>
<subtitle>Staging tree of Christian Lamparter</subtitle>
<id>https://git.openwrt.org/openwrt/staging/chunkeey/atom?h=v19.07.2</id>
<link rel='self' href='https://git.openwrt.org/openwrt/staging/chunkeey/atom?h=v19.07.2'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/'/>
<updated>2019-06-10T09:31:52Z</updated>
<entry>
<title>toolchain: replace LEDE in help text</title>
<updated>2019-06-10T09:31:52Z</updated>
<author>
<name>Karl Pálsson</name>
</author>
<published>2019-06-05T17:16:52Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/commit/?id=3b36aae9d5ec06d2e849212a70e3c8350a3b60b5'/>
<id>urn:sha1:3b36aae9d5ec06d2e849212a70e3c8350a3b60b5</id>
<content type='text'>
Use generic wording.

Signed-off-by: Karl Pálsson &lt;karlp@etactica.com&gt;
Signed-off-by: Christian Lamparter &lt;chunkeey@gmail.com&gt; [fixed a -&gt; á]
</content>
</entry>
<entry>
<title>musl: improve crypt() size hack</title>
<updated>2019-01-22T11:08:03Z</updated>
<author>
<name>Jo-Philipp Wich</name>
</author>
<published>2019-01-22T08:50:09Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/commit/?id=ceb625439a84c7ea4ab1e39f126b6baffc48d1cd'/>
<id>urn:sha1:ceb625439a84c7ea4ab1e39f126b6baffc48d1cd</id>
<content type='text'>
Instead of silently downgrading any non-MD5 crypt() request to DES,
cleanly fail with return NULL and errno = ENOSYS. This allows callers
to notice the missing support instead of the unwanted silent fallback
to DES.

Also add a menuconfig toolchain option to optionally disable the crypt
size hack completely. This can be probably made dependant on SMALL_FLASH
or a similar feature indicator in a future commit.

Ref: https://github.com/openwrt/openwrt/pull/1331
Signed-off-by: Jo-Philipp Wich &lt;jo@mein.io&gt;
</content>
</entry>
<entry>
<title>toolchain: Replace YASM with NASM</title>
<updated>2018-07-05T14:17:06Z</updated>
<author>
<name>Ted Hess</name>
</author>
<published>2018-06-28T23:28:02Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/commit/?id=0f543883cd0505a98fdc680ce2f08cbfca6d52a7'/>
<id>urn:sha1:0f543883cd0505a98fdc680ce2f08cbfca6d52a7</id>
<content type='text'>
Packages libx264 and ffmpeg are built with ASM options on x86 platforms.
The current libx264 version no longer builds with YASM and requires NASM.
ffmpeg 3.x can be built with either YASM or NASM however, furture 4.x versions
will require NASM.

Signed-off-by: Ted Hess &lt;thess@kitschensync.net&gt;
Acked-by: Rosen Penev &lt;rosenp@gmail.com&gt;
</content>
</entry>
<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/chunkeey/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>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/chunkeey/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: use glibc for powerpc64 builds</title>
<updated>2017-10-24T11:24:04Z</updated>
<author>
<name>Florian Larysch</name>
</author>
<published>2016-11-03T13:30:40Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/commit/?id=0de93311e1575ab6f8e9e90b5023b6fb2cedcf1f'/>
<id>urn:sha1:0de93311e1575ab6f8e9e90b5023b6fb2cedcf1f</id>
<content type='text'>
Neither uClibc nor musl currently have working support for powerpc64 in
big endian mode. Thus, default to using glibc for this architecture.

Signed-off-by: Florian Larysch &lt;fl@n621.de&gt;
</content>
</entry>
<entry>
<title>toolchain: remove powerpc64 feature</title>
<updated>2017-10-24T11:24:04Z</updated>
<author>
<name>Florian Larysch</name>
</author>
<published>2016-11-03T13:30:53Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/commit/?id=9e91d3271848fb9093b1a7f92ac9542ced8da88d'/>
<id>urn:sha1:9e91d3271848fb9093b1a7f92ac9542ced8da88d</id>
<content type='text'>
The powerpc64 feature flag was introduced with the PS3 support, which
has been removed for quite a while and is now unused. Remove it and the
special biarch handling it triggered during the toolchain build.

Signed-off-by: Florian Larysch &lt;fl@n621.de&gt;
</content>
</entry>
<entry>
<title>toolchain/insight: Remove from tree</title>
<updated>2017-05-29T07:57:18Z</updated>
<author>
<name>Daniel Engberg</name>
</author>
<published>2017-05-29T07:41:15Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/commit/?id=2cf4e3c420ef452e6a687615ab865eae200ed89a'/>
<id>urn:sha1:2cf4e3c420ef452e6a687615ab865eae200ed89a</id>
<content type='text'>
Insight hasn't been touched since 2009 and I can't find any references at
least 6 years back of being used. Ubuntu and Debian removed insight years ago
from their repos so I think we can safely remove this too.

Signed-off-by: Daniel Engberg &lt;daniel.engberg.lists@pyret.net&gt;
</content>
</entry>
<entry>
<title>build: remove libc version config code</title>
<updated>2017-02-11T14:37:55Z</updated>
<author>
<name>Felix Fietkau</name>
</author>
<published>2017-02-07T09:38:47Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/commit/?id=38fcd2a865c2ec463b6909f613847d41353c1e1e'/>
<id>urn:sha1:38fcd2a865c2ec463b6909f613847d41353c1e1e</id>
<content type='text'>
We only support one version per libc type

Signed-off-by: Felix Fietkau &lt;nbd@nbd.name&gt;
</content>
</entry>
<entry>
<title>toolchain: Rework external toolchain libc selection</title>
<updated>2016-09-28T06:39:01Z</updated>
<author>
<name>Florian Fainelli</name>
</author>
<published>2016-09-19T19:59:32Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/commit/?id=c8e68150bfe2578ce7b0681465d08c5f01823db4'/>
<id>urn:sha1:c8e68150bfe2578ce7b0681465d08c5f01823db4</id>
<content type='text'>
Make it a choice menu which offers the 3 C libraries we know about: glibc,
uClibc and musl. While at it, make it possible for the external toolchain libc
to select USE_GLIBC, USE_UCLIBC or USE_MUSL which is used by several packages
to conditionally include specific CFLAGS (e.g: iproute2).

Because USE_GLIBC et al. can now be selected by external toolchains, we need to
restrict the per-libc menus to check on !EXTERNAL_TOOLCHAIN.

While at it, make musl the default C library for external toolchain to match
the internal toolchain.

Signed-off-by: Florian Fainelli &lt;f.fainelli@gmail.com&gt;
Signed-off-by: Felix Fietkau &lt;nbd@nbd.name&gt;
</content>
</entry>
</feed>
