Re: [Fink-devel] Lesstif/nedit/... problems - possibly cause

2002-01-26 Thread David R. Morrison
Hi Martin. Yes, geomview depends on lesstif too, so presumably this is again the same problem. Has anybody had any trouble with any package other than those which depend on lesstif? (I just compiled a list: ddd, nedit, geomview, grace, xephem, mgv, amaya, xbae). Ultimately, it would be nice to

Re: [Fink-devel] Lesstif/nedit/... problems - possibly cause

2002-01-26 Thread Martin Costabel
"David R. Morrison" wrote: > > If Martin's observation is correct, a concern arises: How was the binary > being distributed by xfree86.org compiled, and is it still equivalent > to fink's, for the purposes of installing other fink packages? Dave, I just wrote about this to the XonX users forum,

Re: [Fink-devel] Lesstif/nedit/... problems - possibly cause

2002-01-25 Thread Jeff Whitaker
> > I may have found something. If it's true, it would be trivial to fix: > > I recompiled libXt (in xfree86-4.2.0) with the -flat_namespace > flag, and I think the bug has disappeared. > > The reason that it worked with the libXt from 4.1.0 is that that > one came from a binary distribution compi

Re: [Fink-devel] Lesstif/nedit/... problems - possibly cause

2002-01-25 Thread Max Horn
At 11:10 Uhr -0500 25.01.2002, David R. Morrison wrote: >If Martin's observation is correct, a concern arises: How was the binary >being distributed by xfree86.org compiled, and is it still equivalent >to fink's, for the purposes of installing other fink packages? I think they compile it just as

Re: [Fink-devel] Lesstif/nedit/... problems - possibly cause

2002-01-25 Thread Max Horn
At 16:48 Uhr +0100 25.01.2002, Martin Costabel wrote: >On vendredi, janvier 25, 2002, at 02:14 , Max Horn wrote: > >>Let us look at it from this point: It all used to work. Then came >>XFree86 4.2.0 and it stopped to work. Now, what exactly changed to >>make it stop work, I wonder? The only thin

Re: [Fink-devel] Lesstif/nedit/... problems - possibly cause

2002-01-25 Thread David R. Morrison
If Martin's observation is correct, a concern arises: How was the binary being distributed by xfree86.org compiled, and is it still equivalent to fink's, for the purposes of installing other fink packages? -- Dave ___ Fink-devel mailing list [EMAIL P

Re: [Fink-devel] Lesstif/nedit/... problems - possibly cause

2002-01-25 Thread Martin Costabel
On vendredi, janvier 25, 2002, at 02:14 , Max Horn wrote: > Let us look at it from this point: It all used to work. Then came > XFree86 4.2.0 and it stopped to work. Now, what exactly changed to > make it stop work, I wonder? The only thing that varied where the > XFree libs. So we should mayb

Re: [Fink-devel] Lesstif/nedit/... problems - possibly cause

2002-01-25 Thread Max Horn
At 13:46 Uhr +0100 25.01.2002, Martin Costabel wrote: >Max Horn wrote: > >> So, maybe the suggestion the linker gives us, to use "-bind_at_load" >> might indeed be the way to go. Maybe somebody could test the result >> with this? > >Doesn't help. Even the advice about using -bind_at_load remain

Re: [Fink-devel] Lesstif/nedit/... problems - possibly cause

2002-01-25 Thread Jeff Whitaker
> >> So, maybe the suggestion the linker gives us, to use "-bind_at_load" > >> might indeed be the way to go. Maybe somebody could test the result > >> with this? > >> > > > >Max: I tried this with nedit - same error. > > Same error, ok :/ > > What does "otool -L /sw/bin/nedit" give ? And what

Re: [Fink-devel] Lesstif/nedit/... problems - possibly cause

2002-01-25 Thread Max Horn
At 5:25 Uhr -0700 25.01.2002, Jeff Whitaker wrote: > > >> >> >However, the static link editor always >> >produces the same linking as the dynamic linker as long as >> >none of the dynamic shared libraries define the same sym- >> >bol. Different linking can occur only when there is more >

Re: [Fink-devel] Lesstif/nedit/... problems - possibly cause

2002-01-25 Thread Martin Costabel
Max Horn wrote: > So, maybe the suggestion the linker gives us, to use "-bind_at_load" > might indeed be the way to go. Maybe somebody could test the result > with this? Doesn't help. Even the advice about using -bind_at_load remains there when this option is used. I see another part of the ld m

Re: [Fink-devel] Lesstif/nedit/... problems - possibly cause

2002-01-25 Thread Jeff Whitaker
> > > >However, the static link editor always > >produces the same linking as the dynamic linker as long as > >none of the dynamic shared libraries define the same sym- > >bol. Different linking can occur only when there is more > >than one definition of a symbol and the library modules >

Re: [Fink-devel] Lesstif/nedit/... problems - possibly cause

2002-01-25 Thread Max Horn
At 10:21 Uhr +0100 25.01.2002, Martin Costabel wrote: >Max, > >This information is also in the lesstif FAQ at /sw/LessTif/FAQ and >/sw/LessTif/doc/FAQ.html. I remember mentioning this two days ago in the >"XFree86 version and grace" thread on fink-users. The FAQ even mentions >it in the same way w

Re: [Fink-devel] Lesstif/nedit/... problems - possibly cause

2002-01-25 Thread Martin Costabel
Max, This information is also in the lesstif FAQ at /sw/LessTif/FAQ and /sw/LessTif/doc/FAQ.html. I remember mentioning this two days ago in the "XFree86 version and grace" thread on fink-users. The FAQ even mentions it in the same way we are seeing it, with "DropSiteManager". The problem seems

Re: [Fink-devel] Lesstif/nedit/... problems - possibly cause

2002-01-24 Thread Jeff Whitaker
Max: I saw this too. The problem is, we are linking the libs in the right order. It looks like the linker is not respecting that. -Jeff On Fri, 25 Jan 2002, Max Horn wrote: > I searched the net and found this: > > http://www.perchine.com/dyp/x/motif-faq/part9/faq-doc-24.html > > To quote it:

[Fink-devel] Lesstif/nedit/... problems - possibly cause

2002-01-24 Thread Max Horn
I searched the net and found this: http://www.perchine.com/dyp/x/motif-faq/part9/faq-doc-24.html To quote it: >269) Why do I get "Error: attempt to add non-widget child "dsm" to parent"? > >[Last modified: May 95] > >Answer: You're linking your libraries in the wrong order. You must link -lXm