public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gaius Mulley <gaius.mulley@southwales.ac.uk>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, Modula-2 (C/C++/D/F/Go/Jit)] (Register spec fn) (v2)
Date: Tue, 02 Jul 2019 00:18:00 -0000	[thread overview]
Message-ID: <87ef39jnld.fsf@j228-gm.comp.glam.ac.uk> (raw)
In-Reply-To: <20190629180828.GB18316@gate.crashing.org> (Segher Boessenkool's	message of "Sat, 29 Jun 2019 13:08:28 -0500")

Segher Boessenkool <segher@kernel.crashing.org> writes:

> Hi Gaius,
>
> On Fri, Jun 14, 2019 at 02:09:48PM +0100, Gaius Mulley wrote:
>> here is version two of the patches which introduce Modula-2 into the
>> GCC trunk.  The patches include:
>> 
>>   (*)  a patch to allow all front ends to register a lang spec function.
>>        (included are patches for all front ends to provide an empty
>>         callback function).
>>   (*)  patch diffs to allow the Modula-2 front end driver to be
>>        built using GCC Makefile and friends.
>> 
>> The compressed tarball includes:
>> 
>>   (*)  gcc/m2  (compiler driver and lang-spec stuff for Modula-2).
>>        Including the need for registering lang spec functions.
>>   (*)  gcc/testsuite/gm2  (a Modula-2 dejagnu test to ensure that
>>        the gm2 driver is built and can understands --version).
>
> I built on pwoerpc64-linux, with the patch and the tarball.
>
> I first need this patch, because srcdir is an absolute path for me:
>
> ===
> diff --git a/gcc/m2/Make-lang.in b/gcc/m2/Make-lang.in
> index e2d5098..a423a9e 100644
> --- a/gcc/m2/Make-lang.in
> +++ b/gcc/m2/Make-lang.in
> @@ -71,13 +71,13 @@ m2/gm2config.h:
>              export AR ; \
>              RANLIB=`echo $(RANLIB_FOR_TARGET) | sed -e "s/^ //"` ; \
>              export RANLIB ; \
> -            $(SHELL) -c '../$(srcdir)/m2/configure --srcdir=../$(srcdir)/m2 --t
> +            $(SHELL) -c '$(srcdir)/m2/configure --srcdir=$(srcdir)/m2 --target=
>          else \
> -            $(SHELL) -c '../$(srcdir)/m2/configure --srcdir=../$(srcdir)/m2 --t
> +            $(SHELL) -c '$(srcdir)/m2/configure --srcdir=$(srcdir)/m2 --target=
>          fi
>  
>  m2/gm2version.c: m2/gm2version.h
> -	cd m2 ; bash ../$(srcdir)/m2/tools-src/makeversion -p ../$(srcdir)
> +	cd m2 ; bash $(srcdir)/m2/tools-src/makeversion -p $(srcdir)
>  
>  # Build hooks.
>  
> ===
>
> (This patch might not be correct, but it works for me to get things to
> build, at least).
>
> But then I still get build failures: it tries to run xgcc when it hasn't
> been built yet.  ("it" == "something", I didn't keep logs, sorry).
>
> I let it run overnight with -j1, and it finished.  The testsuite is
> running now :-)
>
>
> Segher

Hi Segher,

many thanks for the patch and highlighting the relative vs absolute
srcdir build.  I've fixed the makeversion with a change to the script
(directory option added).  I'll work on the configure line and explore a
solution.  Yes -j1 is definitely an overnight task!


regards,
Gaius

  reply	other threads:[~2019-07-02  0:18 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14 13:10 Gaius Mulley
2019-06-29 10:15 ` Richard Sandiford
2019-06-29 12:52   ` Richard Biener
2019-06-29 20:29   ` Gaius Mulley
2019-06-29 18:08 ` Segher Boessenkool
2019-07-02  0:18   ` Gaius Mulley [this message]
2019-07-03  8:41 ` Rainer Orth
2019-07-08 15:20   ` Gaius Mulley
2019-07-08 15:31     ` Rainer Orth
2019-07-09  9:25       ` Rainer Orth
2019-07-09 11:41         ` Gaius Mulley
2019-07-10 11:50           ` Rainer Orth
2019-07-08 15:41     ` Gaius Mulley
2019-07-08 21:21 ` Matthias Klose
2019-07-09  6:37   ` Matthias Klose
2019-07-09 19:50     ` Gaius Mulley
2019-07-09 21:35       ` Matthias Klose
2019-07-10 17:56         ` Matthias Klose
2019-07-10 20:18           ` Gaius Mulley
2019-07-10 20:38             ` Matthias Klose
2019-07-10 21:16               ` Gaius Mulley
2019-07-09  9:56   ` Matthias Klose
2019-07-09 12:14     ` Gaius Mulley
2019-07-09 13:24       ` Matthias Klose
2019-07-09 13:49         ` Gaius Mulley
2019-07-09 16:23           ` Matthias Klose
2019-07-09 17:22             ` Gaius Mulley
2019-07-09 12:31   ` Rainer Orth
2019-07-09 15:57     ` Gaius Mulley
2019-07-09 17:32       ` Matthias Klose
2019-07-10 20:45         ` Gaius Mulley
2019-07-10 12:11       ` Rainer Orth
2019-07-09 21:36   ` Matthias Klose
2019-07-10 17:11     ` Matthias Klose
2019-07-10 20:49       ` Gaius Mulley
2019-07-11  7:57   ` Matthias Klose
2019-07-11 12:12     ` Gaius Mulley
2019-07-11 16:40       ` Segher Boessenkool
2019-07-11 17:26         ` Gaius Mulley
2019-07-12 15:41           ` Segher Boessenkool
2019-07-12 18:35             ` Gaius Mulley
2019-07-18 20:15   ` Matthias Klose
2019-11-20 10:10     ` Gaius Mulley
2019-07-19 14:22 ` Matthias Klose
2019-07-20 21:41 ` Matthias Klose

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=87ef39jnld.fsf@j228-gm.comp.glam.ac.uk \
    --to=gaius.mulley@southwales.ac.uk \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=segher@kernel.crashing.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).