public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Bruce Edson <bruce@steptech.com>
To: Ian Roxborough <irox@redhat.com>
Cc: "Sourcenav (E-mail)" <sourcenav@sources.redhat.com>
Subject: RE: Headaches building Source Navigator under Windows
Date: Tue, 26 Feb 2002 12:30:00 -0000	[thread overview]
Message-ID: <26F9F6EAB586D411850700B0D049E6E4014D2E5B@shasta.pdx.steptech.com> (raw)

Just as another attempt at this, I tried what you suggested, namely putting
cl.exe in quotes.  Configure now runs to the end.  Yahoo!  Quite the stab in
the dark, Ian. I am not sure what was happening, maybe you could explain.
Thanks!

Now on to the next road block in the 'make' portion of the build.  This
seems to run along for a while without errors, although a few warnings,
until the following:

LINK : LNK6004: ./tix4181.exe not found or not built by the last incremental
link; performing full link
make[2]: Leaving directory `/snbuild/tix/win'
make[1]: Leaving directory `/snbuild/tix'
make[1]: Entering directory `/snbuild/itcl'
Making in itcl/win
make[2]: Entering directory `/snbuild/itcl/itcl/win'
make[2]: *** No rule to make target `itcl_bicmds.obj', needed by
`snitcl30.dll'.
  Stop.
make[2]: Leaving directory `/snbuild/itcl/itcl/win'
make[1]: *** [all] Error 1
make[1]: Leaving directory `/snbuild/itcl'
make: *** [all-itcl] Error 2

Any thoughts?

Bruce
-----Original Message-----
From: Ian Roxborough [mailto:irox@redhat.com]
Sent: Tuesday, February 26, 2002 12:07 PM
To: Bruce Edson
Cc: Mo DeJong
Subject: Re: Headaches building Source Navigator under Windows



A stab in the dark:

Are you setting to CC="cl.exe ...." before you run configure?

Ian.

Bruce Edson wrote:
> 
> Thanks for responding, Mo.
> 
> I removed the host option and still get the same results.  I originally
put
> it there after my first attempt of a cygwin install.  That's been updated
> now, so it appears that the host option isn't needed.
> 
> When configuring itcl/win, it attempts to cd into '../../../tcl/win' and
> fails.  Maybe I need to change something to get it cd into
> '../../../tcl8.1/win'.  If so what and where would I make the change?
> 
> Ran grep in snbuild/tcl8.1 directory and got the expected results,
> 's%@CONFIGDIR@%win%g'.  I agree, it looks mighty strange that its playing
in
> the unix path here.
> 
> I also noticed that when creating tclconfig.sh and tkconfig.sh, they were
> created in snbuild/tcl8.1/unix and snbuild/tk8.1/unix subdirectories.
This
> was shortly after receiving the message '> cd: can't cd to
> ../../../tcl/win'.  Can anyone think of why?
> 
> Bruce
> 
> -----Original Message-----
> From: Mo DeJong [mailto:supermo@bayarea.net]
> Sent: Tuesday, February 26, 2002 12:48 AM
> To: sourcenav
> Subject: Re: Headaches building Source Navigator under Windows
> 
> On Fri, 22 Feb 2002 13:07:46 -0800
> Bruce Edson <bruce@steptech.com> wrote:
> 
> > I went to Cygwin site and figured out how to get the rest of the
> utilities.
> > So, now I am at the point where the 'configure' as described in the
readme
> > file, breaks with the following errors.
> 
> > ../sourc/configure --host=i686-pc-cygwin
> > --prefix="c:/docume~1/bruce/hpkeck~1/snkeck~1/opt/sourcenav"
> 
> Well, this looks ok. Any particular reason you passed a --host option
here?
> 
> > 2.
> > configuring in itcl/win
> > running /bin/sh ../../../../source/itcl/itcl/win/configure
> > --host=i686-pc-cygwin --target=i686-pc-cygwin
> > '--prefix=c:/docume~1/bruce/hpkeck~1/snkeck~1/opt/sourcenav'
> > --cache-file=../../../config.cache
> --srcdir=../../../../source/itcl/itcl/win
> > cd: can't cd to ../../../tcl/win
> 
> Humm, I would think that should be looking in ../tcl8.1/win, but I
> am not sure if it matters.
> 
> > 6.
> > Configuring snavigator...
> > checking for Tcl configuration script... (cached)
> > /snbuild/tcl8.1/unix/tclConfig.sh
> > checking for Tk configuration script... (cached)
> > /snbuild/tk8.1/unix/tkConfig.sh
> > checking for Tcl headers in the source tree... (cached) configure:
error:
> > Can't find any Tcl headers
> > Configure in /snbuild/snavigator failed, exiting.
> 
> Well, this is not right. It should be checking in tcl8.1/win not the
> unix subdir. Me thinks something has gone wrong in tcl8.1/configure.in
> where it selects either the unix subdir or the win subdir based on the
> --host setting.
> 
> Go into your $build/tcl8.1 dir and run this grep:
> grep CONFIGDIR config.status
> 
> You should get a result like:
> s%@CONFIGDIR@%win%g
> 
> If you get "unix" instead of "win" then that is the problem. You could try
> to not pass a --host option and see if that makes any diff.
> 
> cheers
> Mo

             reply	other threads:[~2002-02-26 20:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-26 12:30 Bruce Edson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-26 12:12 Bruce Edson
2002-02-26  0:23 Bruce Edson
2002-02-22 13:52 Bruce Edson
2002-02-22 14:48 ` Ian Roxborough
2002-02-22 13:21 Bruce Edson
2002-02-22 13:23 ` Syd Polk
2002-02-22 13:32 ` Ian Roxborough
2002-02-26  9:12 ` Mo DeJong
2002-02-26  9:20   ` Syd Polk
2002-02-27  8:32     ` Ralf Corsepius
2002-02-21 17:47 Bruce Edson
2002-02-21 18:08 ` Ian Roxborough
2002-02-21 18:33   ` Mo DeJong
2002-02-21 18:35     ` Ian Roxborough

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=26F9F6EAB586D411850700B0D049E6E4014D2E5B@shasta.pdx.steptech.com \
    --to=bruce@steptech.com \
    --cc=irox@redhat.com \
    --cc=sourcenav@sources.redhat.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).