help-gnu-radius
[Top][All Lists]
Advanced

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

Re: [Help-gnu-radius] problems installing GNU Radius


From: Paul Doxey
Subject: Re: [Help-gnu-radius] problems installing GNU Radius
Date: Fri, 20 Jul 2001 13:22:46 -0500

Hi Sergey,

Since I'm not a unix whiz, I don't know how to add to the $PATH, so I
set up a link to gcc and got the following result:

# ./configure
loading cache ./config.cache
checking host system type... sparc-sun-solaris2.6
checking target system type... sparc-sun-solaris2.6
checking build system type... sparc-sun-solaris2.6
checking for a BSD compatible install... ./install-sh -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... missing
checking for working autoconf... missing
checking for working automake... missing
checking for working autoheader... missing
checking for working makeinfo... missing
checking whether to enable maintainer-specific portions of Makefiles...
no
checking for gcc... gcc
checking whether the C compiler (gcc  ) works... yes
checking whether the C compiler (gcc  ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for ranlib... :
checking for bison... no
checking for byacc... no
checking how to run the C preprocessor... gcc -E
checking for flex... no
checking for lex... no
./configure: flex: not found
checking for flex... lex
checking for yywrap in -ll... yes
checking lex output file root... ./configure: lex: not found
configure: error: cannot find output from lex; giving up

My $PATH looks like this:

# echo $PATH
/usr/bin:/usr/ucb:/etc:.
#

Paul

Sergey Poznyakoff wrote:

> > checking for gcc... no
> > checking for cc... no
> > configure: error: no acceptable cc found in $PATH
> >
> > Does this look right?
> No, it does not... But it means that gcc is not in your PATH. You
> should simply update your PATH variable so that gcc could be found.
> By the way, your previous posting had:
>
> > > > checking for gcc... gcc
>
> That is, gcc was found earlier...
>
> At a pinch you can just override the CC variable when running
> configure like this:
>
>           CC="<full_path_to_gcc>/gcc" ./configure
>
> but this is not recommended, since gcc itself relies on $PATH being
> set up correctly.
>
> Regards,
> Sergey

Attachment: paul.doxey.vcf
Description: Card for Paul Doxey


reply via email to

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