RE: non-widget child "DropSiteManager" error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )

RE: non-widget child "DropSiteManager" error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )

[Atwood, Robert C]

Well, I believe that something like 'You have to directly edit the
<package>.sh script in order to alter the configuration options, which
are passed to the configure script, such as --enable-debug or
--enable/disable-static' would/should be included there. 

Also since ./configure --help ususally provides information about what
options/environment variables are available or used, and the Cygwin
build script makes this step essentially opaque to the user, I feel that
the responsibility for providing this also gets transferred to the
Cygwin build script. Perhaps the 'help' function would also simply call
the configure script for the package and echo back the help options from
it.  I will see if I can do this at least  before sending a patch to the
address you mention. 

I though you meant 'what does "documentation" mean', like very
sarcastic! 

Method 2 link:
I see what you mean, and I did glance at this before -- but not in great
detail because it is mostly about how to create the package but not much
about how to use the package once it is created.
In the 'canned instructions' it only mentions using the 'all' option ,
it does not mention the sub-options such as prep, build,conf ... only
because Harold mentioned it did I get the idea that these other options
exist.  (then trying to read the script )




-----Original Message-----
From: cygwin-xfree-owner@cygwin.com
[mailto:cygwin-xfree-owner@cygwin.com] On Behalf Of Brian Ford
Sent: 21 January 2004 16:09
To: cygwin-xfree@cygwin.com
Subject: RE: non-widget child "DropSiteManager" error (WAS: RE: Grace
(xmgrace) 5.1.12-1 ... )


On Wed, 21 Jan 2004, Atwood, Robert C wrote:
> Brian Ford wrote:
> >Robert C Atwood wrote:
> >> Is this documented somewhere?
> >>
> >What does *this* mean :^D?
> >
> :-C
> *fulmination removed*
>
> Umm ... is there a place where it says 'Here is how you build a Cygwin

> package from the source archive distributed via Cygwin setup. 1. 
> Unpack the archive 2. There will be a script called 
> <package><release>.sh  3. Run this script with (one of) the followign 
> arguments: prep , build, all, (etc.) 4. Here is what each of the 
> arguments do. ... 5. this produces an archive, unpack this as 
> follows.... 6. anything else.
>
Sorry.  If you look at the context from your previous message, it really
was not clear whether this refered to
--[enable|disable]-[static|shared], how to build a DLL with libtool,
etc. In fact, the this you explained above was not even on my guess list
:).

Is think this is the closest this to what you are looking for:

http://cygwin.com/setup.html#package_contents

Look under "Method 2".

> Also I believe the following addition to the script would probably 
> save some people (like me) much headache ... suitably filled in where 
> blank, I don't quite get what all the different options are for.
>
I agree.  PTC.  Please send them to cygwin-apps at cygwin dot com.
Although, don't get your hopes up.  There has been another very useful
patch to this script pending for a long time now, and it is not clear
why it has not been accepted.

I'm not sure who is in charge of the generic build script.  Maybe that
is the problem.

[snip]

I have my new machine set up now, so I'll try to take a stab at
compiling it myself today.  I'll let you know how I make out.  Thanks
for being patient.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

Re: non-widget child "DropSiteManager" error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )

[Christopher Faylor]

On Wed, Jan 21, 2004 at 04:35:30PM -0000, Atwood, Robert C wrote:
>Well, I believe that something like 'You have to directly edit the
><package>.sh script in order to alter the configuration options, which
>are passed to the configure script, such as --enable-debug or
>--enable/disable-static' would/should be included there.

If you have opinions on the subject then you'd be well-advised to voice
them in the proper forum, to which Brian has already pointed you.  This
certainly isn't an issue for cygwin-xfree.

RE: non-widget child "DropSiteManager" error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )

[Brian Ford]

On Wed, 21 Jan 2004, Brian Ford wrote:

> I have my new machine set up now, so I'll try to take a stab at compiling
> it myself today.  I'll let you know how I make out.  Thanks for being
> patient.
>

It compiled for me (including DLLs) almost out of the box.  I did make the
following change to lesstif-0.93.91-6.sh.  I am not sure that the change
was required, because I did not try without it.  But, it "felt" like a
better idea to me :^D.

In the prep rule, remove all the autotool stuff between:
  touch INSTALL && \
and
  rm -f INSTALL )

replacing it simply with:
  autoreconf --install --force && \

so it reads:
prep() {
  (cd ${topdir} && \
  tar xv${opt_decomp}f ${src_orig_pkg} ; \
  cd ${topdir} && \
  patch -p0 < ${src_patch}
  && mkdirs ) && \
  (cd ${srcdir} && \
  touch INSTALL && \
  autoreconf --install --force && \
  rm -f INSTALL )
}

To do a debug build, just look at the target all:
  all) prep && conf && build && install && \
     strip && pkg && spkg && finish ; \
          STATUS=$? ;;

and do everything but the strip step.

Let me know if this doesn't work for you.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

RE: non-widget child "DropSiteManager" error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )

[Igor Pechtchanski]

On Wed, 21 Jan 2004, Brian Ford wrote:

> On Wed, 21 Jan 2004, Atwood, Robert C wrote:
>
> [snip]
> > Also I believe the following addition to the script would probably save
> > some people (like me) much headache ... suitably filled in where blank,
> > I don't quite get what all the different options are for.
>
> I agree.  PTC.  Please send them to cygwin-apps at cygwin dot com.
> Although, don't get your hopes up.  There has been another very useful
> patch to this script pending for a long time now, and it is not clear why
> it has not been accepted.
>
> I'm not sure who is in charge of the generic build script.  Maybe that is
> the problem.

Technically, I think everyone believes that Chuck Wilson is officially in
charge of that.  However, he did mention recently that he'd be too busy to
do anything with the script for a while...  So, here's a question for the
powers-that-be of Cygwin-apps: who can approve patches to the
generic-build-script (and the generic-readme)?  Who can commit?  Or should
we just wait for Chuck?
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

RE: non-widget child "DropSiteManager" error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )

[Brian Ford]

On Wed, 21 Jan 2004, Atwood, Robert C wrote:
> Brian Ford wrote:
> >Robert C Atwood wrote:
> >> Is this documented somewhere?
> >>
> >What does *this* mean :^D?
> >
> :-C
> *fulmination removed*
>
> Umm ... is there a place where it says 'Here is how you build a Cygwin
> package from the source archive distributed via Cygwin setup. 1. Unpack
> the archive 2. There will be a script called <package><release>.sh  3.
> Run this script with (one of) the followign arguments: prep , build,
> all, (etc.) 4. Here is what each of the arguments do. ... 5. this
> produces an archive, unpack this as follows.... 6. anything else.
>
Sorry.  If you look at the context from your previous message, it really
was not clear whether this refered to
--[enable|disable]-[static|shared], how to build a DLL with libtool, etc.
In fact, the this you explained above was not even on my guess list :).

Is think this is the closest this to what you are looking for:

http://cygwin.com/setup.html#package_contents

Look under "Method 2".

> Also I believe the following addition to the script would probably save
> some people (like me) much headache ... suitably filled in where blank,
> I don't quite get what all the different options are for.
>
I agree.  PTC.  Please send them to cygwin-apps at cygwin dot com.
Although, don't get your hopes up.  There has been another very useful
patch to this script pending for a long time now, and it is not clear why
it has not been accepted.

I'm not sure who is in charge of the generic build script.  Maybe that is
the problem.

[snip]

I have my new machine set up now, so I'll try to take a stab at compiling
it myself today.  I'll let you know how I make out.  Thanks for being
patient.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

RE: non-widget child "DropSiteManager" error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )

[Atwood, Robert C]

To ask a simple question:

When are the dll supposed to get created during the build/install
process?



*duh* okay --  I did not look in the *-announce archives. But I did see
this same text in the lesstif.README of the distribution. Maybe I did
not understand it... I interpret these points ("Port notes")  as
referring to things that Harold has already done for this version, not
something that the user has to do. Is this incorrect? It seemed to work
for Harold anyways, he has generated a package. 

>Why are you trying to build it yourself?
Obviously I must be a masochist with a need to waste time. :-D

>See the following reference for some details:
>http://sources.redhat.com/ml/cygwin-xfree/2003-10/msg00401.html
Okay, that explains something.

>Did you make sure that this step from Harold's lesstif announcement 
>worked?

No, in fact I am sorry but I still don't understand what you are asking.
I do have the up-to-date build tools, as of that day that Harold posted
0.93.91-6 , unless I am completely missign something. There were no
complaints from the confiure/build script though. dlltool is installed,
the command for creating dll seems to be located in ltmain.sh , I don't
see any messages saying that it failed. I just don't get dll's

How should one 'check if (all these steps) worked'? I would expect it to
fail with certain messages if it didn't work. 

Is there any other step *necessary* besides:

1 change the script to have --enable-debug --enable-shared
--disable-static flags

2 ./lesstif-0.93.91-6.sh prep
3 ./lesstif-0.93.91-6.sh conf
4 ./lesstif-0.93.91-6.sh build
5 ./lesstif-0.93.91-6.sh install

6 then using the result in the .install directory?

 I used 
./lesstif-0.93.91-6.sh all 

the first time I tried it, with identical results (except I had to
untarbz the results, and debug was not enabled) I have not looked into
creating a setup.ini, is this where the .dll get created?

Or to ask a very uncomplicated question:

When are the dll supposed to get created in the build/install process?

Given this information I may be able to see why it is not happening on
my system. I am going to move this question to the top of this message
so maybe people will see it instead of having to read down to this
point!

Thanks, 
Robert

-----Original Message-----
From: cygwin-xfree-owner@cygwin.com
[mailto:cygwin-xfree-owner@cygwin.com] On Behalf Of David Fraser
Sent: 21 January 2004 12:56
To: cygwin-xfree@cygwin.com
Subject: Re: non-widget child "DropSiteManager" error (WAS: RE: Grace
(xmgrace) 5.1.12-1 ... )


Atwood, Robert C wrote:

>Can you tell me the date/title of the announcement? I think it was a 
>while before I started reading this list, and Harold is so active that 
>I so far could not find it in the archives.
>
>  
>
Updated: lesstif-0.93.91-6
01/16/2004 07:13 AM

