Re: DBusKit 0.1.1 with GNU runtime: dk_make_protocol error while building

Patrick Cardona <[email protected]>
Newsgroups gmane.comp.lib.gnustep.general
Message-ID <a994a6c0e552758ff950b6695411b583@pi400>
Hi Yavor,

On 2025-10-27 16:00:32 +0100 Yavor Doganov <[email protected]> wrote:

> Patrick Cardona wrote:
>>   Linking tool dk_make_protocol ...
>> /usr/bin/ld : 
>> ../Source/DBusKit.framework/Versions/Current/./libDBusKit.so : réf
>> érence indéfinie vers « GS_GC_HIDE »
>> /usr/bin/ld : 
>> ../Source/DBusKit.framework/Versions/Current/./libDBusKit.so : réf
>> érence indéfinie vers « GS_GC_UNHIDE »
>> collect2: error: ld returned 1 exit status
> 
> You can use the Debian patch [1] which is taken from the upstream
> repository.
> 
> [1] 
> https://sources.debian.org/src/dbuskit/0.1.1-14/debian/patches/no-gc-macros.patch
> 

Thank you for your help: I tested the patch and I have an error:

patrick@pi400:~/SOURCES/libs-dbuskit-0.1.1/Source $ patch --dry-run --verbose -u DKNotificationCenter.m --input $HOME/dbuskit_GC_macros.patch
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|Description: Remove GC macros as GC is gone from base
|Origin: upstream, commit:r39612
|Bug-Debian: https://bugs.debian.org/878051
|Forwarded: not-needed
|Last-Update: 2017-10-09
|---
|
|--- dbuskit.orig/Source/DKNotificationCenter.m
|+++ dbuskit/Source/DKNotificationCenter.m
--------------------------
checking file DKNotificationCenter.m
Hunk #1 succeeded at 514.
Hunk #2 succeeded at 530.
patch unexpectedly ends in middle of line
Hunk #3 succeeded at 556 with fuzz 1.
done

Can I ignore the "patch unexpectedly ends in middle of line" or is it an error to check more in depth?

Patrick

-- 
Patrick Cardona - Pi400 - GNU/Linux aarch64 (Debian 13.1) 
Xorg (1:7.7+24) - libcairo2 (1.18.4-1+rpt1 arm64)
Window Maker (0.96.0) - GWorkspace (1.1.0 - 02 2025) - Theme: AGNOSTEP - MUA: GNUMail (1.4.0)
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.