> Maybe because it's looking for "stdio.h" and the file you located is > called "std_cstdio.h"? >
That was one of my original thoughts but it would seem like it's pretty lame to have to go and create symbolic links for every standard library header just to compile anything. I think likely there is some bonehead step i'm missing. Just not sure what it is. -Lkb > On Wed, 5 Jun 2002, Lorin wrote: > > > For some reason i can't seem to get anything to compile on openbsd 3.0. > > > > The gcc packages i've installed are: > > gcc-3.0.1-c++.tgz > > gcc-3.0.1-core.tgz > > > > when i try to compile anything i get a whole mess of errors, about std > > libraries like stdio.h string.h signal.h > > > > according to gcc.gnu.org those should be part of the regular gcc package > > now, and in fact a locate does show: > > > > bash-2.05# locate stdio.h > > /usr/local/include/g++-v3/bits/std_cstdio.h > > > > So why won't it compile? Anybody? Bueller? > > > > -Lkb > > > > > > > > _______________________________________________ > > Bits mailing list > > [EMAIL PROTECTED] > > http://www.sugoi.org/mailman/listinfo/bits > > > > _______________________________________________ Bits mailing list [EMAIL PROTECTED] http://www.sugoi.org/mailman/listinfo/bits
