From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30606 invoked by alias); 6 Feb 2006 19:03:10 -0000 Received: (qmail 30588 invoked by uid 48); 6 Feb 2006 19:03:09 -0000 Date: Mon, 06 Feb 2006 19:03:00 -0000 Message-ID: <20060206190309.30587.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libgcj/17311] Wrong libgcc_s.so.1 is used by lt-gij In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: java-prs@gcc.gnu.org From: "hjl at lucon dot org" Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-prs-owner@gcc.gnu.org X-SW-Source: 2006-q1/txt/msg00144.txt.bz2 List-Id: ------- Comment #16 from hjl at lucon dot org 2006-02-06 19:03 ------- Please read the summary line: "Wrong libgcc_s.so.1 is used by lt-gij". Ld.so will search DT_RPATH first for any shared libraries. If you have DT_RPATH entries pointing to installed paths to libraries/executables in the build tree, when you run such an executable in the build tree, the shared libraries in installed paths will be used, if they exist. That is the newly built shared libraries in the build tree may never be used. Sometimes it is fatal if the shared library in the installed path isn't 100% compatible with the newly built one. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17311