building

[Eric Christopher]

On Thu, 2003-06-19 at 16:00, Peter T Greening wrote:
> about #1, I don't understand exactly what you mean.
> I did this:
> cd /usr/local/src/gcc
> tar -xvzf ~/tarballs/gcc-3.3.tgz
> this created /usr/local/src/gcc/gcc-3.3.  I cd to this, and run configure. 
> cd gcc-3.3
> ./configure --prefix=/usr/local/pkg/gcc/gcc-3.3
> (note after build, a utility called pkglink will make links from 
> /usr/local/pkg/gcc/gcc-3.3/bin to /usr/local/bin and the same for lib, var, 
> etc, et. cetria.
> 
>  How should I set up a "build" directory?

:pwd
/home/foo
:mkdir build-gcc
:cd build-gcc
:/usr/local/src/gcc/gcc-3.3/configure \
--prefix=/usr/local/pkg/gcc/gcc-3.3
:make bootstrap
:make install
:cd ..
:rm -rf build-gcc

-eric

> On Wednesday 18 June 2003 05:16 pm, Eric Christopher wrote:
> > On Wed, 2003-06-18 at 16:09, Peter T Greening wrote:
> > > Hi, I am trying to build gcc 3.3 on a linux redhat NFS environment.  The
> > > machine I am trying to build on is a redhat 7.3 running on an athlon(mp),
> > > and almost all of the NFS mounted software was built on 7.3 machines. The
> > > run configure as folllows:"./configure
> > > --prefix=/usr/local/pkg/gcc/gcc-3.3". While building gnu c compiler, it
> > > returns the following error:
> >
> > 1) Don't configure in the source directory. Make a build directory and
> > use that.
> > 2) When using nfs, and in general, it's a good idea to use full paths.
> > e.g. /path/to/configure ....
> >
> > -eric
-- 
Eric Christopher <echristo@redhat.com>