Re: gcc-11 fails "misordered hunks" Ventures/Xcode 15

Merle Reinhart <[email protected]>
Newsgroups gmane.os.apple.fink.general
Message-ID <[email protected]>
If I remember correctly, installing the fink patch allows this patch diff to work.

Merle



> On Oct 1, 2023, at 11:21 AM, Scott Hannahs via Fink-users <[email protected]> wrote:
> 
> External Email - Use Caution
> 
> I had this same problem in Monterey / Xcode 14 as well.  But I had an older built version of gcc-11 that was working and so did not report this.  I see that there is an arm and a ventura patch.  This is being built on an Apple  X86-64 system.
> % arch;machine
> i386
> x86_64h
> 
> Here is the the relevant excerpts (I hope) from the console output.  With (hopefully) irrelevant lines elided.
> 
> NOTE: it appears to be applying the ARM patch to this system.  The file mentioned fink.idYDP contains the following, which looks like it is attempting to use the arm patch.
> 
> #!/bin/sh -ev
>         patch -p1 < /opt/sw/fink/dists/stable/main/finkinfo/languages/gcc11-arm.patch
>         #patch -p1 < %{PatchFile2}
>         # don't update live infodoc dir
>         find . -name Makefile.in | xargs perl -pi -e 's/install-info --version/false/g'
> 
> The other script it is trying to execute is also the arm patch!
> #!/usr/bin/perl
> use Fink::Services qw(execute);
> {
> local $/;
> $script = <DATA>;
> }
> exit &execute($script);
> __DATA__
> #!/bin/sh -ev
> patch -p1 < /opt/sw/fink/dists/stable/main/finkinfo/languages/gcc11-arm.patch
> #patch -p1 < %{PatchFile2}
> # don't update live infodoc dir
> find . -name Makefile.in | xargs perl -pi -e 's/install-info --version/false/g'
> 
> Lastly, should I be submitting these issue through GitHub to keep track of things or is this a good forum.
> 
> -Scott
> 
> [console log]
> sudo -u fink-bld [ENV] sh -c /tmp/fink.vJ4j9
> [ -r /opt/sw/fink/dists/stable/main/finkinfo/languages/gcc11-arm.patch ]
> sudo -u fink-bld [ENV] sh -c /tmp/fink.dXxRx
> /tmp/fink.idYDP
> #!/bin/sh -ev
> patch -p1 < /opt/sw/fink/dists/stable/main/finkinfo/languages/gcc11-arm.patch
> patching file Makefile.def
> …..
> patching file ‘gcc/config/aarch64/aarch64-builtins.c'
> patching file 'gcc/config/aarch64/aarch64-c.c'
> patching file 'gcc/config/aarch64/aarch64-protos.h'
> patching file 'gcc/config/aarch64/aarch64-sve-builtins.cc'
> patching file 'gcc/config/aarch64/aarch64.c'
> patch: **** misordered hunks! output would be garbled
> ### execution of /tmp/fink.idYDP failed, exit code 2
> ### execution of /tmp/fink.dXxRx failed, exit code 2
> Removing runtime build-lock...
> Removing build-lock package...
> /opt/sw/bin/dpkg-lockwait -r fink-buildlock-gcc11-11.4.0-1
> (Reading database ... 199629 files and directories currently installed.)
> Removing fink-buildlock-gcc11-11.4.0-1 (2023.10.01-00.23.55) ...
> Failed: phase patching: gcc11-11.4.0-1 failed
> 
> ...
> Also include the following system information:
> Package manager version: 0.45.99.git
> Distribution version: selfupdate-git Sat Sep 30 14:28:48 2023, 13.0, x86_64
> Trees: local/main stable/main
> Xcode.app: 15.0
> Xcode command-line tools: 15.0.0.0.1.1694021235
> Max. Fink build jobs:  1
> 
> _______________________________________________
> Fink-users mailing list
> [email protected]
> List archive:
> https://urldefense.com/v3/__https://sourceforge.net/p/fink/mailman/fink-users/__;!!CrWY41Z8OgsX0i-WU-0LuAcUu2o!08VPyxEutuSmoy1bMxbbkRc1HJqE-QEOK5HJXOsz-6AFIqCCIsxbVkQCI8IQn5wqze3hbK-DTsdp801nRGI4AT-O0IKU$ 
> Subscription management:
> https://urldefense.com/v3/__https://lists.sourceforge.net/lists/listinfo/fink-users__;!!CrWY41Z8OgsX0i-WU-0LuAcUu2o!08VPyxEutuSmoy1bMxbbkRc1HJqE-QEOK5HJXOsz-6AFIqCCIsxbVkQCI8IQn5wqze3hbK-DTsdp801nRGI4AdBeDQ00$



_______________________________________________
Fink-users mailing list
[email protected]
List archive:
https://sourceforge.net/p/fink/mailman/fink-users/
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.