public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gzp at gmx dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libmudflap/38339] libtool: compile: not configured to build any kind of library
Date: Tue, 30 Dec 2008 08:00:00 -0000	[thread overview]
Message-ID: <20081230075925.30500.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38339-15827@http.gcc.gnu.org/bugzilla/>



------- Comment #11 from gzp at gmx dot net  2008-12-30 07:59 -------
Ok, but seems like the problem is around libtool. I don't know how libtool
copied/generated in libmudflap directory, but replacing that file with (GNU
libtool) 1.5.26 (1.1220.2.492 2008/01/30 06:40:56) solves the problem.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38339


  parent reply	other threads:[~2008-12-30  8:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-01  7:57 [Bug libmudflap/38339] New: " gzp at gmx dot net
2008-12-01  8:05 ` [Bug libmudflap/38339] " gzp at gmx dot net
2008-12-24  1:31 ` pinskia at gcc dot gnu dot org
2008-12-24  1:34 ` pinskia at gcc dot gnu dot org
2008-12-27  9:09 ` gzp at gmx dot net
2008-12-29 14:26 ` rwild at gcc dot gnu dot org
2008-12-29 23:38 ` gzp at gmx dot net
2008-12-29 23:39 ` gzp at gmx dot net
2008-12-29 23:41 ` gzp at gmx dot net
2008-12-29 23:42 ` gzp at gmx dot net
2008-12-30  0:06 ` pinskia at gcc dot gnu dot org
2008-12-30  8:00 ` gzp at gmx dot net [this message]
2009-01-29 10:43 ` gzp at gmx dot net
2010-09-22 18:49 ` rwild at gcc dot gnu dot org
     [not found] <bug-38339-4@http.gcc.gnu.org/bugzilla/>
2010-09-29 13:38 ` gzp at gmx dot net
2010-09-30  0:21 ` rwild at gcc dot gnu.org
2010-10-01 18:42 ` gzp at papp dot hu
2010-10-02  5:34 ` rwild at gcc dot gnu.org
2010-10-02  6:56 ` gzp at papp dot hu
2010-10-02  6:58 ` gzp at papp dot hu
2010-10-02  7:13 ` rwild at gcc dot gnu.org
2010-10-02  7:17 ` gzp at papp dot hu

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=20081230075925.30500.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).