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

Bug#306280: marked as done (FTBFS: libtool: compile: cannot determine name of library object from `')



Your message dated Fri, 17 Jun 2005 19:32:53 +0200
with message-id <17075.2373.754652.378664@gargle.gargle.HOWL>
and subject line FTBFS: libtool: compile: cannot determine name of library object from `'
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 25 Apr 2005 13:58:12 +0000
>From rene.engelhard@gmx.de Mon Apr 25 06:58:12 2005
Return-path: <rene.engelhard@gmx.de>
Received: from public.id2-vpn.continvity.gns.novell.com (emea3-mh.id2.novell.com) [195.33.99.129] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1DQ46F-0002Ei-00; Mon, 25 Apr 2005 06:58:12 -0700
Received: from localhost
	(l4-client.id2.novell.com [149.44.117.251])
	by emea3-mh.id2.novell.com; Mon, 25 Apr 2005 14:57:31 +0100
Received: by localhost (Postfix, from userid 1000)
	id 265A4356DD; Mon, 25 Apr 2005 15:52:11 +0200 (CEST)
Date: Mon, 25 Apr 2005 15:52:11 +0200
From: Rene Engelhard <rene@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: FTBFS: libtool: compile: cannot determine name of library object from `'
Message-ID: <20050425135211.GA32220@rene-engelhard.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-Reportbug-Version: 3.8
X-PGP-Key: 248AEB73
X-PGP-Fingerprint: 41FA F208 28D4 7CA5 19BB  7AD9 F859 90B0 248A EB73
User-Agent: Mutt/1.5.6+20040907i
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
	autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: gcc-4.0
Severity: serious
Tags: experimental

[...]
/bin/sh ./libtool --mode=compile /home/rene/gcc-4.0-4.0.0/build/gcc/xgcc
-B/home/rene/gcc-4.0-4.0.0/build/gcc/ -B/usr/powerpc-linux/bin/
-B/usr/powerpc-linux/lib/ -isystem /usr/powerpc-linux/include -isystem
/usr/powerpc-linux/sys-include -c -I.
-I/home/rene/gcc-4.0-4.0.0/src/libobjc   -O2 -g -O2 -W -Wall
-Wwrite-strings -Wstrict-prototypes -DHAVE_GTHR_DEFAULT -DIN_GCC
-DIN_TARGET_LIBS -fno-strict-aliasing
-I/home/rene/gcc-4.0-4.0.0/src/libobjc/objc
-I/home/rene/gcc-4.0-4.0.0/src/libobjc/../gcc
-I/home/rene/gcc-4.0-4.0.0/src/libobjc/../gcc/config -I../../gcc
-I/home/rene/gcc-4.0-4.0.0/src/libobjc/../include
/home/rene/gcc-4.0-4.0.0/src/libobjc/thr-objc.c
libtool: compile: cannot determine name of library object from `'
make[4]: *** [thr-objc.lo] Fehler 1
make[4]: Verlasse Verzeichnis
»/home/rene/gcc-4.0-4.0.0/build/powerpc-linux/libobjc«
make[3]: *** [all-target-libobjc] Fehler 2
make[3]: Verlasse Verzeichnis »/home/rene/gcc-4.0-4.0.0/build«
make[2]: *** [bootstrap] Fehler 2
make[2]: Verlasse Verzeichnis »/home/rene/gcc-4.0-4.0.0/build«
s=`cat status`; rm -f status; test $s -eq 0
make[1]: *** [stamps/05-build-stamp] Fehler 1
make[1]: Verlasse Verzeichnis »/home/rene/gcc-4.0-4.0.0«
make: *** [stamps/05-build-stamp] Fehler 2

Grüße/Regards,

René

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: powerpc (ppc)
Kernel: Linux 2.6.11.7
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)

---------------------------------------
Received: (at 306280-done) by bugs.debian.org; 17 Jun 2005 17:32:57 +0000
>From doko@cs.tu-berlin.de Fri Jun 17 10:32:57 2005
Return-path: <doko@cs.tu-berlin.de>
Received: from mail.cs.tu-berlin.de [130.149.17.13] (root)
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1DjKi8-000704-00; Fri, 17 Jun 2005 10:32:56 -0700
Received: from mailhost.cs.tu-berlin.de (postfix@mail.cs.tu-berlin.de [130.149.17.13])
	by mail.cs.tu-berlin.de (8.9.3p2/8.9.3) with ESMTP id TAA01797
	for <306280-done@bugs.debian.org>; Fri, 17 Jun 2005 19:32:54 +0200 (MEST)
Received: from localhost (localhost [127.0.0.1])
	by mailhost.cs.tu-berlin.de (Postfix) with ESMTP id 2770BF2B9
	for <306280-done@bugs.debian.org>; Fri, 17 Jun 2005 19:32:54 +0200 (MEST)
Received: from mailhost.cs.tu-berlin.de ([127.0.0.1])
 by localhost (bueno [127.0.0.1]) (amavisd-new, port 10224) with ESMTP
 id 28294-34 for <306280-done@bugs.debian.org>;
 Fri, 17 Jun 2005 19:32:54 +0200 (MEST) 14101
Received: from bolero.cs.tu-berlin.de (bolero.cs.tu-berlin.de [130.149.19.1])
	by mailhost.cs.tu-berlin.de (Postfix) with ESMTP
	for <306280-done@bugs.debian.org>; Fri, 17 Jun 2005 19:32:53 +0200 (MEST)
Received: (from doko@localhost)
	by bolero.cs.tu-berlin.de (8.12.10+Sun/8.12.8/Submit) id j5HHWrQx029682;
	Fri, 17 Jun 2005 19:32:53 +0200 (MEST)
From: Matthias Klose <doko@cs.tu-berlin.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <17075.2373.754652.378664@gargle.gargle.HOWL>
Date: Fri, 17 Jun 2005 19:32:53 +0200
To: 306280-done@bugs.debian.org
Subject: Re: FTBFS: libtool: compile: cannot determine name of library object from `'
X-Mailer: VM 7.17 under 21.4 (patch 17) "Jumbo Shrimp" XEmacs Lucid
X-Virus-Scanned: by amavisd-new at cs.tu-berlin.de
Delivered-To: 306280-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
	version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

closing, isn't reproducible anymore. gcc-4.0 was updated in the
meantime. please reopen the bug report, if the problem shows up again.



Reply to: