public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: "Ralf Habacker" <Ralf.Habacker@freenet.de>
To: <cygwin-xfree@cygwin.com>
Subject: AW: AW: cygwin.rules - Enabling shared libXt finally?
Date: Wed, 22 Oct 2003 17:16:00 -0000 [thread overview]
Message-ID: <JGEMLHPCGMNLEIGOCPMGIELCIGAA.Ralf.Habacker@freenet.de> (raw)
In-Reply-To: <3F95EA46.4000109@cwilson.fastmail.fm>
No,
there is no functional changes. I only want to make sure, that no c function
in Intrinsic.c can use the symbol _y (in c 'y'),
so this patch renames it to __$XtInherit, which isn't usable for c
functions.
BTW: I was very in rush while doing the last patch, which may fails to be
applied. The symbol which has to be patched is _y and not _$$y like done in
the previous patch. I've added an updated patch.
Ralf
--- 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
Ralf
>
> 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
>
>
prev parent reply other threads:[~2003-10-22 17:16 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
2003-10-22 17:16 ` Ralf Habacker [this message]
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=JGEMLHPCGMNLEIGOCPMGIELCIGAA.Ralf.Habacker@freenet.de \
--to=ralf.habacker@freenet.de \
--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).