public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amylaar at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/55144] New: opening glibc-c.o: No such file or directory
Date: Wed, 31 Oct 2012 03:48:00 -0000	[thread overview]
Message-ID: <bug-55144-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 55144
           Summary: opening glibc-c.o: No such file or directory
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Keywords: build
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: amylaar@gcc.gnu.org
            Blocks: 47093
            Target: bfin-linux-uclibc, cris-linux, crisv32-linux,
                    m32rle-linux, m32r-linux


Since glibc-c.c has been added, a number of targets are configured to
link with glibc-c.o, yet t-glibc is not in tmake_file - presumably because
there was no need before to use ${tmake_file} - possibly even a reason not
to use it - in the tmake_file setting for the affected targets in config.gcc.


             reply	other threads:[~2012-10-31  3:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-31  3:48 amylaar at gcc dot gnu.org [this message]
2013-04-16 10:15 ` [Bug target/55144] " mans at mansr dot com
2015-04-22  8:26 ` aldot at gcc dot gnu.org
2015-04-22  8:48 ` aldot at gcc dot gnu.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-55144-4@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).