Hi Linus,
You have to do “make dirclean”.
Thank you,
Boris Krasnovskiy
> On May 2, 2019, at 11:28 AM, Linus Walleij wrote:
>
>> On Thu, May 2, 2019 at 12:30 AM Boris Krasnovskiy wrote:
>>
>> Crash during init that you can see, is pretty far along in the boot process,
>> so toolchain likely
On Thu, May 2, 2019 at 12:30 AM Boris Krasnovskiy wrote:
> Crash during init that you can see, is pretty far along in the boot process,
> so toolchain likely correct.
I found the problem, actually the toolchain was incorrect, but that was
a sideffect of the build system. After applying
this pat
Hi Linus,
I did check generated toolchain defaults. They seem correct.
As such I believe issue is with one of the packages.
Extra information like crash log could help to determine which one.
Here are the generated toolchain defaults for gimeni:
The following options are target specific:
-mabi
Hi Linus,
I do not see anything wrong for your target. And I do not have any Gemini
devices.
Crash during init that you can see, is pretty far along in the boot process, so
toolchain likely correct.
Maybe an issue with some packages…
You can run “ gcc -Q --help=target” on the compiled
Hi Boris & friends,
commit 8dcc1087602e2dd606e4f6e81a06aee62cfd4f4c
"toolchain: ARM: Fix toolchain compilation for gcc 8.x"
regresses the Gemini (FA526-based).
I cannot quite see how. I noticed init crashed with the latest
OpenWrt codebase and bisected it down to this commit.
Before the commit i