>**********************************************
>
>Did you make sure that this step from Harold's lesstif announcement 
>worked?
>
>2) Make the build script run aclocal, autoconf, and automake, and make 
>the mkpatch step exclude files generated by these programs.  This makes

>the package patch readable and useful.
>
>I think you might need to include libtool in that list.  Make sure all 
>of the afore mentioned tools are up to date, and then try:
>
>autoreconf --install --force
>
>  
>

Re: non-widget child "DropSiteManager" error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )

[David Fraser]

Atwood, Robert C wrote:

>Can you tell me the date/title of the announcement? I think it was a
>while before I started reading this list, and Harold is so active that I
>so far could not find it in the archives.
>
>  
>
Updated: lesstif-0.93.91-6
01/16/2004 07:13 AM

>**********************************************
>
>Did you make sure that this step from Harold's lesstif announcement
>worked?
>
>2) Make the build script run aclocal, autoconf, and automake, and make
>the mkpatch step exclude files generated by these programs.  This makes
>the package patch readable and useful.
>
>I think you might need to include libtool in that list.  Make sure all
>of the afore mentioned tools are up to date, and then try:
>
>autoreconf --install --force
>
>  
>

RE: non-widget child "DropSiteManager" error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )

[Atwood, Robert C]

Can you tell me the date/title of the announcement? I think it was a
while before I started reading this list, and Harold is so active that I
so far could not find it in the archives.


**********************************************

Did you make sure that this step from Harold's lesstif announcement
worked?

2) Make the build script run aclocal, autoconf, and automake, and make
the mkpatch step exclude files generated by these programs.  This makes
the package patch readable and useful.

I think you might need to include libtool in that list.  Make sure all
of the afore mentioned tools are up to date, and then try:

autoreconf --install --force

RE: non-widget child "DropSiteManager" error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )

[Atwood, Robert C]

> Is this documented somewhere?
>
What does *this* mean :^D?
 
:-C
*fulmination removed*

Umm ... is there a place where it says 'Here is how you build a Cygwin
package from the source archive distributed via Cygwin setup. 1. Unpack
the archive 2. There will be a script called <package><release>.sh  3.
Run this script with (one of) the followign arguments: prep , build,
all, (etc.) 4. Here is what each of the arguments do. ... 5. this
produces an archive, unpack this as follows.... 6. anything else. 

Also I believe the following addition to the script would probably save
some people (like me) much headache ... suitably filled in where blank,
I don't quite get what all the different options are for.

# print a brief help message
help(){
   echo "Cygwin installation script $0 "
echo "<special instructions for this particular package if necessary?>"
echo " Options: "
echo "   help: Print this message. "
echo "   prep: Prepare the Cygwin patched version of the source. "
echo "   mkdirs: Make the directory heirarchy needed. ?... "
echo "   conf:   Run the configure script with suggested options for
Cygwin "
echo "   build:  Compile the package from the source code "
echo "   check:   "
echo "   clean:  Remove files produced by configuring and building "
echo "   install: "
echo "   strip:  Remove extra symbols from the compiled package "
echo "   package: "
echo "   pkg: "
echo "   mkpatch: "
echo "   src-package: "
echo "   spkg: "
echo "   finish: "
echo "   sigfile: "
echo "   checksig: "
echo "   all:    "

}
# end
case $1 in
  help) help; STATUS=$?;;
  prep)	prep ; STATUS=$? ;;
  mkdirs)	mkdirs; STATUS=$? ;;
  conf)		conf ; STATUS=$? ;;
  build)	build ; STATUS=$? ;;
  check)	check ; STATUS=$? ;;
  clean)	clean ; STATUS=$? ;;
  install)	install ; STATUS=$? ;;
  strip)	strip ; STATUS=$? ;;
  package)	pkg ; STATUS=$? ;;
  pkg)	pkg ; STATUS=$? ;;
  mkpatch)	mkpatch ; STATUS=$? ;;
  src-package)	spkg ; STATUS=$? ;;
  spkg)		name=$0 text="SCRIPT" sigfile; spkg ; STATUS=$? ;;
  finish)	finish ; STATUS=$? ;;
  sigfile)	sigfile ; STATUS=$? ;;
  checksig)	checksig ; STATUS=$? ;;
  all) prep && conf && build && install && \
     strip && pkg && name=$0 text="SCRIPT" sigfile && spkg && \
     finish && echo All finished! ; \
	  STATUS=$? ;;
  *) echo "Error: bad arguments" ; exit 1 ;;
esac

RE: non-widget child "DropSiteManager" error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )

[Brian Ford]

On Tue, 20 Jan 2004, Atwood, Robert C wrote:

> As far as I can tell, it not only build static .a library files, but did
> not create any shared .dll files. Is there another step needed to do
> this? I will try to comprehend some parts of the script and see if I can
> figure how to create the dll's or why I did not get them in the first
> place.
>
Did you make sure that this step from Harold's lesstif announcement
worked?

2) Make the build script run aclocal, autoconf, and automake, and make
the mkpatch step exclude files generated by these programs.  This
makes the package patch readable and useful.

I think you might need to include libtool in that list.  Make sure all of
the afore mentioned tools are up to date, and then try:

autoreconf --install --force

> At first I tried buildign the lesstif by manually runing ./configure and
> make but this did not work.
>
Probably due to the above.

