Re: Building m4 on BSDI 4.0.1

[Chris McGuire]

At 02:38 AM 12/13/2006, you wrote:
>Chris McGuire <address@hidden> writes:
>
>> I suspect that it is just a matter of configure not applying changes
>> it would make to BSD/OS 4.1 to my BSDI 4.0.1 box.
>
>Yes, most likely so.  But to turn this vague idea into code that
>actually works for you, we need a concrete example of a simple
>C program that does not work on your host.  Something like this:
>
>  #include <wchar.h>
>  #include <sys/types.h>
>  wchar_t foo;
>
>or whatever the pattern is that makes your C compiler reject the program.

To be very honest, this is beyond my knowledge...unfortunately. :( I would need 
something that I could simply cut and paste and you'd tell me what command(s) 
to run and test it. I'm sure you don't have time for that. But if you do, I'm 
more than willing to try.

Wasn't the output of the build process that I sent along originally (showing 
where it failed) an example?


>On second thought, perhaps you should just remove /usr/include/wchar.h
>on your host.  That solves your problem, and the file can't be doing
>you any good anyway.

That is exactly what I did and it seems to work well. I only wonder if there is 
a replacement for wchar.h that would allow it to work properly or if autoconf 
or configure could be tweaked in future versions to apply what appears to be a 
known issue and fix for BSD/OS 4.1 to BSDI 4.0.1 as well?

Thanks,
Chris