Re: 2.95.2 missing files?

[Derek Greer <dgreer at fedex dot com>]

Alexandre Oliva wrote:

> On Mar 17, 2000, Derek Greer <dgreer@fedex.com> wrote:
>
> > re-read my original email you will see that I said the program WOULD
> > NOT compile when I attempted to compile it on the same operating
> > system I installed it on (Solaris 2.5.1).
>
> Do you mean you build GCC from *sources* on Solaris 2.5.1 and it won't
> compile programs that include certain headers?

Yes.


>  Didn't you just
> install some pre-compiled binary for 2.6?
>

What happened was that I installed the gcc in my home directory because I
didn't want to inadvertently overwrite anything accidentally.  When I
installed it, I was on 2.5.1.  When I tried to compile my program, it didn't
like some things in sockets.h.  My home directory is also mounted to a system
running 2.6 so I figured I could try it on that system just to see what
happens.  Once I logged into the 2.6. system I was able to compile the
program without errors.

>
> If not, could it be that some patches that modified header files have
> been installed after GCC?
>

That could be.  This system has been around a few years so it is possible
files have been modified.

>
> > "Stand alone" means it doesn't need pre-existing header files.
>
> It is a stand-alone compiler.  The library, that provides the headers,
> is a separate issue.  You don't always need the headers to compile a
> (admittedly ridiculously simple :-) program, but you often need the
> libraries and run-time objects.  So, yes, GCC is not stand-alone, if
> that's what you want to hear (or read :-)
>
> >> > Perhaps the correct answer is that 2.95.2 hasn't been tested for
> >> > Solaris 2.5.1, at least with sockets.
> >>
> >> This answer is wrong.  :-) It will work perfectly well with sockets on
> >> Solaris 2.5.1, as long as you build it on Solaris 2.5.1.  Just try it
> >> :-)
>
> > I have already addressed you misunderstanding earlier, so I won't
> > comment further on that point.
>
> I know GCC 2.95.2 works on Solaris 2.5.1 because I use it myself, and
> I build a lot of programs that use sockets with it.  And I also know
> that a lot of people have trouble just like yours.  The most common
> reason is having installed GCC on one version of Solaris and being
> running it on another.  The second most common reason is when people
> install BIND in a way that replaces some of their socket-related
> headers.  Was that your case?
>
> > so unless you personally tested it for this system you aren't
> > qualified to say my answer is incorrect.
>
> I only did because I am :-)
>
> --
> Alexandre Oliva    Enjoy Guaranį, see http://www.ic.unicamp.br/~oliva/
> Cygnus Solutions, a Red Hat company        aoliva@{redhat, cygnus}.com
> Free Software Developer and Evangelist    CS PhD student at IC-Unicamp
> oliva@{lsd.ic.unicamp.br, gnu.org}   Write to mailing lists, not to me