> This is a list all the files called Xm that got installed :
> </usr/X11R6>$find . -name '*Xm\.*'
> ./lib/libXm.la
> ./lib/libXm.a
> ./include/Xm/Xm.h
> Thanks again
> Robert
>
Yeah, there should definately be more.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

RE: non-widget child "DropSiteManager" error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )

[Brian Ford]

On Tue, 20 Jan 2004, Atwood, Robert C wrote:

> >I believe this is a static lesstif lib.  And, AFAIK, a static lesstif
> lib will not work now that Xt is a DLL.  I don't know why
> >it is still in the package.  I would think that lesstif-0.93.91-6.sh
> should be passing --disable-static to configure and that
> >would keep this from being built/installed.
>
> It has both --enable-static and --enable-shared in there, does one
> override the other? I do not get the dll.
>
No.  They are supposed to be independent.

> I am trying again with the --enable-static removed ; or do you actually
> have to specify --disable-static?
>
It depends on how this package is defaulted.  I don't remember and am
still in the process of migrating to a new PC, so I don't have easy access
to the source.  That is also the reason for all the vague replies.

> Is this documented somewhere?
>
What does *this* mean :^D?

> However, I don't see why one library can't be static and the other
> shared, doesn't it just look for the needed symbol at run-time?  --  I
> am willing to take your word for it though.
>
No.  Windows requires all symbols to be defined at link time.  Xt/Xm/Xaw3d
all depend on more *nix like behavior and expect to override symbols at
run time.  The hack used to fix this hooks into DLL initialization.  Thus,
no static lib support.  There are probably other reasons as well.

Search the achives for VendorShell if you want more detail.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

RE: non-widget child "DropSiteManager" error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )

[Atwood, Robert C]

>I believe this is a static lesstif lib.  And, AFAIK, a static lesstif
lib will not work now that Xt is a DLL.  I don't know why 
>it is still in the package.  I would think that lesstif-0.93.91-6.sh
should be passing --disable-static to configure and that 
>would keep this from being built/installed.

It has both --enable-static and --enable-shared in there, does one
override the other? I do not get the dll. 

I am trying again with the --enable-static removed ; or do you actually
have to specify --disable-static?

Is this documented somewhere?

However, I don't see why one library can't be static and the other
shared, doesn't it just look for the needed symbol at run-time?  --  I
am willing to take your word for it though.


 

RE: non-widget child "DropSiteManager" error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )

[Atwood, Robert C]

As far as I can tell, it not only build static .a library files, but did
not create any shared .dll files. Is there another step needed to do
this? I will try to comprehend some parts of the script and see if I can
figure how to create the dll's or why I did not get them in the first
place.

At first I tried buildign the lesstif by manually runing ./configure and
make but this did not work.

This is a list all the files called Xm that got installed :
</usr/X11R6>$find . -name '*Xm\.*'
./lib/libXm.la
./lib/libXm.a
./include/Xm/Xm.h
Thanks again
Robert
-----Original Message-----
From: cygwin-xfree-owner@cygwin.com
[mailto:cygwin-xfree-owner@cygwin.com] On Behalf Of Brian Ford
Sent: 20 January 2004 18:54
To: cygwin-xfree@cygwin.com
Subject: RE: non-widget child "DropSiteManager" error (WAS: RE: Grace
(xmgrace) 5.1.12-1 ... )


On Tue, 20 Jan 2004, Atwood, Robert C wrote:

> What I did: Building lesstif -- just using the provided script (for 
> now, without even trying debugging) Sorry this is my first exposure to

> the cygwin building scripts, I am not sure what it did with my 
> config.log, but it is the script included in 0.93.91-6, using 
> <package>.sh all
>
The whole build is done in .build.

>             Installing lesstif -- untarred the resulting archive into 
> the / location
>
>             Configuring grace -- grace-5.1.12-1.sh prep
>                                  export X_EXTRA_LIBS="-lXft 
> -lfontconfig -lXrender"
>                                  cd grace-5.1.12
>                                  ./configure 
> --with-motif-library-/usr/X11R6/lib/libXm.a  [--enable-debug] (tried
> with/without)
>
I believe this is a static lesstif lib.  And, AFAIK, a static lesstif
lib will not work now that Xt is a DLL.  I don't know why it is still in
the package.  I would think that lesstif-0.93.91-6.sh should be passing
--disable-static to configure and that would keep this from being
built/installed.

Do not use that lib.  Move it out of the way.  You should be linking
with libXm.dll.a, although -lXm should just do that.

>                                  make
>                                  make tests
>
> The errors occurred here. I tried some other ways of getting the 
> librarys included (before I settled on this way) with identical 
> results. With the lesstif installed from the binary package via setup,

> the tests work (but crash, as mentioned, with a seg fault if an axis 
> dialog is
> opened) In this case no graphs open, only the error message
(non-widget
> etc.) in the parent terminal window.
>
That is because you are linking with the broken static lib.

> I am not sure why X_EXTRA_LIBS were needed when they were not needed 
> when I compiled grace using the lesstif that was installed from the 
> binary package. This was very confusing. As far as I can tell, these 
> libraries are not part of lesstif,(are they?)
>
Libtool may have taken care of this for you, although I don't know why
it isn't now.  Look in libXm.la.

