From: ralf@uni-koblenz.de
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: "K." <conradp@cse.unsw.edu.au>, linux@cthulhu.engr.sgi.com
Subject: Re: crtbegin.o, crtend.o
Date: Tue, 13 Jan 1998 03:36:23 +0100 [thread overview]
Message-ID: <19980113033623.32297@uni-koblenz.de> (raw)
In-Reply-To: <19980112195622.35682@alpha.franken.de>; from Thomas Bogendoerfer on Mon, Jan 12, 1998 at 07:56:22PM +0100
On Mon, Jan 12, 1998 at 07:56:22PM +0100, Thomas Bogendoerfer wrote:
> > > um... can anyone point out where these files can be obtained? In our
> > > recent install, (Indy R4600) made from the root-be-0.01 root filesystem
> > > with the recent binutils-2.8.1-2, they are missing. We hacked out dummy
> > > object files (crtbegin has a __main() which calls main() and crtend is
> > > empty) and we can successfully compile simple programs; but before we turn
> > > our attention to compiling nastier pieces of code we would like to check
> > > that we have not tainted our /usr/lib :)
> >
> > Upgrade your system with all the rpm packages. root-0.01 was my first
> > collection of Indy executables and basically_every_ ELF file has bugs in
> > it ...
>
> but at least with the little endian gcc rpm you want get crtbegin.o and
> crtend.o, because they are missing. Neither x86, alpha nor sparc have such
> files (at least not in gcc), so they are missing from the redhat .spec file.
> Sorry for the late bug report.
I think we had that topic before. My rpm gcc-2.7.2-2 dated 971213 fixes
that. Think I never uploaded it, sigh ...
Ralf
prev parent reply other threads:[~1998-01-13 2:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-12 5:23 crtbegin.o, crtend.o K.
1998-01-12 8:58 ` ralf
1998-01-12 17:18 ` Alex deVries
1998-01-13 1:36 ` ralf
1998-01-13 3:24 ` Alex deVries
1998-01-12 18:56 ` Thomas Bogendoerfer
1998-01-13 2:36 ` ralf [this message]
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=19980113033623.32297@uni-koblenz.de \
--to=ralf@uni-koblenz.de \
--cc=conradp@cse.unsw.edu.au \
--cc=linux@cthulhu.engr.sgi.com \
--cc=tsbogend@alpha.franken.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.