public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: Alexey Salmin <alexey.salmin@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: gcc trunk and -lmpc
Date: Sat, 24 Apr 2010 11:14:00 -0000	[thread overview]
Message-ID: <mcry6gdslwl.fsf@dhcp-172-17-9-151.mtv.corp.google.com> (raw)
In-Reply-To: <y2x87a8dc11004212116i39636cc6mf3be6f5651e03de2@mail.gmail.com> (Alexey Salmin's message of "Thu\, 22 Apr 2010 11\:16\:25 +0700")

Alexey Salmin <alexey.salmin@gmail.com> writes:

> Hello! Today I tried to build latest gcc trunk (rev #158628) and got
> the following errors:
>
> libbackend.a(builtins.o): In function `fold_builtin_ccos':
> /home/salmin/gcc-trunk/host-x86_64-unknown-linux-gnu/gcc/../.././gcc/builtins.c:7341:
> undefined reference to `mpc_cosh'
> /home/salmin/gcc-trunk/host-x86_64-unknown-linux-gnu/gcc/../.././gcc/builtins.c:7341:
> undefined reference to `mpc_cos'
> libbackend.a(builtins.o): In function `fold_builtin_cexp':
> /home/salmin/gcc-trunk/host-x86_64-unknown-linux-gnu/gcc/../.././gcc/builtins.c:7434:
> undefined reference to `mpc_exp'
> ....
>
> which is surprising because I have libmpc installed (debian sid):
> salmin@salmin:~/gcc-trunk$ dpkg -l libmpc* | grep ^ii | grep -v libmpcdec
> ii  libmpc-dev                           0.8.1-1
>          multiple precision complex floating-point library development
> package
> ii  libmpc2                              0.8.1-1
>          multiple precision complex floating-point library
>
> configuring with LDFLAGS=-lmpc solved the problem. Is it a bug in
> Makefile or something or I'm doing it wrong?

This certainly sounds like a bug in the configure script or the
Makefile.  It may be that since mpc is so new few people have tested
building gcc against an installed libmpc.

Ian

      reply	other threads:[~2010-04-24  1:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-22 10:47 Alexey Salmin
2010-04-24 11:14 ` Ian Lance Taylor [this message]

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=mcry6gdslwl.fsf@dhcp-172-17-9-151.mtv.corp.google.com \
    --to=iant@google.com \
    --cc=alexey.salmin@gmail.com \
    --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).