gtk+2 fails to compile (fixed now for 10.15)

Tom Liehe via Fink-beginners <[email protected]>
Newsgroups gmane.os.apple.fink.beginners
Message-ID <[email protected]>
Hi Matthias,

I’m on 10.15 and the fix worked for me. Looks like the solution was to disable cups but I think that only applies to 10.15?

Hanspeter, thanks for the fix. Pretty sure I don’t care about cups! Is that the final solution? I’ve been trying to fix gtkprintbackendcups.c to use the 10.15 ipp accessors, almost finished but am stuck on what to do with attr->num_values. Probably I can drop this effort :)


Hi Matthias,

I’m on 10.15 and the fix worked for me. Looks like the solution was to disable cups but I think that only applies to 10.15? I guess a fix for 10.14 is still needed.

Hanspeter, thanks for the fix. Pretty sure I don’t care about cups! Is that the final solution? I’ve been trying to fix gtkprintbackendcups.c to use the 10.15 ipp accessors, almost finished but am stuck on what to do with attr->num_values. Probably I can drop this effort :)

> On Jan 26, 2020, at 1:56 PM, Matthias Geissbuehler <[email protected] <mailto:[email protected]>> wrote:
> 
> Dear Hanspeter,
> 
> Thanks for your help.
> I just ran a fink selfupdate and fink update-all followed by another attempt of installing octave - and with it GTK:
> It still fails with the same type of errors:
>   (error: incomplete definition of type 'struct _ipp_s').
> (...)
> Failed: phase compiling: gtk+2-2.18.9-13 failed
> 
> 
> Quick notice also: I'm running Mac OS 10.14.6 (not 10.15).
> 
> Any idea if I could do something further?
> Thanks for your help!
> 
> Matthias
> 
> 
> Gtk+2 should now be working on 10.15.
> 
> Hanspeter

_______________________________________________
Fink-beginners mailing list
[email protected]
List archive:
https://sourceforge.net/p/fink/mailman/fink-users/
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-beginners
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.