Re: Building problem

TK Soh <[email protected]> Thu, 27 May 2010 01:10:23 +0000
Newsgroups gmane.editors.nedit.user
Message-ID <[email protected]>
On Wed, May 26, 2010 at 9:27 PM, Bert Wesarg <bert.wesarg-gM/[email protected]> wrote:
> On Fri, May 21, 2010 at 20:52, Bert Wesarg <bert.wesarg-gM/[email protected]> wrote:
>> Maybe I have on the discussion list more luck.
>>
>> Bert
>>
>> On Wed, May 19, 2010 at 03:32, TK Soh <[email protected]> wrote:
>>> On Tue, May 18, 2010 at 9:19 PM, Bert Wesarg <bert.wesarg-gM/[email protected]> wrote:
>>>> Hi,
>>>>
>>>> does anybody has any building problems lately?
>>>>
>>>> I have really a strange problem. After installing Ubuntu 10.04 freshly
>>>> on my notebook, I can't run a self build nedit binary anymore. The
>>>> error message is;
>>>>
>>>> Error: Shell widget nedit has zero width and/or height
>>>>
>>>> The offender is in source/nedit.c:516:
>>>>
>>>>    XtRealizeWidget(TheAppShell);
>>>>
>>>> I have tried to reproduce this with a minimal X application (see
>>>> attached file), which showed the same error, but than suddenly stopped
>>>> to show this error.
>>>>
>>>> Any help would be very appreciated.
>>>
>>> Just curious, are you linking to Lesstif on OM?
>>
>> I could reproduced this error with the appshell.c code without linking
>> to motif. Anyway I have only tested openmotif (self-build 2.3.2, 2.3.3
>> and ubuntu 2.2.3).
>>
>> That looked like this (out from memory):
>>
>> 1. compile appshell.c without motif
>> 2. run appshell
>>  -> Error: Shell widget appShell has zero width and/or height
>> 3. compile appshell.c with motif (i.e. -DWITH_MOTIF and -lXm)
>> 4. run appshell
>>  -> works as expected
>> 5. compile appshell.c without motif
>> 6. run appshell
>>  -> works as expected
>>
>> So I assumed some "memory" from X that remembers some dimensions for
>> this app. This was on the weekend. Yesterday I tried it again and it
>> didn't work anymore. The appshell (w or w/o motif) always worked. Only
>> the self-build nedit does not.
>>
>
> The solution was vary simple: I had -lXm after -lXt in the
> commandline, which must be in-front of it.

You mean you need to put Xm in front to solve the problem? Any guru
out there can share the reason why the order is significant?
-- 
NEdit Discuss mailing list - [email protected]
http://www.nedit.org/mailman/listinfo/discuss