public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Harold L Hunt II <huntharo@msu.edu>
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 ?
Date: Fri, 16 Jan 2004 17:55:00 -0000	[thread overview]
Message-ID: <4008259A.4090306@msu.edu> (raw)
In-Reply-To: <972A5A4D5DCE4B4989643A8BF329AD7E091E22@icex34.cc.ic.ac.uk>

Robert,

I should clarify that when I applied the patch by hand, I did not touch 
the revision tags (didn't really need to).

Here is the difference I applied:

http://cvs.sourceforge.net/viewcvs.py/lesstif/lesstif/lib/Xm/SeparatoG.c?r1=1.24&r2=1.26


Volker said that grace was built with static libs, which is why there is 
no difference from upgrading to the 0.93.91 build (it doesn't use the DLLs).

You build lesstif as follows:

1) cd /usr/src

2) ./lesstif-0.93.94-1.sh prep

3) ./lesstif-0.93.94-1.sh conf > conf.log 2>&1

4) ./lesstif-0.93.94-1.sh build > build.log 2>&1

5) ./lesstif-0.93.94-1.sh install > install.log 2>&1

6) ./lesstif-0.93.94-1.sh strip

7) ./lesstif-0.93.94-1.sh pkg

8) ./lesstif-0.93.94-1.sh spkg

You will then have a new lesstif package that you can install by 
creating a new setup.ini file.  You'll have to ask or search for help on 
that.  You will need some scripts called "upset" to do this.

Harold


  parent reply	other threads:[~2004-01-16 17:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-15 20:19 Atwood, Robert C
2004-01-16  5:19 ` Harold L Hunt II
2004-01-16 17:55 ` Harold L Hunt II [this message]
2004-01-16 17:59 ` Harold L Hunt II
2004-01-16 20:41 ` Harold L Hunt II
  -- strict thread matches above, loose matches on Subject: below --
2004-01-19 11:20 Atwood, Robert C
2004-01-16 18:34 Atwood, Robert C
2004-01-16 16:07 Atwood, Robert C
2004-01-16 16:35 ` Volker Quetschke
2004-01-16 13:41 Atwood, Robert C
2004-01-16 15:20 ` Volker Quetschke
2004-01-15 19:08 Atwood, Robert C
2004-01-15 19:53 ` Harold L Hunt II

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=4008259A.4090306@msu.edu \
    --to=huntharo@msu.edu \
    --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).