public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: SMANSFEL@bouyguestelecom.fr
To: keiths@redhat.com
Cc: insight@sources.redhat.com, sebastien.mansfeld@club-internet.fr
Subject: RE: Problems building Insight 5.3 on Sun Solaris !
Date: Tue, 01 Jul 2003 17:59:00 -0000	[thread overview]
Message-ID: <776BD5C0BA88D4118ABD0008C79F30770953D6D6@bt1sqteb.bpa.bouyguestelecom.fr> (raw)

It worked !!
I shouldn't have used the same directory for building the all thing.
Thanks for all of your help and patience !

Cordialement, 

Sébastien MANSFELD 
SOPRA Group 
Europa M  - 4ème étage - Aile D - fenêtre 19 
* : 01 39 45 (6)37 45 
<mailto:smansfel@bouyguestelecom.fr> 



-----Message d'origine-----
De: Keith Seitz [mailto:keiths@redhat.com]
Date: mardi 1 juillet 2003 17:24
À: SOPRA - MANSFELD, Sebastien
Cc: insight@sources.redhat.com; sebastien.mansfeld@club-internet.fr
Objet: RE: Problems building Insight 5.3 on Sun Solaris !


On Tue, 2003-07-01 at 01:40, SMANSFEL@bouyguestelecom.fr wrote:
> You're absolutely right !
> Here it's (see attached file).

I've diff'd your Makefile with the one that I've generated and used on
my Red Hat linux box -- no substantial differences.

As I suspected, your make is complaining about line 59 of the Makefile
(although I think it is really 58):

58 ifeq ($(TCL_SHLIB_SUFFIX),.dll)
59 CYGWIN_CFLAGS=-I$(srcdir)/../../../../tcl/win
60 else
61 CYGWIN_CFLAGS=
62 endif

I edited the paths in your Makefile (srdir, plugin_srcdir, and
plugin_builddir) and used it to build the example plugin, rhabout. It
worked!

Are you absolutely certain that you're using GNU make? I've inspected
your build script, and although it is quite goofy (it appears to
duplicate the build dependencies that are inheritly part of the source
tree you've already downloaded), I don't see immediately why it might
affect anything.

Here's what I would like you to do:
1. configure and build the source tree as normal. i.e., without your
build script. This will really make it easier for me to understand the
process behind the build that is occurring on your machine. To do this:
$ ls
src/
$ mkdir solaris; cd solaris
$ ../src/configure > config.out 2>&1
[snip]
$ make all-gdb > build.out 2>&1

Send the two resulting files, config.out and build.out, to the list.

Also, do this:
$ which make
[send output to list]
$ make -v
[send output to list]

I cannot understand why your version of GNU make would choke on line
58/59 and mine does not...

Hmm. One more thing to try. Does the build work if you delete the whole
ifeq-else-endif clause starting at line 58?

Keith


             reply	other threads:[~2003-07-01 17:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-01 17:59 SMANSFEL [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-01  9:25 SMANSFEL
2003-07-01  9:18 SMANSFEL
2003-07-01 15:13 ` Keith Seitz
2003-06-30 17:18 SMANSFEL
2003-06-30 17:27 ` Keith Seitz
2003-06-30 16:25 SMANSFEL
2003-06-30 16:57 ` Keith Seitz
2003-06-30 15:52 SMANSFEL
2003-06-30 16:52 ` Keith Seitz
2003-06-30 10:45 SMANSFEL
2003-06-27 14:42 sebastien.mansfeld
2003-06-27 16:45 ` Keith Seitz

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=776BD5C0BA88D4118ABD0008C79F30770953D6D6@bt1sqteb.bpa.bouyguestelecom.fr \
    --to=smansfel@bouyguestelecom.fr \
    --cc=insight@sources.redhat.com \
    --cc=keiths@redhat.com \
    --cc=sebastien.mansfeld@club-internet.fr \
    /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).