unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 47480@debbugs.gnu.org
Subject: bug#47480: gprolog: hash mismatch
Date: Tue, 30 Mar 2021 22:16:27 +0200	[thread overview]
Message-ID: <87h7kscs84.fsf@gnu.org> (raw)
In-Reply-To: <861rbwhlce.fsf@gmail.com> (zimoun's message of "Tue, 30 Mar 2021 14:33:53 +0200")

Hi!

zimoun <zimon.toutoune@gmail.com> skribis:

> Basically, most seems a Copyright update and a documentation
> regeneration. Except this:
>
> $ diff -r --no-dereference from-ci/src/Ma2Asm/x86_64_any.c from-upstream/src/Ma2Asm/x86_64_any.c
> 213,214c213,216
> < #if defined(M_x86_64_darwin) || defined(M_x86_64_bsd) || defined(M_x86_64_linux) 
> <   pic_code = 1;			/* NB: on darwin and BSD everything is PIC code, last gcc 6 needs this for linux */
> ---
>> #if defined(M_x86_64_darwin) || defined(M_x86_64_bsd)
>>   pic_code = 1;                 /* NB: on darwin and BSD everything is PIC code */
>> #elif defined(M_x86_64_linux) && __GNUC__ >= 6 /* gcc >= 6 needs PIC for linux */
>>   pic_code = 1;
>
> $ diff -r --no-dereference from-ci/src/Wam2Ma/wam2ma.c from-upstream/src/Wam2Ma/wam2ma.c
> 514c514,516
> <     Syntax_Error("multifile or multifile expected");
> ---
>>     {
>>       Syntax_Error("multifile or multifile expected");
>>     }

Bah, sadness.

Anyway, I guess that means we can update the hash, with a link to this
report for posterity.

Thanks,
Ludo’.




  reply	other threads:[~2021-03-30 20:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29 17:14 bug#47480: gprolog: hash mismatch zimoun
2021-03-29 21:37 ` Ludovic Courtès
2021-03-30 12:33   ` zimoun
2021-03-30 20:16     ` Ludovic Courtès [this message]
2021-11-04 20:53 ` bug#47480: logo " phodina via Bug reports for GNU Guix

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h7kscs84.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=47480@debbugs.gnu.org \
    --cc=zimon.toutoune@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).