[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Building TCC with the upcoming Mes 0.26
|
From: |
Janneke Nieuwenhuizen |
|
Subject: |
Re: Building TCC with the upcoming Mes 0.26 |
|
Date: |
Thu, 23 Nov 2023 22:38:55 +0100 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Timothy Sample writes:
> Ekaitz Zarraga <ekaitz@elenq.tech> writes:
>
>> On 11/23/23 08:48, Janneke Nieuwenhuizen wrote:
>>> Timothy Sample writes:
>>>> The first was that I had to revert the ‘bootstrap.sh’ changes from
>>>> commit 0d3c4ddc4bcb57db690ee8ebab106fa6fda75823. Not sure what that’s
>>>> about.
>>> The commit message is prettry clear? It's for tcc riscv64 (it only
>>> knows a simplified assembly). Do you know how this broke your build,
>>> I believe Andrius even built tcc for x86?
>
> It’s line 32 of “build-source-lib.sh”. It tries to copy from:
>
> ${srcdest}lib/$mes_kernel/$mes_cpu-mes-$compiler
>
> Which is “../lib/linux/x86-mes-tcc”, and which doesn’t exist.
Ah, that makes sense!
> I don’t pretend to understand the build system super well, but it would
> fix it to hide it behind:
>
> if test -d ${srcdest}lib/$mes_kernel/$mes_cpu-mes-tcc
>
> Here’s a patch for that. I tested it and was able to do the build with
> it. I did not test that it works for the RISC-V build (I wouldn’t even
> know how!).
Yes, that looks better than the hack that I had; thanks!
> From f2b5378d072fa0e0dc4810be494327f07aa88b3e Mon Sep 17 00:00:00 2001
> From: Timothy Sample <samplet@ngyro.com>
> Date: Thu, 23 Nov 2023 11:57:27 -0600
> Subject: [PATCH] build: Only build tcc-lib if tcc sources exist.
Applied to version-0.25.
Janneke
--
Janneke Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond https://LilyPond.org
Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com