Re: [gccsdk] Flex and Bison broken?

On Sun, 08 Feb 2015 12:11:22 -0000, alan buckley <alan_baa@hotmail.com>
wrote:

> WPB wrote on Date: Sat, 7 Feb 2015 20:27:31:
[snip]
>> Both fail. Flex with the following error:
>>
>> File '$.usr.local.bin.m4' not found
>>
>> I know there is a port of 'm4' at riscos.info, but it's certainly not
>> going to be found at that location on my hard drive!
[snip]

It looks like 'flex' on RISC OS needs to be told where to look for the M4
binary. The current M4 port on riscos.info sets an 'm4' alias, so 'flex'
should just be able to run the command. Is there a reason my some dev
tools are packaged up as part of !GCC (like flex and bison) and some (like
M4) are separate?

[snip]
>> So it looks like there's a hard-coded reference in there to a file:
>> /home/alanb/gccsdk/env/share/bison/m4sugar/m4sugar.m4 - again, it
>> appears
>> 'bison' is broken. Would people agree?
>>
>> If anyone has any input on this, it would be greatly appreciated.
>>
>
> The path looks like it's from my machine when I last ran the autobuilder
> on bison. If anyone knows what the paths should be for RISC OS (or
> better still had a patch) I can look at fixing and rebuilding both flex
> and bison.
>
> Regards,
> Alan

I had suspected 'alanb' was you! ;) I can't shed any light on this, other
than to observe that the package that contains bison contains /only/ the
bison binary. The file m4sugar.m4 isn't included, nor is it anywhere in my
!GCC distribution. So it appears to be missing completely. As to where it
/should/ go, I really couldn't say.

I also thought that the output of flex and bison both required linking
against flex and bison library functions, usually distributed with them.
Is that not the case with the RISC OS ports?

I'd look into this more myself, but I have no way of running the
autobuilder. I once tried to install it on my NAS box, but I couldn't find
an autoconf package for my NAS, so I was flummoxed.

Thanks,

WPB

_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK