Re: Where's ../fixinc/fixtests on m68k-next-nextstep3 ?

[Bruce Korb <bkorb at sco dot COM>]

toon@moene.indiv.nluug.nl wrote:
> [[...]] I notice that fixincludes doesn't work on
> m68k-next-nextstep3.
> 
> Apparently, the build of C and f77 doesn't fail on the not-fixed
> headers when using the good old cpp, but it does when using the
> cpplib'd one.
> 
> I tried to track this down and I sort of have - it's caused
> by the environment variable PWD not being defined at these
> spots in inclhack.sh:
> 
> FIXTESTS=$PWD/fixinc/fixtests
> FIXFIXES=$PWD/fixinc/fixfixes

It ought to be possible to replace "$PWD" with "`pwd`".
Unfortunately, after having changed jobs, I don't have
access to the sources set up yet.  Let alone write
access to the archive :-}.

> However, when trying to find the cause of this, I got completely
> lost in a twisty maze of shell scripts, all claiming to be
> generated automatically.

There are three automatically generated files:

  inclhack.sh
  fixincl.sh
  fixincl.x

any of many shell scripts may get copied into
${objdir}/gcc/fixincludes.  Given your problem,
it would not be any of gcc/fixinc/fixinc.*.
In fact, $FIXTESTS is only referenced in inclhack.sh.

> Does anybody know where PWD is supposed to be set ?

It is possible I was relying on a ksh-ism.
I used to do that.  I have stopped now, tho
this may be a dinkleberry.  But, like
I said, I cannot see the sources at the moment.

> BTW, does anybody know where the executables fixtests and fixfixes
> end up ?  On my system, they're *not* in {objdir}/gcc/fixinc ...

They should be.  I think the compile failed.
Of course, if you get the compile working, then
the 'fixincl' program will compile too, and you
won't need fixtests/fixfixes.

Regards,
	Bruce