See the following reference for some details:

http://sources.redhat.com/ml/cygwin-xfree/2003-10/msg00401.html

> Final linking line:
>
> gcc -O2 -mcpu=pentiumpro -fno-common -Wall -pedantic -Wpointer-arith 
> -Wnested-externs -I.. -I. -I../T1lib/t1lib -I../Xbae 
> -I/usr/X11R6/include main.o plotone.o files.o ssdata.o utils.o 
> drawticks.o nonlfit.o lmdif.o as274c.o fit.o fourier.o graphs.o 
> graphutils.o setutils.o regionutils.o objutils.o computils.o 
> defaults.o params.o draw.o dlmodule.o pars.o missing.o  iofilters.o 
> dates.o t1fonts.o device.o dummydrv.o mfdrv.o mifdrv.o psdrv.o 
> pdfdrv.o svgdrv.o gd.o rstdrv.o mathstuff.o Tab.o motifutils.o 
> compwin.o comwin.o eblockwin.o editpwin.o events.o featext.o 
> fileswin.o plotwin.o graphappwin.o helpwin.o hotwin.o locatewin.o 
> miscwin.o monwin.o nonlwin.o printwin.o ptswin.o regionwin.o setwin.o 
> strwin.o setappwin.o tickwin.o worldwin.o fontwin.o xutil.o x11drv.o
xmgrace.o -o xmgrace.exe
> -L/usr/X11R6/lib   ../Xbae/Xbae/libXbae.a /usr/X11R6/lib/libXm.a -lXpm
>
Yep.  Don't use that one.

> -lXp -lXmu -lXt -lXext -lX11  -lSM -lICE -lXft  -lfontconfig -lXrender
> ../cephes/libcephes.a   ../T1lib/libt1.a  -ltiff -ljpeg -lpng -lz -lm
>

You will still need the debug build to find the dialog problem.  Look in
the <package>.sh script to figure out how to do one manually.  It isn't
that hard to dig through.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

RE: non-widget child "DropSiteManager" error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )

[Brian Ford]

On Tue, 20 Jan 2004, Atwood, Robert C wrote:

> What I did: Building lesstif -- just using the provided script (for now,
> without even trying debugging)
> Sorry this is my first exposure to the cygwin building scripts, I am not
> sure what it did with my config.log, but it is the script included in
> 0.93.91-6, using <package>.sh all
>
The whole build is done in .build.

>             Installing lesstif -- untarred the resulting archive into
> the / location
>
>             Configuring grace -- grace-5.1.12-1.sh prep
>                                  export X_EXTRA_LIBS="-lXft -lfontconfig
> -lXrender"
>                                  cd grace-5.1.12
>                                  ./configure
> --with-motif-library-/usr/X11R6/lib/libXm.a  [--enable-debug] (tried
> with/without)
>
I believe this is a static lesstif lib.  And, AFAIK, a static lesstif lib
will not work now that Xt is a DLL.  I don't know why it is still in the
package.  I would think that lesstif-0.93.91-6.sh should be passing
--disable-static to configure and that would keep this from being
built/installed.

Do not use that lib.  Move it out of the way.  You should be linking with
libXm.dll.a, although -lXm should just do that.

>                                  make
>                                  make tests
>
> The errors occurred here. I tried some other ways of getting the
> librarys included (before I settled on this way) with identical results.
> With the lesstif installed from the binary package via setup, the tests
> work (but crash, as mentioned, with a seg fault if an axis dialog is
> opened) In this case no graphs open, only the error message (non-widget
> etc.) in the parent terminal window.
>
That is because you are linking with the broken static lib.

> I am not sure why X_EXTRA_LIBS were needed when they were not needed
> when I compiled grace using the lesstif that was installed from the
> binary package. This was very confusing. As far as I can tell, these
> libraries are not part of lesstif,(are they?)
>
Libtool may have taken care of this for you, although I don't know why it
isn't now.  Look in libXm.la.

See the following reference for some details:

http://sources.redhat.com/ml/cygwin-xfree/2003-10/msg00401.html

> Final linking line:
>
> gcc -O2 -mcpu=pentiumpro -fno-common -Wall -pedantic -Wpointer-arith
> -Wnested-externs -I.. -I. -I../T1lib/t1lib -I../Xbae
> -I/usr/X11R6/include main.o plotone.o files.o ssdata.o utils.o
> drawticks.o nonlfit.o lmdif.o as274c.o fit.o fourier.o graphs.o
> graphutils.o setutils.o regionutils.o objutils.o computils.o defaults.o
> params.o draw.o dlmodule.o pars.o missing.o  iofilters.o dates.o
> t1fonts.o device.o dummydrv.o mfdrv.o mifdrv.o psdrv.o pdfdrv.o svgdrv.o
> gd.o rstdrv.o mathstuff.o Tab.o motifutils.o compwin.o comwin.o
> eblockwin.o editpwin.o events.o featext.o fileswin.o plotwin.o
> graphappwin.o helpwin.o hotwin.o locatewin.o miscwin.o monwin.o
> nonlwin.o printwin.o ptswin.o regionwin.o setwin.o strwin.o setappwin.o
> tickwin.o worldwin.o fontwin.o xutil.o x11drv.o xmgrace.o -o xmgrace.exe
> -L/usr/X11R6/lib   ../Xbae/Xbae/libXbae.a /usr/X11R6/lib/libXm.a -lXpm
>
Yep.  Don't use that one.

> -lXp -lXmu -lXt -lXext -lX11  -lSM -lICE -lXft  -lfontconfig -lXrender
> ../cephes/libcephes.a   ../T1lib/libt1.a  -ltiff -ljpeg -lpng -lz -lm
>

You will still need the debug build to find the dialog problem.  Look in
the <package>.sh script to figure out how to do one manually.  It isn't
that hard to dig through.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

RE: non-widget child "DropSiteManager" error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )

[Atwood, Robert C]

No huge rush, I am getting the graphing I want done using Grace on a
linux box, no reason other than a bit of convenience to do it on a
window/cygwin installation.. 

What I did: Building lesstif -- just using the provided script (for now,
without even trying debugging)
Sorry this is my first exposure to the cygwin building scripts, I am not
sure what it did with my config.log, but it is the script included in
0.93.91-6, using <package>.sh all 
            Installing lesstif -- untarred the resulting archive into
the / location

            Configuring grace -- grace-5.1.12-1.sh prep
                                 export X_EXTRA_LIBS="-lXft -lfontconfig
-lXrender" 
                                 cd grace-5.1.12
                                 ./configure
--with-motif-library-/usr/X11R6/lib/libXm.a  [--enable-debug] (tried
with/without)
                                 make
                                 make tests

The errors occurred here. I tried some other ways of getting the
librarys included (before I settled on this way) with identical results.
With the lesstif installed from the binary package via setup, the tests
work (but crash, as mentioned, with a seg fault if an axis dialog is
opened) In this case no graphs open, only the error message (non-widget
etc.) in the parent terminal window.


I am not sure why X_EXTRA_LIBS were needed when they were not needed
when I compiled grace using the lesstif that was installed from the
binary package. This was very confusing. As far as I can tell, these
libraries are not part of lesstif,(are they?) 



Final linking line:


gcc -O2 -mcpu=pentiumpro -fno-common -Wall -pedantic -Wpointer-arith
-Wnested-externs -I.. -I. -I../T1lib/t1lib -I../Xbae
-I/usr/X11R6/include main.o plotone.o files.o ssdata.o utils.o
drawticks.o nonlfit.o lmdif.o as274c.o fit.o fourier.o graphs.o
graphutils.o setutils.o regionutils.o objutils.o computils.o defaults.o
params.o draw.o dlmodule.o pars.o missing.o  iofilters.o dates.o
t1fonts.o device.o dummydrv.o mfdrv.o mifdrv.o psdrv.o pdfdrv.o svgdrv.o
gd.o rstdrv.o mathstuff.o Tab.o motifutils.o compwin.o comwin.o
eblockwin.o editpwin.o events.o featext.o fileswin.o plotwin.o
graphappwin.o helpwin.o hotwin.o locatewin.o miscwin.o monwin.o
nonlwin.o printwin.o ptswin.o regionwin.o setwin.o strwin.o setappwin.o
tickwin.o worldwin.o fontwin.o xutil.o x11drv.o xmgrace.o -o xmgrace.exe
-L/usr/X11R6/lib   ../Xbae/Xbae/libXbae.a /usr/X11R6/lib/libXm.a -lXpm
-lXp -lXmu -lXt -lXext -lX11  -lSM -lICE -lXft  -lfontconfig -lXrender
../cephes/libcephes.a   ../T1lib/libt1.a  -ltiff -ljpeg -lpng -lz -lm  

Thanks again.
Dr. Robert Atwood
Research Associate
Dept. of Materials
Imperial College London
London, UK



-----Original Message-----
From: cygwin-xfree-owner@cygwin.com
[mailto:cygwin-xfree-owner@cygwin.com] On Behalf Of Brian Ford
Sent: 20 January 2004 17:24
To: cygwin-xfree@cygwin.com
Subject: RE: non-widget child "DropSiteManager" error (WAS: RE: Grace
(xmgrace) 5.1.12-1 ... )


On Tue, 20 Jan 2004, Atwood, Robert C wrote:

> Dear Brian and other list people:
>
> Why am I trying to build it myself?
>
> Because the distributed package (0-93-91-5)  seems to cause another 
> problem, even the version that Harold Hunt patched (0.93.91-6) using 
> Danny Backx's fix for the bug I encounterd a few months ago, and have 
> no idea why it still crashes. I cannot find out in any more detail 
> unless I run with a debug-compiled version.
>
> Please see the archived thread on 'Grace (xmgrace) 5.1.12-1 ... ' for 
> much greater detail on this (including backtraces, etc)
>
Ok.  I'm way behind on my list traffic because of the flu, holidays, and
a funeral.  I have briefly scanned the thread you refer to now.

> Is there another way to get a debug-compiled version other than 
> building it myself?
>
Not that I know of.

> Harold's test-version of 0.93.94 seems to have this problem 
> (non-widget
> etc.) (if it really is from lesstif) and he says it causes problems
with
> nedit as well, so it is not a true release. But I am building a
> 0.93.91-6 without changes (at first) just to find out exactly where
the
> crash is coming from, but get this (different) problem.
>
It is from lesstif.

Could you post your exact link line?  I haven't had time to try the test
version yet.

> I certainly realize that a 'properly built' lesstif is what I want, in

> what way is my version not 'properly built'?  That is essentially what

> I was asking in the first place! However I followed Harold's 
> directions exactly without trying to patch it or even debug it (at 
> first) and I have this problem.
>
> How do I distinguish whether it is not 'properly built' or not 
> 'properly updated'? Which is the problem?
>
I don't know.  Properly linked might also be the problem, hence the
request above.  What did you pass to configure?

Did you try putting the extra freetype libs in LIBS?

> Can you provide details on what constitutes a 'properly updated' 
> lesstif? I got the source from 0.93.91-6 (one line different from
> 0.93.91-5)
>
That should be fine.

> Can you build xmgrace from source and then get the axis properties 
> dialog box (double click an axis) to open without crashing? (Note the 
> release 5-1-12-1 package binaries are compiled with STATIC libraries 
> from an earlier version of lesstif and do not crash.)
>
Maybe, but it'll be a while.

> > Update: by adding absolute paths to the missing libraries, I can get

> > it to compile,but now I get
> >
This is probably bad.  By "the libraries", you mean the dll's, or the
import libs?  You want the latter, I believe.

Sorry to be so sparse with the reply.  I'm really backed up right now.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

RE: non-widget child "DropSiteManager" error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )

[Brian Ford]

On Tue, 20 Jan 2004, Atwood, Robert C wrote:

> Dear Brian and other list people:
>
> Why am I trying to build it myself?
>
> Because the distributed package (0-93-91-5)  seems to cause another
> problem, even the version that Harold Hunt patched (0.93.91-6) using
> Danny Backx's fix for the bug I encounterd a few months ago, and have no
> idea why it still crashes. I cannot find out in any more detail unless I
> run with a debug-compiled version.
>
> Please see the archived thread on 'Grace (xmgrace) 5.1.12-1 ... ' for
> much greater detail on this (including backtraces, etc)
>
Ok.  I'm way behind on my list traffic because of the flu, holidays, and a
funeral.  I have briefly scanned the thread you refer to now.

> Is there another way to get a debug-compiled version other than building
> it myself?
>
Not that I know of.

> Harold's test-version of 0.93.94 seems to have this problem (non-widget
> etc.) (if it really is from lesstif) and he says it causes problems with
> nedit as well, so it is not a true release. But I am building a
> 0.93.91-6 without changes (at first) just to find out exactly where the
> crash is coming from, but get this (different) problem.
>
It is from lesstif.

Could you post your exact link line?  I haven't had time to try the test
version yet.

> I certainly realize that a 'properly built' lesstif is what I want, in
> what way is my version not 'properly built'?  That is essentially what I
> was asking in the first place! However I followed Harold's directions
> exactly without trying to patch it or even debug it (at first) and I
> have this problem.
>
> How do I distinguish whether it is not 'properly built' or not 'properly
> updated'? Which is the problem?
>
I don't know.  Properly linked might also be the problem, hence the
request above.  What did you pass to configure?

Did you try putting the extra freetype libs in LIBS?

> Can you provide details on what constitutes a 'properly updated'
> lesstif? I got the source from 0.93.91-6 (one line different from
> 0.93.91-5)
>
That should be fine.

> Can you build xmgrace from source and then get the axis properties
> dialog box (double click an axis) to open without crashing? (Note the
> release 5-1-12-1 package binaries are compiled with STATIC libraries
> from an earlier version of lesstif and do not crash.)
>
Maybe, but it'll be a while.

> > Update: by adding absolute paths to the missing libraries, I can get
> > it to compile,but now I get
> >
This is probably bad.  By "the libraries", you mean the dll's, or the
import libs?  You want the latter, I believe.

Sorry to be so sparse with the reply.  I'm really backed up right now.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

RE: non-widget child "DropSiteManager" error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )

[Atwood, Robert C]

Dear Brian and other list people:

Why am I trying to build it myself?

Because the distributed package (0-93-91-5)  seems to cause another
problem, even the version that Harold Hunt patched (0.93.91-6) using
Danny Backx's fix for the bug I encounterd a few months ago, and have no
idea why it still crashes. I cannot find out in any more detail unless I
run with a debug-compiled version. 

Is there another way to get a debug-compiled version other than building
it myself?

Harold's test-version of 0.93.94 seems to have this problem (non-widget
etc.) (if it really is from lesstif) and he says it causes problems with
nedit as well, so it is not a true release. But I am building a
0.93.91-6 without changes (at first) just to find out exactly where the
crash is coming from, but get this (different) problem.  

Please see the archived thread on 'Grace (xmgrace) 5.1.12-1 ... ' for
much greater detail on this (including backtraces, etc)

I certainly realize that a 'properly built' lesstif is what I want, in
what way is my version not 'properly built'? That is essentially what I
was asking in the first place! However I followed Harold's directions
exactly without trying to patch it or even debug it (at first) and I
have this problem. 

How do I distinguish whether it is not 'properly built' or not 'properly
updated'? Which is the problem? 

