public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "kris dot van dot hees at oracle dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/4725] New: Linking of funit-scopes.c fails with --coverage -O0 is specified
Date: Mon, 02 Jul 2007 21:08:00 -0000 [thread overview]
Message-ID: <20070702210800.4725.kris.van.hees@oracle.com> (raw)
When building frysk without --enable-coverage (compilation and link options
include -g -O), funit-scopes.c compiles and links correctly.
When building frysk with --enable-coverage (compilation and link options include
-g --coverage --O0), funit-scopes.c compiles correctly, but fails to link with
the following error:
gcc
-I/home/aedil/build_farm/frysk_gcov/frysk_config/frysk-core/../frysk-imports/include
-I/home/aedil/build_farm/frysk_gcov/frysk_config/frysk-core -I. -fPIC
-fasynchronous-unwind-tables -g --coverage -O0 -Wall -Werror -o
frysk/pkglibdir/funit-scopes frysk/pkglibdir/funit-scopes.o
frysk/pkglibdir/funit-scopes.o: In function `first':
/home/aedil/build_farm/frysk_gcov/frysk_config/frysk-core/frysk/pkglibdir/funit-scopes.c:13:
undefined reference to `second'
collect2: ld returned 1 exit status
make[2]: *** [frysk/pkglibdir/funit-scopes] Error 1
This is happening on FC6, both on i386 and x86_64.
Gcc version is gcc version 4.1.1 20070105 (Red Hat 4.1.1-51).
The only change between a previous successful build of frysk and the current
failures (as far as this file is concerned) is the actual content of the source
code file (same GCC versions etc).
Investigating this problem a bit further, but it seems to be a bug in gcc.
--
Summary: Linking of funit-scopes.c fails with --coverage -O0 is
specified
Product: frysk
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: general
AssignedTo: frysk-bugzilla at sourceware dot org
ReportedBy: kris dot van dot hees at oracle dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=4725
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2007-07-02 21:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 21:08 kris dot van dot hees at oracle dot com [this message]
2007-07-03 18:04 ` [Bug general/4725] " kris dot van dot hees at oracle dot com
2007-07-03 18:05 ` kris dot van dot hees at oracle dot com
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=20070702210800.4725.kris.van.hees@oracle.com \
--to=sourceware-bugzilla@sourceware.org \
--cc=frysk-bugzilla@sourceware.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).