From: Michael S. Zick <mszick@goquest.com>
To: gcc@gcc.gnu.org
Subject: Ada-3.1.1 Makefile Madness
Date: Thu, 08 Aug 2002 08:09:00 -0000 [thread overview]
Message-ID: <02080809593600.00968@localhost.localdomain> (raw)
Hi folks...
I seem to have a makefile problem here while bootstraping gcc-3.1.1<c,ada>.
While following the <release>/INSTALL#build.html instructions for building a
native Ada...
When I reach the "make gnatlib_and_tools" step from within
<release>/gcc-bld/gcc...
The archive building fails.
Descending into <release>/gcc-bld/gcc/ada and trying "make gnatlib" allowed
me to capture the attached text which seems to indicate what is going wrong...
The "ar...." command expects the objects (except for "prefix.o") to be in the
<release>/gcc-bld/gcc/ada/rts directory.
The two prior calls to "make" found SOME of them in <release>/gcc-bld/gcc/ada
but didn't build, move or link them into <release>/gcc-bld/ada/rts.
To continue my build, I hand "cp -p 'd" the missing *.o's into rts and
everything else seemed to work.
Would it be possible to get a "Makefile" generated in
<release>/gcc-bld/ada/rts that understands how to go from ../*.ads -> *.o and
also use mt-frag and mh-frag as appropriate?
The existing makefile (Makefile.adalib) in "rts" will build the *.o's in that
directory but complains about the missing archives (which are yet to be
built).
I have made a few other comments in the attached "cut and paste" of the build
output text attached.
Mike
Attachment:
ada-3.1.1-fail.txt
Description: Make output text
next reply other threads:[~2002-08-08 8:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 8:09 Michael S. Zick [this message]
2002-08-08 12:11 ` Florian Weimer
2002-08-08 16:17 ` Michael S. Zick
2002-08-09 0:11 ` Andris Pavenis
2002-08-09 6:35 ` Michael S. Zick
2002-08-09 10:00 ` Michael S. Zick
2002-08-09 14:33 ` Michael S. Zick
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=02080809593600.00968@localhost.localdomain \
--to=mszick@goquest.com \
--cc=gcc@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).