public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "andrew.pennebaker at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/61891] New: line-map.c: file "<command-line>" left but not entered during `cabal install -p haskell-src-exts`
Date: Wed, 23 Jul 2014 23:07:00 -0000	[thread overview]
Message-ID: <bug-61891-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61891

            Bug ID: 61891
           Summary: line-map.c: file "<command-line>" left but not entered
                    during `cabal install -p haskell-src-exts`
           Product: gcc
           Version: 4.8.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: andrew.pennebaker at gmail dot com

When I install the haskell-src-exts Cabal package, including profiling
information, with:

$ cabal install -p haskell-src-exts

I see an error reported by GCC:

line-map.c: file "<command-line>" left but not entered

I spend more of my time in Haskell than C, so I'm not quite sure what's going
wrong. Maybe look in the C sources for haskell-src-exts or its dependencies to
find the line-map.c file that triggers the error?

System:

* GHC 7.6.3
* GCC 4.8.2
* Ubuntu 14.04


             reply	other threads:[~2014-07-23 23:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-23 23:07 andrew.pennebaker at gmail dot com [this message]
2014-07-24  6:27 ` [Bug preprocessor/61891] " mpolacek 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-61891-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).