From: "Suhaib M. Siddiqi" <Ssiddiqi@InspirePharm.Com>
To: "Rick Scott" <rwscott@omnisig.com>
Cc: "Stipe Tolj" <tolj@uni-duesseldorf.de>,
"Jon A. Christopher" <jon@quorum.tamu.edu>,
"tromey" <tromey@cygnus.com>,
"Francois Felix Ingrand" <felix@dial.oleane.com>,
"Kilfoyle, Greg" <greg.kilfoyle@compaq.com>,
"lesstif" <lesstif@hungry.com>,
"gnu-win32" <gnu-win32@cygnus.com>, "automake" <automake@gnu.org>
Subject: Re: How To: Re: LessTif build under Cygwin32?
Date: Sun, 31 Jan 1999 23:52:00 -0000 [thread overview]
Message-ID: <004301be4ad3$b9ef86b0$29acdfd0@InspirePharm.Com> (raw)
Yes, It should be able to find if you set LD before runing configure,
But does not.
It kept failing with error message "no acceptable ld found in $PATH"
By manually editing the configure script, it find it and works.
Suhaib
----
*************************************************
Suhaib M. Siddiqi, Ph.D.
Senior Research Chemist
Inspire Pharmaceuticals, Inc.
4222 Emperor Blvd., Suite 470
Durham, NC 27703-8466
Tel: 919-941-9777 Ext. 238
Fax: 919-941-9797
E-Mail: Ssiddiqi@inspirepharm.com
http://www.inspirepharm.com
============================
----- Original Message -----
From: Rick Scott <rwscott@omnisig.com>
To: Suhaib M. Siddiqi <Ssiddiqi@InspirePharm.Com>
Cc: Stipe Tolj <tolj@uni-duesseldorf.de>; Jon A. Christopher
<jon@quorum.tamu.edu>; tromey <tromey@cygnus.com>; Francois Felix
Ingrand <felix@dial.oleane.com>; Kilfoyle, Greg
<greg.kilfoyle@compaq.com>; lesstif <lesstif@hungry.com>; gnu-win32
<gnu-win32@cygnus.com>; automake <automake@gnu.org>
Sent: Thursday, January 28, 1999 10:17 AM
Subject: Re: How To: Re: LessTif build under Cygwin32?
>What ld does configure find without all the editing.
>
>You should be able to set the evironment variable LD to whatever you
want
>before you run configure, and it should use that. Should be easier
than
>editing files.
>
>I would like to fix it so that it "configures out of the box".
>
>
>> Stipe,
>> I cannot send you precompiled LessTif 0.87 libraries right now.
>> I use Cygnus only to create Makef ile and test the configuration
files.
>> For the final compilation I use PGI commercial compilers. Therefore,
>> the
>> compiled Cygnus/LessTif binaries were desrtroyed. However, I do have
>> configuration files in-tact yet to recreat them again.
>>
>> However, I will be able to send you a precompiled LessTif 0.87 next
>> week. All, I have to do is to run a "make
>> clean" then "make" commands to rebuild them.
>>
>> Here are some MUST which users can follow to compile LessTif 0.87
>> themselves.
>>
>>
>> 1) X11R6.4 installation is required. Compile it yourself or download
it
>> from
>> Andy Piper's or Sergey's web sites.
>>
>> 2) The hard drives must be monuted in binary mode otherwise
>> configuration files
>> will fail. Users must use Sergey's COOLVIEW. Cygwin1.lib out of
Cygnus
>> distribution
>> gives problems.
>> Als, use EGCS-1.1.1 from Mumit Khan. The GCC in Cygnus distribution
>> gives problems, somtimes.
>>
>> 3) Lesstif-current.tar.gz source code must be extracted on a binary
>> mounted disk
>> using tar zxvf lesstif-current.tar.gz. Do not use anyother utility
to
>> extract the source
>> code otherwise you will have a pars errors mess during compilation.
>>
>> 4) Go to Lesstif-current source directory and edit "configure"
script.
>> Search for the
>> line LD='$ac_cv_path".
>> Change it to LD="/usr/cygnus-b20/H-i586-cygwin32/bin/ld.exe" (repalce
it
>> with your correct path)
>> Use only VI editor (no vanila Microsoft Note pad please)
>>
>> 5) Go to Xlt directory and edit the "configure" script.
>> Search for the
>> line LD='$ac_cv_path".
>> Change it to LD="/usr/cygnus-b20/H-i586-cygwin32/bin/ld.exe" (repalce
it
>> with your correct path)
>> Use only VI editor (no vanila Microsoft Note pad please)
>>
>> 6) Go to Lesstif/test subdirectory and
>> Search for the
>> line LD='$ac_cv_path".
>> Change it to LD="/usr/cygnus-b20/H-i586-cygwin32/bin/ld.exe" (repalce
it
>> with your correct path)
>> Use only VI editor (no vanila Microsoft Note pad please)
>>
>> 7) Now run the "configure" script with the following command
>>
>>
./configure --prefix=/lesstif/dist --x-includes=/usr/cygwin-b20/X11R6/in
>>
clude --x-libraries=/usr/cygwin-b20/X11R6/lib --target=H-i586-cygwin32 -
>> -enable-shared=yes --enable-static=yes
>>
>> Note: Repace /usr/cygwin-b20 according to your system path for Cygnus
>> B-20.1 installation. I have it installed under
>> /usr/cygwin-b20 on my system, because I am still using B-19 too.
>>
>> 8) Now run the make" command and LessTif should compile, under
>> Cygnus-B-20.1
>> ----
>> *************************************************
>> Suhaib M. Siddiqi, Ph.D.
>> Senior Research Chemist
>> Inspire Pharmaceuticals, Inc.
>> 4222 Emperor Blvd., Suite 470
>> Durham, NC 27703-8466
>>
>> Tel: 919-941-9777 Ext. 238
>> Fax: 919-941-9797
>> E-Mail: Ssiddiqi@inspirepharm.com
>> http://www.inspirepharm.com
>>
>> ============================
>>
>>
>>
>>
>> ----- Original Message -----
>> From: Stipe Tolj <tolj@uni-duesseldorf.de>
>> To: Suhaib M. Siddiqi <Ssiddiqi@InspirePharm.com>
>> Cc: Jon A. Christopher <jon@quorum.tamu.edu>; tromey
>> <tromey@cygnus.com>; Rick Scott <rwscott@omnisig.com>; Francois Felix
>> Ingrand <felix@dial.oleane.com>; Kilfoyle, Greg
>> <greg.kilfoyle@compaq.com>; lesstif <lesstif@hungry.com>; gnu-win32
>> <gnu-win32@cygnus.com>; automake <automake@gnu.org>
>> Sent: Tuesday, January 26, 1999 7:32 PM
>> Subject: Re: LessTif build under Cygwin32?
>>
>>
>> >Hello,
>> >
>> >> I was refering to myself. I did not have any problems in
compiling
>> >> LessTif 0.87 under Cygnus-B20, Cygnus-B-19, using EGCS and with
>> >> a little hack (i.e manually altering all the Makefiles generated
by
>> >> configure script under Cygwin) I used PGI compilers to
>> >> compile LessTif 0.87.
>> >
>> >may someone be able to contribute a clean binary package or even
better
>> >cygwin supported port source for out of the box compilation of the
>> latest
>> >lesstif and I'll put it on our distribution page at our project's
web
>> site.
>> >
>> >Same thing for the DDD debugger if available.
>> >
>> >Please consider Cygwin b20.1 as building and compilation
environment.
>> Thanks.
>> >
>> >Regards,
>> >Stipe
>> >
>> >--
>> >Stipe Tolj <tolj@uni-duesseldorf.de>
>> >
>> >Cygwin Porting Project -- "We build UNIX on top of Windows"
>> > http://www.student.uni-koeln.de/cygwin/
>> >
>> >Department of Economical Computer Science
>> >University of Cologne, Germany
>> >
>> >
>> >
>> >
>>
>>
>>
>
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next reply other threads:[~1999-01-31 23:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-31 23:52 Suhaib M. Siddiqi [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-02-03 4:06 Suhaib M. Siddiqi
1999-02-28 23:02 ` Suhaib M. Siddiqi
1999-02-02 5:44 Suhaib M. Siddiqi
1999-02-02 18:44 ` Stipe Tolj
1999-02-28 23:02 ` Stipe Tolj
1999-02-28 23:02 ` Suhaib M. Siddiqi
1999-01-31 23:52 Suhaib M. Siddiqi
1999-01-31 23:52 Suhaib M. Siddiqi
1999-01-31 23:52 ` Stipe Tolj
1999-01-31 23:52 ` Jon A. Christopher
1999-01-31 23:52 Suhaib M. Siddiqi
1999-01-31 23:52 ` Rick Scott
1999-01-31 23:52 Suhaib M. Siddiqi
1999-01-31 3:59 Earnie Boyd
1999-01-31 23:52 ` Earnie Boyd
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='004301be4ad3$b9ef86b0$29acdfd0@InspirePharm.Com' \
--to=ssiddiqi@inspirepharm.com \
--cc=automake@gnu.org \
--cc=felix@dial.oleane.com \
--cc=gnu-win32@cygnus.com \
--cc=greg.kilfoyle@compaq.com \
--cc=jon@quorum.tamu.edu \
--cc=lesstif@hungry.com \
--cc=rwscott@omnisig.com \
--cc=tolj@uni-duesseldorf.de \
--cc=tromey@cygnus.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).