bug-make
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-make] Re: Building GNU packages


From: Jeffrey L. Wasserman
Subject: [Bug-make] Re: Building GNU packages
Date: Sun, 17 Sep 2000 19:04:46 -0400 (EDT)

Hello, and thanks alot for your reply.

On 17 Sep 2000 address@hidden wrote:
> If find yourself running out of space, try 'make bootstrap-lean'
>   instead of 'make bootstrap' .

okay, I'll try this next time I try to compile gcc.  Luckily we've got a
bunch of room in /tmp, though.

> I thought you said you were on a Solaris 2.7 system. This gcc 2.7.2 is
>   configured for solaris 2.5.1 . My (admittedly limitied)
>   experience with solaris suggests that this is likely to cause
>   problems.

Here's what the ol' uname gives me:
bash-2.03$ uname -a
SunOS iron 5.7 Generic_106541-10 sun4u sparc SUNW,Ultra-5_10

I've been assuming that SunOS 5.7 is Solaris 2.7, maybe this is 
a wildly wrong assumption?  Some precompiled binaries I've downloaded
have worked, though.  Although, now that I think about it, one of them
didn't, it said it couldn't find some .so files or something like that.

> I suggest you try to find a pre-compiled binary of gcc, and try
>   that. www.sunfreeware.com is one place to look for solaris binaries of
>   gcc, but I am afraid they will not have one that can be installed by
>   someone other than root.

I am not root.  But I was hoping to somehow install some of the binaries
within a bin directory in my home path.  Should this be feasible?  I
assume there will be many problems with the include files and compiled
libraries and all that, as I'll have to re-direct all other compilations
to use these paths instead of the system defaults.  Maybe I can convince
the sysadmins to upgrade gcc, and (hopefully) add some of the GNU tools
too. 
 
> Since this may be a problem with gnu make, I am cc'ing this to the
>   gnu-make list.

Because this happened with both gcc and make, and other packages before
these, I'm assuming that perhaps something is wrong with the libraries,
which gave me those parse errors. The paths to some of the include files
have the version 2.7.2 in it, so I was wondering if there were known
problems with the libraries of gcc version 2.7.2.

I'll see if I can do anything with the pre-compiled Solaris binaries you
mentioned.

Thanks again for your response!

        Sincerely,
        Jeff Wasserman 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]