Can you provide details on what constitutes a 'properly updated'
lesstif? I got the source from 0.93.91-6 (one line different from
0.93.91-5) 

Can you build xmgrace from source and then get the axis properties
dialog box (double click an axis) to open without crashing? (Note the
release 5-1-12-1 package binaries are compiled with STATIC libraries
from an earlier version of lesstif and do not crash.)

Thanks for your help
Robert


-----Original Message-----
From: cygwin-xfree-owner@cygwin.com
[mailto:cygwin-xfree-owner@cygwin.com] On Behalf Of Brian Ford
Sent: 19 January 2004 22:45
To: cygwin-xfree@cygwin.com
Subject: Re: non-widget child "DropSiteManager" error (WAS: RE: Grace
(xmgrace) 5.1.12-1 ... )


On Mon, 19 Jan 2004, Atwood, Robert C wrote:

> Update: by adding absolute paths to the missing libraries, I can get 
> it to compile,but now I get
>
> Error: attempt to add non-widget child "DropSiteManager" to parent 
> "xmgrace" which supports only widgets
>
> I have scanned the mailing list archive , and notice this problem 
> mentioned a few times with other software, eg DDD,  but I cannot find 
> any resolution to this problem mentioned. Any pointers/ redirections 
> to an example I haven't found yet?
>
Using a properly updated or build lesstif will correct this problem.
Why are you trying to build it yourself?

Re: non-widget child "DropSiteManager" error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )

[Brian Ford]

On Mon, 19 Jan 2004, Atwood, Robert C wrote:

> Update: by adding absolute paths to the missing libraries, I can get it
> to compile,but now I get
>
> Error: attempt to add non-widget child "DropSiteManager" to parent
> "xmgrace" which supports only widgets
>
> I have scanned the mailing list archive , and notice this problem
> mentioned a few times with other software, eg DDD,  but I cannot find
> any resolution to this problem mentioned.
> Any pointers/ redirections to an example I haven't found yet?
>
Using a properly updated or build lesstif will correct this problem.  Why
are you trying to build it yourself?

non-widget child "DropSiteManager" error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )

[Atwood, Robert C]

Update: by adding absolute paths to the missing libraries, I can get it
to compile,but now I get 

Error: attempt to add non-widget child "DropSiteManager" to parent
"xmgrace" which supports only widgets 


I have scanned the mailing list archive , and notice this problem
mentioned a few times with other software, eg DDD,  but I cannot find
any resolution to this problem mentioned. 
Any pointers/ redirections to an example I haven't found yet?

Thanks

Robert



-----Original Message-----
From: cygwin-xfree-owner@cygwin.com
[mailto:cygwin-xfree-owner@cygwin.com] On Behalf Of Atwood, Robert C
Sent: 19 January 2004 11:20
To: cygwin-xfree@cygwin.com
Subject: RE: Grace (xmgrace) 5.1.12-1 graph program -- building under
cygwin -- possibly LessTif bug from 0.93.91 ?


Thanks again Harold -- This is getting to be a steadily decreasing
priority for me so don't rush to solve my problems at the expense of
those interviews. I can easily transfer the data to a Linux box and use
my patched Grace from there to get the tick marks -- at this point the
only reason to pursue this is to learn how, maybe I can even locate the
bug ( with a little help) ... 
I imagine that several other people also know the answers to these
questions as they are getting more general. I have had no problem doing
the same things on a Linux box, so it seems that it is the differences
between Linux (Red Hat 9, Red Hat 8, and Slackware 8.1) and Cygwin that
are messing me up.  

>You need at least the following packages to build grace and lesstif:

>fontconfig
>libfontconfig1
>libfontconfig-devel

>XFree86-prog


>Harold


I have those, but I cannot figure out how to get Configure to pick them
up. That is, I can compile the little test routine (as used by configure
to test the M*tif installation)  from the command line by including all
the -l flags for these libraries directly but grace<version>/configure
always fails because it is not including those flags.  ( I figured this
out since last time I posted here...the libraries were all
there,somewhere, just not referenced by -l flags ) 
-lXft -lfontconfig -lXrender in addition to those mentioned by default

I tried adding them in the environment variable LDFLAGS but that didn't
work either -- possibly they are in the wrong order. The LDFLAGS seems
to get put before the -I flags and before the other libraries. 

Is there some cygwin equvalent of ldconfig or ld.so.conf that I am
missing out here?  Or does the grace-<version>/configure script need
some changes to use a compiled LessTif instead of packaged binaries?
(this is what I will probably try next) 

I have had some confusion in the past about this, on Cygwin certain
libraries getting automatically referenced .. when does a library not
explicitly referenced by a -l flag get automatically referenced? 


--Robert

-----Original Message-----
From: cygwin-xfree-owner@cygwin.com
[mailto:cygwin-xfree-owner@cygwin.com] On Behalf Of Harold L Hunt II
Sent: 16 January 2004 20:41
To: cygwin-xfree@cygwin.com
Subject: Re: Grace (xmgrace) 5.1.12-1 graph program -- building under
cygwin -- possibly LessTif bug from 0.93.91 ?


Robert,

You need at least the following packages to build grace and lesstif:

fontconfig
libfontconfig1
libfontconfig-devel

XFree86-prog


Harold