Re: new package: ghcup-0.1.17.8

[kwshi <kwshi@users.noreply.github.com>]

[-- Attachment #1: Type: text/plain, Size: 1558 bytes --]

New comment by kwshi on void-packages repository

https://github.com/void-linux/void-packages/pull/35624#issuecomment-1152441085

Comment:
> > I've applied @hasufell's patch and gotten the build to work; compilation on/to non-`x86_64` architectures or musl unfortunately doesn't work currently because some of ghcup's dependencies are incompatible (e.g., haskell's `libarchive` package explicitly imports a glibc header).  This package template is ready for review.
> 
> That can't be. The ghcup binaries are built on alpine linux with musl.
> 
> There's a static libarchive option: `-f-system-libarchive`

Weird-- I've tried building with `-f-system-libarchive` and the error still appears. The relevant error message, I think, is
```
c/archive_platform.h:84:10: error:
     fatal error: sys/cdefs.h: No such file or directory
       84 | #include <sys/cdefs.h>
          |          ^~~~~~~~~~~~~
   |
84 | #include <sys/cdefs.h>
```
Where all googled instances of `sys/cdefs.h` seem to point to GNU libc.  The full error log on the workflow run is at https://github.com/void-linux/void-packages.

I've updated the package template to use `-f-system-libarchive`, and as you can see from the [CI logs](https://github.com/void-linux/void-packages/runs/6833102145?check_suite_focus=true) the same error still occurs; cabal is still trying to build the `libarchive` library, even though per my understanding it shouldn't (if we're using static libarchive).

I'll do some more investigation on alpine to see what might explain this disparity.