public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andris Pavenis <pavenis@latnet.lv>
To: "Michael S. Zick" <mszick@goquest.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Ada-3.1.1 Makefile Madness
Date: Fri, 09 Aug 2002 00:11:00 -0000	[thread overview]
Message-ID: <200208091009.58422.pavenis@latnet.lv> (raw)
In-Reply-To: <02080818072700.06892@localhost.localdomain>

On Friday 09 August 2002 02:07, Michael S. Zick wrote:
> On Thursday 08 August 2002 02:11 pm, Florian Weimer wrote:
> > Michael S. Zick <mszick@goquest.com> writes:
> > > When I reach the "make gnatlib_and_tools" step from within
> > > <release>/gcc-bld/gcc...
> >
> > Your build directory is inside the source directory tree.  Maybe
> > that's causing the problems you are seeing.
>
> Could well be the problem.
> The instructions do say: "...where objdir is a subdirectory of srcdir ...
> unsupported..."

It didn't work also for me (target i586-pc-msdosdjgpp). Moving build directory 
out of source directory and specifying absolute path to sources worked

>
> BUT - that I was able to get to work with a little file copying.
>
> The organization: <something>/<release>/gcc .... with building in:
> <something>/<bld-gcc>/ .... is a total loser on my machine.
>
> The instructions do say: "... some broken make's ... where srcdir is
> seperate from objdir ... fail".  (No shit!)
>
> So, Question: "What is the minimum REQUIRED version of gnu-make to
> successfully build gcc-3.1.1<c, ada>?   (Note the "Ada").

make-3.79.1 worked OK for me.

Andris

  reply	other threads:[~2002-08-09  0:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-08  8:09 Michael S. Zick
2002-08-08 12:11 ` Florian Weimer
2002-08-08 16:17   ` Michael S. Zick
2002-08-09  0:11     ` Andris Pavenis [this message]
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=200208091009.58422.pavenis@latnet.lv \
    --to=pavenis@latnet.lv \
    --cc=gcc@gcc.gnu.org \
    --cc=mszick@goquest.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).