BIND9.3.0 installation

Piniella, David A DPiniella at med.miami.edu
Sun Dec 19 21:35:21 UTC 2004


You shouldn't need to compile (or configure) gcc for installation
itself; sunfreeware (or blastwave.com) offer it as a package which you
can install with the solaris pkg-add utility (# pkg-add -d gcc.pkg would
be the command).

You have to make the "cc" variable in the config that you're trying to
compile use "gcc" instead of cc (or point to gcc). You can also try
making /usr/ucb/cc a link to gcc (wherever you have it installed -- if
it's from sunfreeware.com that'll be /usr/local or /opt unless you
specified somewhere else.)

Make sure that whichever way you choose to do it, you add that directory
to your path.


David Piniella
Network Specialist
Medical Information Technology
University of Miami


-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On
Behalf Of Kelly
Sent: Saturday, December 18, 2004 11:44 PM
To: bind-users at isc.org
Subject: Re: BIND9.3.0 installation


This is what I get when I try to configure 'GCC' for installation.

Any help?

# ./configure
loading cache ./config.cache
checking host system type... i386-pc-solaris2.9
checking target system type... i386-pc-solaris2.9
checking build system type... i386-pc-solaris2.9
checking for a BSD compatible install... ./install-sh -c
/usr/ucb/cc:  language optional software package not installed
*** The command 'cc -o conftest -g   conftest.c' failed.
*** You must set the environment variable CC to a working compiler.
#=20

> First step is to make sure that gcc is installed.  It isn't installed
by=20
> default on a Solaris 9 build.  You can get it from=20
> http://sunfreeware.com.  I'd recommend the UUNET or SprintLink mirror=20
> for downloads.  You should probably download and install GCC, libiconv

> and OpenSSL.  That should get you what you need for compilers, etc.
>=20
> For most build that I have done on Solaris, your best bet is to set
your=20
> path like this:
>=20
> PATH=3D/usr/local/bin:/usr/ccs/bin:${PATH}
> export PATH
>=20
> This also *assumes* you're in sh, ksh or bash.
>=20
> That should take care of the compile.
>=20
> Good luck!
>=20
> Don
>=20
>=20
> Kelly wrote:
>=20
> >I have gotten past this part and now the install is telling me the c=20
> >compiler cannot create executables.  It does find the 'cc' but it
does=20
> >not find the 'gcc'.
> >
> >Any thoughts?
> >
> >
> >Kelly



More information about the bind-users mailing list