unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Dave Uhring" <daveuhring@yahoo.com>
Subject: Re: Has anyone actually built emacs 21.3 for SOLARIS (sparc)?
Date: Fri, 23 May 2003 05:41:13 -0500	[thread overview]
Message-ID: <pan.2003.05.23.10.41.11.234674@yahoo.com> (raw)
In-Reply-To: bakbhh$q7b$1@reader1.panix.com

On Fri, 23 May 2003 05:28:17 +0000, David Combs wrote:

> In article <pan.2003.05.22.15.45.10.303311@yahoo.com>,
> Dave Uhring <daveuhring@yahoo.com> wrote:
>>On Thu, 22 May 2003 15:06:10 +0000,
>>bbense+gnu.emacs.help.comp.unix.solaris.May.22.0 wrote:
> 
>>
>>> _ AFAIK, autoconf doesn't know how to set these things. You
>>>   either have to write your own hacks to configure.in or use the
>>>   generic libtool solution. Libtool was written to solve exactly
>>>   this problem. 
>>
>>/tmp/emacs-21.3/src/Makefile generated with $LDFLAGS=""
>>
>>LDFLAGS= -L/usr/openwin/lib
>>X11_LDFLAGS = -L/usr/openwin/lib
>>LIBX= $(LIBXMENU) $(X11_LDFLAGS) $(LIBXT) -ltiff -ljpeg -lpng -lz -lm -lXpm -lX11
>>


As I pointed out in the next few lines this is completely in error.
 
> Since I uses csh, I made a  file env.source:
> 
> setenv LDFLAGS '-L/usr/openwin/lib'
> setenv X11_LDFLAGS  '-L/usr/openwin/lib'
> setenv LIBX '$(LIBXMENU) $(X11_LDFLAGS) $(LIBXT) -ltiff -ljpeg -lpng -lz -lm -lXpm -lX11'
> 
> , and then said "source env.source", and then "env", and got:
> 
> LDFLAGS=-L/usr/openwin/lib
> X11_LDFLAGS=-L/usr/openwin/lib
> LIBX=$(LIBXMENU) $(X11_LDFLAGS) $(LIBXT) -ltiff -ljpeg -lpng -lz -lm -lXpm -lX11
> 110 ==/david3/from_netcom-dir2/sources-stuff/emacs-21.3==> 
> 
> as the final three lines.
> 
> Look ok to you?

No.  You set up your env.source incorrectly.  I keep telling you that
LDFLAGS must contain -L and -R entries for each library directory and you
did not even bother with -R/usr/openwin/lib in your env.source file.

 
>>Note that the -R/usr/openwin/lib linking argument does not exist.  Neither
>>does -L/usr/sfw/lib and hence /usr/ccs/bin/ld is NOT going to find
>>libtiff.so, libjpeg.so or libpng.so, let alone provide the required
>>run-time link paths.
>>
>>Now export LDFLAGS properly and run configure again.  
> 
> I think (maybe wrongly, for sure!) that csh has no export cmd,
> nor(?) needs one?

Right, but you need to use setenv, which is the csh equivalent to
ksh,bash,zsh export.
 
> Oh, better do a "make clean", I suppose, first.

Just remove config.cache and config.status if you have a clean source
tree.
 
                                                                                                                                      
> Note that my libx is a lot shorter than yours; I guess I'll ltry
> making it this way first, then worry later about those other
> things.

That is because libtiff, libjpeg, etc were not found.

It will not build correctly.

  parent reply	other threads:[~2003-05-23 10:41 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-20 16:41 Has anyone actually built emacs 21.3 for SOLARIS (sparc)? David Combs
2003-05-20 18:10 ` Stefan Monnier
2003-05-20 19:38   ` Dave Uhring
2003-05-20 18:39 ` Dave Uhring
2003-05-21 21:47   ` David Combs
2003-05-21 22:37     ` Stefan Monnier
2003-05-21 23:15       ` Darren Dunham
2003-05-22  0:54         ` Stefan Monnier
2003-05-22 15:06           ` bbense+gnu.emacs.help.comp.unix.solaris.May.22.03
2003-05-22 15:45             ` Dave Uhring
2003-05-23  5:28               ` David Combs
2003-05-23  9:18                 ` David Combs
2003-05-23 10:45                   ` Dave Uhring
2003-05-26  0:44                     ` David Combs
2003-05-23 10:41                 ` Dave Uhring [this message]
2003-05-23  4:36             ` David Combs
2003-05-23  5:53               ` Miles Bader
2003-05-22  8:02       ` David Combs
2003-05-22 13:56         ` Stefan Monnier
2003-05-22 14:53           ` David Combs
2003-05-20 19:53 ` Bijan Soleymani
2003-05-20 21:03   ` Dave Uhring
2003-05-21  8:50     ` David Combs
2003-05-21 15:55       ` Dave Uhring
2003-05-21 22:24         ` David Combs
2003-05-21 22:49           ` Stefan Monnier
2003-05-21 23:34           ` Dave Uhring
2003-05-22  8:07             ` David Combs
2003-05-22 13:48             ` Casper H.S. Dik
2003-05-22 14:45               ` Dave Uhring
2003-05-24  7:29                 ` David Combs
2003-05-24 14:55                   ` Dave Uhring
2003-05-25 16:40                     ` Philip Brown
2003-05-26  2:46                       ` David Combs
2003-05-26 19:14                         ` Philip Brown
2003-05-26 13:13                     ` David Combs
2003-05-26 15:46                       ` Dave Uhring
2003-05-26 22:49                         ` David Combs
2003-05-26 23:44                           ` Dave Uhring
2003-05-27  0:10                             ` Dave Uhring
2003-06-03  7:13                               ` David Combs
2003-06-03  7:09                             ` David Combs
2003-06-03 13:47                               ` Dave Uhring
2003-05-27 15:42                         ` Kevin Rodgers
2003-06-03  7:19                           ` David Combs
2003-05-21 21:44     ` David Combs

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pan.2003.05.23.10.41.11.234674@yahoo.com \
    --to=daveuhring@yahoo.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).