Re: [gccsdk] Flex and Bison broken?

In message <op.xtpe35abizronj@bluey>
WPB <wpb.feed@gmx.com> wrote:

> Guess what? I'm back!
>
> So, now with everyone's help (thank you), I've progressed to the point
> that 'make' is trying to invoke flex and then bison.
>
> Both fail. Flex with the following error:
>
> File '$.usr.local.bin.m4' not found
>
OK, it sounds like the native linux m4 would do the job for the
cross-compiler (or not, I'm unsure)
To try these things out initially, you can make a directory on your hard
drive /usr/local/bin and put the ported binary of m4 in it.

<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?
>
Yes this has been done by the cross-compiler for the cross-compiler to
use. Once again, you can create the m4sugar.m4 file in that location
for the purpose of trying it out.

I did make path adjusted versions and everything got found, but still
run into an error.

To help organise these hard paths into something manageable, I use a
directory /home which I also set to the HOME variable at Boot time.
SetEval HOME Boot$Dir LEFT(LEN Boot$Dir -6)+"/home"
for portability. Otherwise you might get away 'set HOME /home'
This equates to $HOME, some linux ports crash on starting without a clue
to why without it.

You can then adopt $HOME/bin $HOME/share etc.
Often compiling can be done --with-prefix= or the default paths can be
changed in the source, sometimes config.h has paths.

Some things will integrate easily into the !GCC structure, but you are
no further ahead by having a hard path into a !GCC location.
you can try \<GCC\$Dir\>/bin style, but I have had that fail too.

Ron M.





_______________________________________________
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