public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Harold L Hunt II <huntharo@msu.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: AW: cygwin.rules - Enabling shared libXt finally?
Date: Wed, 22 Oct 2003 02:39:00 -0000 [thread overview]
Message-ID: <3F95EDD1.5030900@msu.edu> (raw)
In-Reply-To: <3F95EA46.4000109@cwilson.fastmail.fm>
I would be okay with that if it happened. I am the one that recompiled
lesstif and I don't think that the maintainers of other Xt-dependent
apps have recompiled yet.
However, if it isn't a big deal then I will wait until the 4.4.0 release
to make this change. 4.4.0 should be released around December some time.
Harold
Charles Wilson wrote:
> Errm, this isn't going to change the public interface is it? That is,
> if Harold releases another libXt with this change, would that break the
> recently re-compiled and released lesstif, etc etc?
>
> --
> Chuck
>
> Ralf Habacker wrote:
>
>>> Not sure I understand. What should be changed in the current version
>>> of the Xt code?
>>
>>
>>
>> only note 1, chaning the label. The second note is only for completeness.
>>
>>
>>> Attached are my curent xc/lib/Xt/[Initialize.c|IntrinsicP.h] files.
>>> Please send a diff against these if anything should be changed. Note
>>> that these are intentionally from the 4.3 branch.
>>>
>>
>> --- Initialize-old.c 2003-10-21 20:21:18.000000000 +0200
>> +++ Initialize.c 2003-10-21 20:23:25.000000000 +0200
>> @@ -236,8 +236,8 @@
>>
>> asm (".data\n\
>> .globl __XtInherit \n\
>> - __XtInherit: jmp *_$$y \n\
>> - _$$y: .long ___XtInherit \n\
>> + __XtInherit: jmp *__$XtInherit \n\
>> + __$XtInherit: .long ___XtInherit \n\
>> .text \n");
>>
>> #define _XtInherit __XtInherit
>
>
next prev parent reply other threads:[~2003-10-22 2:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 7:43 Ralf Habacker
2003-10-21 13:10 ` Harold L Hunt II
2003-10-21 18:30 ` AW: " Ralf Habacker
2003-10-22 2:22 ` Charles Wilson
2003-10-22 2:39 ` Harold L Hunt II [this message]
2003-10-22 17:16 ` AW: " Ralf Habacker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F95EDD1.5030900@msu.edu \
--to=huntharo@msu.edu \
--cc=cygwin-xfree@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).