public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Syd Polk <spolk@redhat.com>
To: Todd Dukes <tdukes@ibmoto.com>
Cc: snavigator <sourcenav@sources.redhat.com>
Subject: Re: build problems with SN452
Date: Wed, 20 Sep 2000 04:43:00 -0000	[thread overview]
Message-ID: <39C8A378.589EEF96@redhat.com> (raw)
In-Reply-To: <39C7881F.A07F5257@ibmoto.com>

Todd Dukes wrote:
> 
> I have two problems with building the SN452-source tarball
> on Solaris.

Which version of Solaris? I build it on Solaris 2.5.1 and Solaris 2.7
just fine. Are you using gcc or the native compiler?
 
> 1. TK8.1 seems to want static X11 libraries in /usr/local/lib.
>    Solaris doesn't come with static X11 libraries, and the so's
>    are in /usr/lib. I fixed this be replacing all of the
>       -Wl,-Bstatic -L/usr/local/lib -lX11 -lXext -lX11 -Wl,-Bdynamic
> -ldl
>    in the Makefiles with
>       -L/usr/lib -lX11 -lXext -lX11
> 
> 2. I typed 'make check' after building to completion and saw the error
>    message 'runtest not found'. I did a find for runtest in both the
>    source and build directories and could not find it.
>

Yup. We don't actually have a test harness right now (in the works) and
make check does not do anything. 

> Neither of these are severely inconvenient, but they may confuse
> some people who are trying to build from source.
> 
> 'make install' did work much better this time that with 4.5.1
> 
> thanks,
> Todd.
> 
> 
> --
>    | Todd Dukes                      E-MAIL:  tdukes@ibmoto.com |
>    | Motorola Somerset                  Phone:   (512) 996-4865 |

      parent reply	other threads:[~2000-09-20  4:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-19  8:37 Todd Dukes
2000-09-19 11:56 ` Ben Elliston
2000-09-20  4:43 ` Syd Polk [this message]

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=39C8A378.589EEF96@redhat.com \
    --to=spolk@redhat.com \
    --cc=sourcenav@sources.redhat.com \
    --cc=tdukes@ibmoto.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).