From: H.J. Lu <hjl@lucon.org>
To: egcs@cygnus.com
Subject: Re: fixing the c++/f77 circular dependency
Date: Mon, 25 Aug 1997 18:48:33 -0000 [thread overview]
Message-ID: <m0x34Cg-0004ecC@ocean.lucon.org> (raw)
In-Reply-To: u9pvr26rln.fsf@yorick.cygnus.com
>
> >>>>> Jim Wilson <wilson@cygnus.com> writes:
>
> > I'd like to see them in libgcc.a. It should not be hard to put
> > something in libgcc.a from cp/Makefile.
>
> > I am not opposed to having C++ code in libgcc.a if it can be made to
> > work. However, having already dealt with a number of problems resulting
> > from this, I am skeptical that it can be made to work cleanly.
>
> That may be. The code currently in libgcc is the freestanding library,
> which includes some code called by various language constructs, and
> therefore needs to be linked in automatically. I don't want people to have
> to pull in libstdc++ to get RTTI support.
>
> The only other option would seem to be a third library, linked in along
> with libgcc. Then the trick is insinuating it into the specs file.
>
Could someone please tell me why we cannot put a target libgcc.a in
cp/Makefile.in? It will resolve that problem. I am willing to
write a patch if people think it is a good idea.
--
H.J. Lu (hjl@gnu.ai.mit.edu)
WARNING: multiple messages have this Message-ID
From: Olivier Galibert <Olivier.Galibert@mines.u-nancy.fr>
To: egcs@cygnus.com
Subject: Re: fixing the c++/f77 circular dependency
Date: Mon, 25 Aug 1997 19:30:13 -0000 [thread overview]
Message-ID: <m0x34Cg-0004ecC@ocean.lucon.org> (raw)
Message-ID: <19970825193013.4gl_HCRTpQ_fh1Vp9lUPWb49qlI0VHoJIxU31IctNL8@z> (raw)
In-Reply-To: u9pvr26rln.fsf@yorick.cygnus.com
On Mon, Aug 25, 1997 at 11:32:36AM -0700, Jason Merrill wrote:
> The only other option would seem to be a third library, linked in along
> with libgcc. Then the trick is insinuating it into the specs file.
This would be quite a pain if you want to link together C++ and fortran
object files...
OG.
next reply other threads:[~1997-08-25 18:48 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-25 18:48 H.J. Lu [this message]
1997-08-25 19:30 ` Olivier Galibert
-- strict thread matches above, loose matches on Subject: below --
1997-08-30 12:00 Incorrect i960 linker config Stephen Williams
1997-08-30 19:18 ` fixing the c++/f77 circular dependency Joel Sherrill
1997-08-30 12:00 Stephen Williams
1997-08-25 21:30 Jim Wilson
1997-08-25 21:22 Jim Wilson
1997-08-25 21:28 ` Robert Lipe
1997-08-25 21:16 Joe Buck
1997-08-25 20:59 meissner
1997-08-25 20:41 David Edelsohn
1997-08-25 20:47 ` Robert Lipe
1997-08-25 20:59 ` Jason Merrill
1997-08-25 20:25 Joe Buck
1997-08-25 20:25 H.J. Lu
1997-08-25 20:08 Jim Wilson
1997-08-25 18:29 egcs release H.J. Lu
1997-08-25 18:32 ` fixing the c++/f77 circular dependency Jason Merrill
1997-08-24 3:43 Building of generated parser files Jim Meyering
1997-08-24 3:43 ` fixing the c++/f77 circular dependency Jim Wilson
1997-08-22 19:47 H.J. Lu
1997-08-22 19:23 Mike Stump
1997-08-22 19:23 Jim Wilson
1997-08-22 19:23 egcs-ss-970814 on m68k-next-nextstep3 Jeffrey A Law
1997-08-22 19:23 ` fixing the c++/f77 circular dependency Jim Wilson
1997-08-22 17:41 H.J. Lu
1997-08-22 8:36 Andreas Schwab
1997-08-21 18:45 Jim Wilson
1997-08-21 16:51 Problems on PowerPC David Edelsohn
1997-08-21 17:43 ` fixing the c++/f77 circular dependency Dave Love
1997-08-21 17:47 ` Dave Love
1997-08-21 9:21 Problems on PowerPC David McWherter
1997-08-21 9:21 ` fixing the c++/f77 circular dependency Andreas Schwab
1997-08-21 4:52 Doug Evans
1997-08-21 3:05 Ultrasparc addition for sparc.md (fwd) Oleg Krivosheev
1997-08-21 4:27 ` fixing the c++/f77 circular dependency Alexandre Oliva
1997-08-20 23:19 [REQ] If the x86 people could do something about this John Beppu
1997-08-20 23:19 ` fixing the c++/f77 circular dependency Doug Evans
1997-08-20 22:18 Jim Wilson
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=m0x34Cg-0004ecC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=egcs@cygnus.com \
/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).