public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Hiram Clawson, 831-427-7519" <hiramc@sco.COM>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: [Xpert] XFree 4.0.1 module loading
Date: Thu, 17 Aug 2000 21:20:18 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205350@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205303@msgid-missing>

Rather than trying to work with the XFree86 X server to fix up this
loading situation, it is a lot easier to create a couple of tiny
example programs that dlopen() each other to watch the interaction.

I believe you are talking about the sequence:

	main() dlopens foo0()
	foo0() and main() can freely exchange references with each other.
	Now foo0() dlopens foo1()
	The question is, which of main(), foo0() and foo1() can freely
	exchange references with each other ?  Which types of
	dynamic loading schemes will allow all loaded programs to share
	all symbols.

--Hiram

 Date: Thu, 17 Aug 2000 12:13:33 -0400 (EDT)
 From: Stuart Anderson <anderson@metrolink.com>
 To: Marc Aurele La France <tsi@gpu.srv.ualberta.ca>
 cc: Keith Owens <kaos@ocs.com.au>, Michael Madore <mmadore@turbolinux.com>, 
     Bill Nottingham <notting@redhat.com>, linux-ia64@linuxia64.org
 Subject: Re: [Linux-ia64] Re: [Xpert] XFree 4.0.1 module loading 
 
 I've received some code, and should have hardware soon, so I was planning
 on working on it.
 
 On Wed, 16 Aug 2000, Marc Aurele La France wrote:
 
 > On Fri, 11 Aug 2000, Keith Owens wrote:
 > 
 > > >> I guess my question now is:  Should the dlopen() loader be able to
 > > >> resolve inter-module dependencies?  If not, what is left to be done with
 > > >> the elf loader make it functional on IA64?
 > 
 > > >Support for the ELF64 relocation types. Just like a block of code was 
added
 > > >for Alpha support, the same type of thing will have to be added for IA64.
 > 
 > > modutils 2.3.13 has IA64 relocation support, courtesy of Mike Stephens
 > > at Intel.  obj/obj_ia64.c should be a reasonable starting point.
 > 
 > Is anyone going ahead with this?  If not, I can probably come pretty close
 > to getting it working even though I'd be going in blind (no hardware).
 > 
 > Let me know.
 > 
 > Marc.
 > 
 > +----------------------------------+-----------------------------------+
 > |  Marc Aurele La France           |  work:   1-780-492-9310           |


  parent reply	other threads:[~2000-08-17 21:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-10  3:26 [Linux-ia64] Re: [Xpert] XFree 4.0.1 module loading Marc Aurele La France
2000-08-10  4:08 ` Bill Nottingham
2000-08-10  5:34 ` Michael Madore
2000-08-10  5:37 ` Michael Madore
2000-08-10 15:38 ` Marc Aurele La France
2000-08-10 15:42 ` Bill Nottingham
2000-08-10 16:54 ` Stuart Anderson
2000-08-10 17:00 ` Michael Madore
2000-08-10 17:59 ` Bill Nottingham
2000-08-10 18:06 ` Stuart Anderson
2000-08-11  0:16 ` Keith Owens
2000-08-11 15:10 ` David Dawes
2000-08-17  3:29 ` Marc Aurele La France
2000-08-17  6:18 ` Michael Madore
2000-08-17 16:13 ` Stuart Anderson
2000-08-17 21:20 ` Hiram Clawson, 831-427-7519 [this message]
2000-08-18  2:24 ` Marc Aurele La France

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=marc-linux-ia64-105590678205350@msgid-missing \
    --to=hiramc@sco.com \
    --cc=linux-ia64@vger.kernel.org \
    /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