public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/39395]  New: cloog link failure with non-gcc bootstrap compiler
Date: Sat, 07 Mar 2009 08:29:00 -0000	[thread overview]
Message-ID: <bug-39395-9596@http.gcc.gnu.org/bugzilla/> (raw)

I usually bootstrap the weekly snapshot of gcc 4.4
with the Intel C compiler.

This usually works, but this week snapshot 20090306 didn't.

There seem to be some fun & games with linking together to
make cc1-dummy.

icc -g -fkeep-inline-functions -DIN_GCC   -W -Wall -Wwrite-strings
-Wstrict-prot
otypes -Wmissing-prototypes -Wcast-qual -Wold-style-definition -Wc++-compat
-Wmi
ssing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros
-Wno-overle
ngth-strings -fno-common  -DHAVE_CONFIG_H  -o cc1-dummy c-lang.o stub-objc.o
att
ribs.o c-errors.o c-lex.o c-pragma.o c-decl.o c-typeck.o c-convert.o
c-aux-info.
o c-common.o c-opts.o c-format.o c-semantics.o c-ppoutput.o c-cppbuiltin.o
c-obj
c-common.o c-dump.o c-pch.o c-parser.o i386-c.o c-gimplify.o tree-mudflap.o
c-pr
etty-print.o c-omp.o dummy-checksum.o \
          main.o tree-browser.o libbackend.a ../libcpp/libcpp.a
../libdecnumber/
libdecnumber.a ../libcpp/libcpp.a   ../libiberty/libiberty.a
../libdecnumber/lib
decnumber.a -L/lib -lcloog -L/lib -lppl_c -lppl -lgmpxx -lmpfr -lgmp
libbackend.a(graphite.o): In function `cloog_finalize':
/usr/include/cloog/ppl_backend.h:54: undefined reference to `ppl_finalize'
libbackend.a(graphite.o): In function `schedule_to_scattering':
/home/dcb/gcc/20090306/working/gcc/../../src/gcc-4.4-20090306/gcc/graphite.c:666
: undefined reference to `cloog_matrix_alloc'
libbackend.a(graphite.o): In function `print_graphite_bb':
/home/dcb/gcc/20090306/working/gcc/../../src/gcc-4.4-20090306/gcc/graphite.c:708
: undefined reference to `cloog_matrix_print'
/home/dcb/gcc/20090306/working/gcc/../../src/gcc-4.4-20090306/gcc/graphite.c:747
: undefined reference to `cloog_matrix_print'
/home/dcb/gcc/20090306/working/gcc/../../src/gcc-4.4-20090306/gcc/graphite.c:748
: undefined reference to `cloog_matrix_free'
...

Given the number of function with names starting with "cloog", I'd guess
that something has gone wrong in the detection of the correct location
of the cloog libraries.

Using -L/lib for -lcloog looks deeply suspicious to me.
Even more so, -L/lib for -lppl_c and -lppl.


-- 
           Summary: cloog link failure with non-gcc bootstrap compiler
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: dcb314 at hotmail dot com
  GCC host triplet: x86_64-suse-linux


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


             reply	other threads:[~2009-03-07  8:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-07  8:29 dcb314 at hotmail dot com [this message]
2009-03-07 15:30 ` [Bug bootstrap/39395] " spop at gcc dot gnu dot org
2009-03-08 12:37 ` dcb314 at hotmail dot com
2010-02-08  5:58 ` spop at gcc dot gnu dot org

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=bug-39395-9596@http.gcc.gnu.org/bugzilla/ \
    --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).