In installing the latest version of R, I get stuck at the make command:
$ ./configure checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu loading site script './config.site' loading build-specific script './config.site' checking for pwd... /usr/bin/pwd checking whether builddir is srcdir... yes checking for working aclocal... missing checking for working autoconf... missing checking for working automake... missing checking for working autoheader... missing checking for gawk... gawk checking whether ln -s works... yes checking for bison... no checking for byacc... no checking for ar... ar checking for a BSD-compatible install... /usr/bin/install -c checking for sed... /usr/bin/sed checking for which... /usr/bin/which checking for less... /usr/bin/less checking for gtar... /usr/bin/gtar checking for tex... /usr/bin/tex checking for pdftex... /usr/bin/pdftex checking for pdflatex... /usr/bin/pdflatex checking for makeindex... /usr/bin/makeindex checking for makeinfo... /usr/bin/makeinfo checking whether makeinfo version is at least 4.7... yes checking for ginstall-info... no checking for install-info... /usr/sbin/install-info checking for texi2dvi... /usr/bin/texi2dvi checking for kpsewhich... /usr/bin/kpsewhich configure: WARNING: inconsolata.sty not found: PDF vignettes and package manuals will not be rendered optimally checking for unzip... /usr/bin/unzip checking for zip... /usr/bin/zip checking for gzip... /usr/bin/gzip checking for bzip2... /usr/bin/bzip2 checking for firefox... /usr/bin/firefox using default browser ... /usr/bin/firefox checking for acroread... no checking for acroread4... no checking for xdg-open... /usr/bin/xdg-open checking for notangle... false checking for pkg-config... /usr/bin/pkg-config checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking whether gcc needs -traditional... no checking how to run the C preprocessor... gcc -E checking for gfortran... gfortran checking whether we are using the GNU Fortran 77 compiler... yes checking whether gfortran accepts -g... yes checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking how to run the C++ preprocessor... g++ -E checking whether __attribute__((visibility())) is supported... yes checking whether gcc accepts -fvisibility... yes checking whether gfortran accepts -fvisibility... yes checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking for gcc... gcc checking whether we are using the GNU Objective C compiler... no checking whether gcc accepts -g... no checking for Objective C++ compiler... trying some possibilities checking whether g++ can compile ObjC++... no checking whether can compile ObjC++... no no working compiler found checking for a sed that does not truncate output... (cached) /usr/bin/sed checking for fgrep... /usr/bin/grep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking the maximum length of command line arguments... 1572864 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking for /usr/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from gcc object... ok checking for dlfcn.h... yes checking whether we are using the GNU C++ compiler... (cached) yes checking whether g++ accepts -g... (cached) yes checking how to run the C++ preprocessor... g++ -E checking whether we are using the GNU Fortran 77 compiler... (cached) yes checking whether gfortran accepts -g... (cached) yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... no checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no checking for ld used by g++... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC -DPIC checking if g++ PIC flag -fPIC -DPIC works... yes checking if g++ static flag -static works... no checking if g++ supports -c -o file.o... yes checking if g++ supports -c -o file.o... (cached) yes checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no checking for gfortran option to produce PIC... -fPIC checking if gfortran PIC flag -fPIC works... yes checking if gfortran static flag -static works... no checking if gfortran supports -c -o file.o... yes checking if gfortran supports -c -o file.o... (cached) yes checking whether the gfortran linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking for cos in -lm... yes checking for sin in -lm... yes checking for dlopen in -ldl... yes checking readline/history.h usability... no checking readline/history.h presence... no checking for readline/history.h... no checking readline/readline.h usability... no checking readline/readline.h presence... no checking for readline/readline.h... no checking for rl_callback_read_char in -lreadline... no checking for main in -lncurses... no checking for main in -ltermcap... no checking for main in -ltermlib... no checking for rl_callback_read_char in -lreadline... no checking for history_truncate_file... no configure: error: --with-readline=yes (default) and headers/libs are not available [richard@localhost R-3.0.0]$ make make: *** No targets specified and no makefile found. Stop.
What does it want?
On Tue, Apr 30, 2013 at 10:57 AM, Richard Vickery richard.vickeryrv@gmail.com wrote:
In installing the latest version of R, I get stuck at the make command:
$ ./configure
<snipt>
configure: error: --with-readline=yes (default) and headers/libs are not available
This indicates that you need the "readline-devel" package to proceed.
[richard@localhost R-3.0.0]$ make make: *** No targets specified and no makefile found. Stop.
What does it want?
-T.C.
On Tue, Apr 30, 2013 at 12:04 PM, T.C. Hollingsworth < tchollingsworth@gmail.com> wrote:
On Tue, Apr 30, 2013 at 10:57 AM, Richard Vickery richard.vickeryrv@gmail.com wrote:
In installing the latest version of R, I get stuck at the make command:
$ ./configure
<snipt> > configure: error: --with-readline=yes (default) and headers/libs are not > available
This indicates that you need the "readline-devel" package to proceed.
[richard@localhost R-3.0.0]$ make make: *** No targets specified and no makefile found. Stop.
What does it want?
-T.C.
Thanks. I have yum installed readline-devel.
I have encountered another one:
checking for IceConnectionNumber in -lICE... no checking X11/Intrinsic.h usability... no checking X11/Intrinsic.h presence... no checking for X11/Intrinsic.h... no configure: error: --with-x=yes (default) and X11 headers/libs are not available
Would my next "yum install" be IceConectionNumber?
On 4/30/2013 3:31 PM, Richard Vickery wrote:
checking for IceConnectionNumber in -lICE... no checking X11/Intrinsic.h usability... no checking X11/Intrinsic.h presence... no checking for X11/Intrinsic.h... no configure: error: --with-x=yes (default) and X11 headers/libs are not available
Would my next "yum install" be IceConectionNumber?
It appears that the default configuration this package is using expects X Windows to be present (the "--with-x=yes (default)" gave it away) and you evidently don't have any of those required packages installed.
This might be a dumb question but why don't you just try this?: yum install R
Yum is designed to pick up dependencies and figure everything out for you automagically. ;)
On 4/30/2013 15:04, T.C. Hollingsworth wrote:
On Tue, Apr 30, 2013 at 10:57 AM, Richard Vickery richard.vickeryrv@gmail.com wrote:
In installing the latest version of R, I get stuck at the make command:
$ ./configure
<snipt> > configure: error: --with-readline=yes (default) and headers/libs are not > available
This indicates that you need the "readline-devel" package to proceed.
[richard@localhost R-3.0.0]$ make make: *** No targets specified and no makefile found. Stop.
What does it want?
-T.C.
libX11 and libXt.
On Tue, Apr 30, 2013 at 12:49 PM, Tom Rivers tom@impact-crater.com wrote:
This might be a dumb question but why don't you just try this?: yum install R
I think he wanted the new version of R. But now that I look, it's in updates-testing. So just: yum --enablerepo=updates-testing install R
if you want R 3.
-T.C.
On Tue, Apr 30, 2013 at 7:06 PM, T.C. Hollingsworth < tchollingsworth@gmail.com> wrote:
On Tue, Apr 30, 2013 at 12:49 PM, Tom Rivers tom@impact-crater.com wrote:
This might be a dumb question but why don't you just try this?: yum
install
R
I think he wanted the new version of R. But now that I look, it's in updates-testing. So just: yum --enablerepo=updates-testing install R
if you want R 3.
-T.C.
Hi T.C.,
That operation installed R-3.0.0-2, which is AWESOME! #yum install R installs 2.x; I downloaded an R-3.0.0 tar ball from the sight and was installing that before installing the updates-testing" version, and this is where the questions were coming from, but now that I've got 3.0.0-2, I'm not complaining; it's only that the tar ball is not an updates testing version.
Best regards, Richard,
On Tue, Apr 30, 2013 at 8:21 PM, Richard Vickery richard.vickeryrv@gmail.com wrote:
Hi T.C.,
That operation installed R-3.0.0-2, which is AWESOME! #yum install R installs 2.x; I downloaded an R-3.0.0 tar ball from the sight and was installing that before installing the updates-testing" version, and this is where the questions were coming from, but now that I've got 3.0.0-2, I'm not complaining; it's only that the tar ball is not an updates testing version.
Excellent!
If you find that package works fine for you, you can log into the Fedora Update System and give it good karma, which will get it pushed to the stable updates repository faster: https://admin.fedoraproject.org/updates/FEDORA-2013-6425/
-T.C.
On Tue, Apr 30, 2013 at 8:35 PM, T.C. Hollingsworth < tchollingsworth@gmail.com> wrote:
On Tue, Apr 30, 2013 at 8:21 PM, Richard Vickery richard.vickeryrv@gmail.com wrote:
Hi T.C.,
That operation installed R-3.0.0-2, which is AWESOME! #yum install R installs 2.x; I downloaded an R-3.0.0 tar ball from the sight and was installing that before installing the updates-testing" version, and this
is
where the questions were coming from, but now that I've got 3.0.0-2, I'm
not
complaining; it's only that the tar ball is not an updates testing
version.
Excellent!
If you find that package works fine for you, you can log into the Fedora Update System and give it good karma, which will get it pushed to the stable updates repository faster: https://admin.fedoraproject.org/updates/FEDORA-2013-6425/
-T.C.
I forgot my user name; the email I used at the time I set the account up is richard.vickery@telus.net
On 30.04.2013 21:49, Tom Rivers wrote:
On 4/30/2013 3:31 PM, Richard Vickery wrote:
checking for IceConnectionNumber in -lICE... no checking X11/Intrinsic.h usability... no checking X11/Intrinsic.h presence... no checking for X11/Intrinsic.h... no configure: error: --with-x=yes (default) and X11 headers/libs are not available
Would my next "yum install" be IceConectionNumber?
It appears that the default configuration this package is using expects X Windows to be present (the "--with-x=yes (default)" gave it away) and you evidently don't have any of those required packages installed.
This might be a dumb question but why don't you just try this?: yum install R
Yum is designed to pick up dependencies and figure everything out for you automagically. ;)
curl -s http://pkgs.fedoraproject.org/cgit/R.git/plain/R.spec | grep ^BuildRequires
poma
On Tue, Apr 30, 2013 at 9:12 PM, Richard Vickery richard.vickeryrv@gmail.com wrote:
I forgot my user name; the email I used at the time I set the account up is richard.vickery@telus.net
I queryed Fedora's awesome IRC bot on your behalf, and can't seem to find a FAS account under either your old or current e-mail or by searching your last name: 21:35 <tchol> .fas richard.vickery@telus.net 21:35 <zodbot> 'richard.vickery@telus.net' Not Found! 21:36 <tchol> .fas richard.vickeryrv@gmail.com 21:36 <zodbot> 'richard.vickeryrv@gmail.com' Not Found! 21:36 <tchol> .fas vickery 21:36 <zodbot> 'vickery' Not Found! # just to make sure name searches are working 21:36 <tchol> .fas t.c. 21:36 <zodbot> patches 'T.C. Hollingsworth' tchollingsworth@gmail.com
Perhaps your account has been deactivated due to inactivity/because that e-mail is no longer valid? Since your e-mail changed anyway, you might as well register for a new one.
-T.C.
On Tue, Apr 30, 2013 at 9:43 PM, T.C. Hollingsworth < tchollingsworth@gmail.com> wrote:
On Tue, Apr 30, 2013 at 9:12 PM, Richard Vickery richard.vickeryrv@gmail.com wrote:
I forgot my user name; the email I used at the time I set the account up
is
richard.vickery@telus.net
I queryed Fedora's awesome IRC bot on your behalf, and can't seem to find a FAS account under either your old or current e-mail or by searching your last name: 21:35 <tchol> .fas richard.vickery@telus.net 21:35 <zodbot> 'richard.vickery@telus.net' Not Found! 21:36 <tchol> .fas richard.vickeryrv@gmail.com 21:36 <zodbot> 'richard.vickeryrv@gmail.com' Not Found! 21:36 <tchol> .fas vickery 21:36 <zodbot> 'vickery' Not Found! # just to make sure name searches are working 21:36 <tchol> .fas t.c. 21:36 <zodbot> patches 'T.C. Hollingsworth' tchollingsworth@gmail.com
Perhaps your account has been deactivated due to inactivity/because that e-mail is no longer valid? Since your e-mail changed anyway, you might as well register for a new one.
-T.C.
I just got in within September.
Why is it not possible to add my karma without an account? Is it not possible to update the old one?
On Tue, Apr 30, 2013 at 9:51 PM, Richard Vickery richard.vickeryrv@gmail.com wrote:
I just got in within September.
Why is it not possible to add my karma without an account? Is it not possible to update the old one?
Did you perhaps set it to private? I wouldn't be able to query it in that case. To regain access, you'd have to contact Fedora Infrastructure at admin@fedoraproject.org
I would presume an account is required to prevent bots and such from being able to affect Fedora updates. I think that requiring an account presents a reasonable barrier of entry for something of this nature, without creating an undue burden. Note that you can still provide feedback to the package maintainer without an account, it is only required to help get things pushed stable before the 7 day timeout.
-T.C.
-
poma -
Richard Vickery -
staticsafe -
T.C. Hollingsworth -
Tom Rivers