Hans,
Yes, the project is very uncommon, and I agree the lib should be inside the
project directory structure, but I had this issue a long long time ago when
working on an embedded system that shared some libraries between host and
target machine.
I don't know if it's even a bug or just an unsuppor
I don't know how to change the code, but it seems to be caused by
difference between Solaris lex & flex (flex 2.6.4). make check
passes if flex has priority over lex.
Thanks for the info. There are other deficiencies with support for
native Solaris tools -- https://bugs.gnu.org/42393.
The example filename "zardoc.c" in the Vala section should be "zardoz.c";
Indeed. Changed, closing ... --thanks, karl.
Am 24.11.2020 um 21:09 schrieb Fabrizio Bertocci:
Karl,
It took me a while to remember what this issue was about... but I
managed to get to my old reproducer.
Ok, let me do one step back. The root problem is how do I ensure that
paths passed through ./configure command line are valid when bui
Karl,
It took me a while to remember what this issue was about... but I managed
to get to my old reproducer.
Ok, let me do one step back. The root problem is how do I ensure that paths
passed through ./configure command line are valid when building source code
under 'src' (for example).
Look at t
The example filename "zardoc.c" in the Vala section should be "zardoz.c";
it doesn't really matter, but it is almost certainly a typo.
--
https://rrt.sc3d.org
