Re: [gccsdk] gcc unixify failure

In message <851abebe54.beeb@ron1954.woosh.co.nz>
Ron <beeb@woosh.co.nz> wrote:

> I've recently downloaded 4.7.4 and it is runnng standard sfix's.
> This issue is probably there in 4.1.2 also.
>
> Take any c file that would compile into a binary (as an example)
> Rename to foo.bar.c (foo/bar in the c directory)
>
> gcc -o foo.bar.y foo.bar.c
>
> gcc will not find foo/bar.c
> copy foo/bar to foobar (in the c directory)
>
> gcc -o foo.bar.y foobar.c
>
> It doesn't make sense to output to a valid sfix directory (y) but it does show that gcc can riscosify the name for writing but it can't unixify it for reading.
>
> Why does this matter?
> flex outputs lex.yy.c by default.
>
> Using my modded version of gcc that doesn't sfix does allow normal useage, but this is about the standard download of gcc
>
> Thanks, Ron M.
>

I have a found that by setting sfixing back on in my native !GCC.!Run that gcc will find lex.yy.c OK.

I think it shows that the change I made in the recipe file
recipe/files/gcc/gcc/config/arm/riscos-gcc.c (small file by Nick Burrett and John Tytgat)
can allow this to work, without upsetting sfixing and would also work for the standard !GCC download.

I have riscos_convert_filename() returning the name without change.

I'm not sure yet how many uses this function has.
I have been using it returning with no conversion without problems in my non sfixing version.
It appears that this function is separate to the sfixing procedure anyway.

It probably needs attending to in a less blunt way than mine.

I have a failure with -I ../foo.bar (foobar is OK) that I haven't traced yet.
I don't know if this is related, it /is/ part of the cmd line, but the cpp would get passed that also?


Note that this file also contains riscos_host_initialisation() which does wimpslot size checking for 4.1.2
This may have to be changed for 4.7.4?

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