From: Olumide <50295@web.de>
To: gcc-help@gcc.gnu.org
Subject: Re: Compiling gcc-4.1.2 on 64-bit Ubuntu machines
Date: Tue, 25 Jan 2011 10:30:00 -0000 [thread overview]
Message-ID: <4D3EA686.4090806@web.de> (raw)
In-Reply-To: <4D386FB7.1010407@web.de>
On 20/01/2011 17:24, Olumide wrote:
> Good news.
>
> Build was successful -- I think, here's the log file http://goo.gl/SnKsP
>
> (I had to compiled and install textinfo version 4.9 and install the
> latest version ncurses in order to compile texinfo.)
I would like to roll out the build to other machines (several dozen
actually). I've tried copying the entire hierarchy (source and build) to
the target machines and then running make install but I'm getting the
error message (I'd appreciate help solving this problem -- thanks):
make[1]: Entering directory `/transfer/gcc.install/gcc412/gcc-build'
/bin/sh ../gcc-4.1.2/mkinstalldirs /opt/gcc412 /opt/gcc412
make[2]: Entering directory `/transfer/gcc.install/gcc412/gcc-build/fastjar'
/bin/sh ./config.status --recheck
running /bin/sh /transfer/gcc412/gcc-4.1.2/fastjar/configure
--cache-file=./config.cache --build=x86_64-unknown-linux-gnu
--host=x86_64-unknown-linux-gnu --target=x86_64-unknown-linux-gnu
--prefix=/opt/gcc412 --enable-shared --enable-threads=posix
--enable-checking=release --with-system-zlib
--disable-libunwind-exceptions --disable-multilib
--enable-languages=c,c++,java,objc --program-transform-name=s,$,412,;
--srcdir=../../gcc-4.1.2/fastjar CC=gcc CFLAGS=-g -O2 LDFLAGS=
build_alias=x86_64-unknown-linux-gnu host_alias=x86_64-unknown-linux-gnu
target_alias=x86_64-unknown-linux-gnu --no-create --no-recursion
/bin/sh: Can't open /transfer/gcc412/gcc-4.1.2/fastjar/configure
make[2]: *** [config.status] Error 2
make[2]: Leaving directory `/transfer/gcc.install/gcc412/gcc-build/fastjar'
make[1]: *** [install-fastjar] Error 2
make[1]: Leaving directory `/transfer/gcc.install/gcc412/gcc-build'
make: *** [install] Error 2
next prev parent reply other threads:[~2011-01-25 10:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 14:48 Olumide
2011-01-19 15:01 ` Cedric Roux
2011-01-19 15:51 ` Olumide
2011-01-19 16:21 ` Ian Lance Taylor
2011-01-19 16:37 ` Olumide
2011-01-19 16:39 ` Andrew Haley
2011-01-19 17:08 ` Olumide
2011-01-19 17:11 ` Andrew Haley
2011-01-19 20:13 ` Olumide
2011-01-19 21:51 ` David Daney
2011-01-20 13:56 ` Olumide
2011-01-20 17:23 ` Olumide
2011-01-20 20:04 ` Jonathan Wakely
2011-01-25 10:30 ` Olumide [this message]
2011-01-25 10:59 ` Kai Ruottu
2011-01-25 10:59 ` Jonathan Wakely
2011-01-25 11:34 ` Olumide
2011-01-25 11:56 ` Jonathan Wakely
2011-01-25 13:51 ` Olumide
2011-01-19 16:43 ` Cedric Roux
2011-01-19 16:47 ` Jonathan Wakely
2011-01-19 15:19 ` Jeff Law
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D3EA686.4090806@web.de \
--to=50295@web.de \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).