Am 27.03.2024 um 19:14 schrieb Christophe Lyon:
On Tue, 26 Mar 2024 at 16:42, Jens Remus <jre...@linux.ibm.com> wrote:
Am 15.03.2024 um 09:50 schrieb Christophe Lyon:
On Thu, 14 Mar 2024 at 19:10, Simon Marchi <sim...@simark.ca> wrote:
On 2024-03-13 04:02, Christophe Lyon via Gdb wrote:
...
There's just the issue of files that are generated using tools that are
compiled. When experimenting with maintainer mode the other day, I
stumbled on the opcodes/i386-gen, for instance. I don't have a good
solution to that, except to rewrite these tools in a scripting language
like Python.
So for opcodes, it currently means rewriting such programs for i386,
aarch64, ia64 and luckily msp430/rl78/rx share the same opc2c
generator.
Not sure how to find volunteers?
Why are those generated source files checked into the repository and not
generated at build-time? Would there be a reason for s390 do so as well
(opcodes/s390-opc.tab is generated at build-time from
opcodes/s390-opc.txt using s390-mkopc built from opcodes/s390-mkopc.c)?
I remember someone mentioned a requirement of being able to rebuild
with the sources on a read-only filesystem.
I don't know if there's a requirement that such generated files should
be part of the source tree though. Is opcodes/s390-opc.tab in builddir
or in srcdir?
I think there are other motivations but I can't remember them at the moment :-)
Thank you for the insights, Christophe! opcodes/s390-opc.tab is
generated in builddir.
Regards,
Jens
--
Jens Remus
Linux on Z Development (D3303) and z/VSE Support
+49-7031-16-1128 Office
jre...@de.ibm.com
IBM
IBM Deutschland Research & Development GmbH; Vorsitzender des
Aufsichtsrats: Wolfgang Wendt; Geschäftsführung: David Faller; Sitz der
Gesellschaft: Böblingen; Registergericht: Amtsgericht Stuttgart, HRB 243294
IBM Data Privacy Statement: https://www.ibm.com/privacy/
