--- Comment #13 from ramana at gcc dot gnu dot org 2010-03-20 00:09 ---
I think the documentation is adequate in the sense that it is for installation
into a "staging area" rather than the final install area. Notice also the use
of installing this into a chroot.
cheers
Ramana
--
ra
--- Comment #12 from jlpoole at pon dot net 2010-01-07 14:26 ---
Success.
There were no further responses to my question posed in Comment #10; so I
proceeded nonetheless.
I deleted /usr/local/gcj and recreated the directory /usr/local/gcj so as to
purge any hand-added files from previo
--- Comment #11 from jlpoole at pon dot net 2010-01-05 02:34 ---
For the record:
plug build # ls -la config.log
-rw-r--r-- 1 root root 36708 2010-01-03 17:37 config.log
plug build # head config.log
This file contains any messages produced by compilers while
running configure, to aid debu
--- Comment #10 from jlpoole at pon dot net 2010-01-05 02:31 ---
http://gcc.gnu.org/install/finalinstall.html has:
v
...
We strongly recommend to install into a target directory where there is no
previous version of GCC present.
...
Installation into a temporary staging area or into
--- Comment #9 from jakub at gcc dot gnu dot org 2010-01-04 14:20 ---
BTW, DESTDIR is documented e.g. in automake.info quite well.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42409
--- Comment #8 from ramana at gcc dot gnu dot org 2010-01-04 11:32 ---
Waiting for feedback on this one as per Comment #7.
--
ramana at gcc dot gnu dot org changed:
What|Removed |Added
---
--- Comment #7 from jlpoole at pon dot net 2010-01-04 01:51 ---
Thank you.
I've updated trunk to Revision: 155601. Wiped out build and am running make
(it will take a few days). I'll update with my results.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42409
--- Comment #6 from jakub at gcc dot gnu dot org 2010-01-03 18:55 ---
That's just a misunderstanding what DESTDIR is. DESTDIR just says a directory
where the / dir of installed files starts. It is used when you e.g. want to
install everything into a temporary directory to package it up
--- Comment #5 from jlpoole at pon dot net 2010-01-03 18:43 ---
Here's my configuration log:
plug build # pwd
/mnt/seagate2/download/gnu/build
plug build # head config.log
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes
--- Comment #4 from jlpoole at pon dot net 2010-01-03 18:30 ---
I think I found the problem:
the compiler is using an incorrect path, e.g. "/usr/share/java", to find the
ecj.jar file and the other jar files, libgcj-4.5.0.jar
libgcj-tools-4.5.0.jar, when it should have used
"/usr/loc
--- Comment #3 from jlpoole at pon dot net 2010-01-03 18:23 ---
Created an attachment (id=19456)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19456&action=view)
work-around output
To overcome the misdirected path, I created a "java" directory under /usr/share
and copied the /usr/
--- Comment #2 from jlpoole at pon dot net 2010-01-03 18:21 ---
Created an attachment (id=19454)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19454&action=view)
output under normal circumstances
In this output, the compiler incorrectly looks for the ecj.jar under
/usr/share/java
--- Comment #1 from jlpoole at pon dot net 2009-12-24 16:23 ---
I learned from http://gcc.gnu.org/ml/java/2008-08/msg00031.html (Andrew Haley)
how to invoke the test suite:
make check-target-libjava
Here are my results:
make check-target-libjava
...
[assorted make executions]
...
WAR
13 matches
Mail list logo
