>>>>> "Helmut" == Helmut Grohne <hel...@subdivi.de> writes:
>> You also talked about adding native:true for bison. But Is that
>> sufficient?
Helmut> Sufficient for what? Adding it makes the non-minimal cross
Helmut> build stop failing.
Well, makes your particular case stop failing.
I guess I was asking whether adding native=true to finding bison is
sufficient to get the spec built if a native bison is present.
>> Then don't I need to use a native flex and a native C compiler?
Helmut> flex comes in two parts one is the flex tool (where there is
Helmut> only one) and the other is libfl-dev containing libfl.so
Helmut> (where you already build-depend on both). A native C
Helmut> compiler is implied in build-essential (and
Helmut> crossbuild-essential-*).
I was more thinking about the Meson side of things rather than the
Debian side of things.
Do I need to duplicate the logic to choose compiler flags and to set up
config.h for the cross side as well as the native side?
There's a lot of logic in the top level meson.build for selecting
compiler and compiler options (and generating config.h).
I suspect in most cases it will probably just work to use the same
options for cross and native, but we've certainly come across cases
where that's not true (for example the ftcbfs patch against pam was such
a case).
I don't know how all that works in Meson.
For example we explicitly find a compiler in the top level meson.build,
although only use that meson object for autoconf-style probing of the system.
We never tell it to use that compiler for building executables.
So there's a lot going on implicitly.
--Sam
