public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: marwijn.hessel@ict.nl
To: gcc-gnats@gcc.gnu.org
Subject: c++/10601: Mixing C and C++ files
Date: Fri, 02 May 2003 10:06:00 -0000	[thread overview]
Message-ID: <20030502095620.9309.qmail@sources.redhat.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]


>Number:         10601
>Category:       c++
>Synopsis:       Mixing C and C++ files
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri May 02 10:06:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     M.W. Hessel
>Release:        Power-eabi cross gcc-3.2.2, binutils-2.13.2, newlib-1.11.0
>Organization:
>Environment:
Cygwin on a PII platform
>Description:
Cross compiling *.c and *.s, for power-eabi, using GCC v3.2.2, running with Cygwin, it seems to work fine. The generated .ABS file is read by insight v5.3 (source level debugger), and can be downloaded into the target (wurz mpc555 board).

When added a *.cpp file to the project, the linker complains about ‘undefined reference to `__gxx_personality_v0'’. This can be solved by adding the ‘-r’ option the de linker commands (according to the GCC user manual).
The generated .ABS can not be read by insight v5.3. It seems that the generated symbol table is not correct.
>How-To-Repeat:
See description
>Fix:
Not known
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-05-02 10:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-02 10:06 marwijn.hessel [this message]
2003-05-02 10:30 giovannibajo
2003-05-02 16:36 Daniel Jacobowitz
2003-05-03 16:36 M.W. Hessel

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=20030502095620.9309.qmail@sources.redhat.com \
    --to=marwijn.hessel@ict.nl \
    --cc=gcc-gnats@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).