Hi Waldemar,
We will soon publish a Buildroot port on GitHub, which will allow you to
build a toolchain.
With a local.mk and UCLIBC_OVERRIDE_SRCDIR you can provide Buildroot
with a local git repo containing the uClibc-ng source against which you
want to build the toolchain.
It will allow you to test that a toolchain can be produced with upstream
master of uClibc-ng + the patch I provide and that it can compile kernel
+ userspace.
There is no way currently for you to actually run something (no public
simulator or board), we are working on some solution but it's not
available so far.
Best regards,
Yann
On 6/19/20 8:58 AM, Waldemar Brodkorb wrote:
Hi Yann,
I cannot verify toolchain building, because the binutils/gcc you are
publishing has no support for Linux toolchain building. When are you
planning to publish the complete stuff?
best regards
Waldemar
Yann Sionneau wrote,
> Hi Waldemar,
>
> Sorry about the patch, wrong rebase!
>
> I've just sent a new version which should get rid of all trailing spaces and
> newline before EOF issues.
>
> It should also get rid of the merge conflict in include/elf.h
>
> Cheers!
>
> Yann
>
> On 07/06/2020 00:46, Waldemar Brodkorb wrote:
>> Hi Yann,
>>
>> thx for submitting the patch.
>>
>> It does not apply on git master:
>> wbx@helium:~/openadk/uClibc-ng-git$ git am ../../kvx/
>> Applying: kvx: add support for kvx arch to uClibc-ng
>> .git/rebase-apply/patch:463: space before tab in indent.
>> *reloc_addr = symbol_addr + rpnt->r_addend;
>> .git/rebase-apply/patch:464: space before tab in indent.
>> break;
>> .git/rebase-apply/patch:591: trailing whitespace.
>> * Copyright (C) 2018 Kalray Inc.
>> .git/rebase-apply/patch:596: trailing whitespace.
>> #error NOT IMPLEMENTED: THIS IS A SKELETON
>> .git/rebase-apply/patch:749: trailing whitespace.
>> if (res==0)
>> error: patch failed: include/elf.h:272
>> error: include/elf.h: patch does not apply
>> Patch failed at 0001 kvx: add support for kvx arch to uClibc-ng
>> The copy of the patch that failed is found in: .git/rebase-apply/patch
>> When you have resolved this problem, run "git am --continue".
>> If you prefer to skip this patch, run "git am --skip" instead.
>> To restore the original branch and stop patching, run "git am
--abort".
>>
>> Any idea?
>>
>> best regards
>> Waldemar
> _______________________________________________
> devel mailing list
> devel(a)uclibc-ng.org
>
https://mailman.uclibc-ng.org/cgi-bin/mailman/listinfo/devel