I haven't heard back on this so I pushed ahead on the 3 outstanding
problems by just applying more violence to the code base, basically.
1. For wildcard-originating type variables, I added a flag to the
`TauTv` constructor of `MetaInfo`. The knock-on effects of this change
were smaller than I
https://developer.apple.com/forums/thread/692383 is what I'm thinking
of, but in this case there would still be library references shown by
"otool -L", so I guess that's not what you're seeing.
On Mon, Aug 8, 2022 at 7:49 PM Ryan Scott wrote:
>
> Possibly? I'm not familiar with the system cache
Possibly? I'm not familiar with the system cache you're referring to, but
it's a more solid lead than what I have currently. Do you know how one
would confirm if this is the case or not?
Ryan
___
ghc-devs mailing list
ghc-devs@haskell.org
Any chance this is related to the weird system cache thing for system
dylibs that came in with the most recent OS X releases? I don't think
those show up in the normal way.
On Mon, Aug 8, 2022 at 7:33 PM Ryan Scott wrote:
>
> I should clarify that I'm using a borrowed macOS on which I don't have
I should clarify that I'm using a borrowed macOS on which I don't have
admin privileges, so I'm unable to install pkg-config. As a result, I'm
commenting out the pkgconfig-depends: line in libffi.cabal and manually
specifying the extra-lib-dirs and include-dirs via a cabal.project.local
file.
ahh, pkgconfig is what i was overlooking!
agreed with viktor, using the system provided one is definitely safer
On Mon, Aug 8, 2022 at 10:46 AM Viktor Dukhovni
wrote:
> On Mon, Aug 08, 2022 at 09:59:48AM -0400, Viktor Dukhovni wrote:
>
> > On my MacOS laptop I get:
> >
> > $
On Mon, Aug 08, 2022 at 09:59:48AM -0400, Viktor Dukhovni wrote:
> On my MacOS laptop I get:
>
> $ /usr/local/bin/pkg-config --libs libffi
> -lffi
>
> which does not use the "brew"-installed libffi. Not surprising, since
> /usr/local/lib/pkgconfig/ has no symlink to the "libffi.pc"
On Mon, Aug 08, 2022 at 07:29:38AM -0400, Ryan Scott wrote:
> An exception to this rule is macOS, however. On macOS, building libffi
> always appears to default to linking against the static version of libffi,
> even when a dynamic version is also available. To reproduce this
> phenomenon, check
Bruno Damour writes:
> Hello,
> Thanks for this new release !
> Do you plan to add FreeBSD binaries ?
Yes, I have recently been working on the FreeBSD CI infrastructure [1]
and hope to have this finished in time for 9.4.2.
Cheers,
- Ben
[1]
I'm trying to diagnose strange GHC linking behavior which, as far as I can
tell, only occurs on macOS. I feel a bit out of my league debugging this,
so I'm hoping someone knows what is causing this.
When building the Haskell libffi library [1], it will link pass -lffi to
GHC. Typically, most
10 matches
Mail list logo
