public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Bruce Edson <bruce@steptech.com>
To: sourcenav <sourcenav@sources.redhat.com>
Subject: RE: Trouble building grep portion of Source Navigator
Date: Tue, 05 Mar 2002 10:53:00 -0000	[thread overview]
Message-ID: <26F9F6EAB586D411850700B0D049E6E4014D2E84@shasta.pdx.steptech.com> (raw)

Thanks Mo for looking at this.

I've been using export="cl.exe".  It's only slightly different than what you
suggest.  Do you think it would make a difference?

Bruce

-----Original Message-----
From: Mo DeJong [mailto:supermo@bayarea.net]
Sent: Thursday, February 28, 2002 2:12 PM
To: sourcenav
Subject: Re: Trouble building grep portion of Source Navigator


On Thu, 28 Feb 2002 08:54:34 -0800
Bruce Edson <bruce@steptech.com> wrote:

> First problem encountered:
> 
>   It appeared that a portion of grep compiles.  It then runs into a
problem
> with a missing libintl.h file.  When I look into the include directory
> ../intl, sure enough the file is there, but, it is a Windows shortcut file
> to libgettext.h back in the source tree.  I wasn't aware that Make would
> work with shortcut files.  If I replace the shortcut with a real version
of
> the file (not libgettext.h), I get past this problem.  Why is this
shortcut
> file being created for me?  Also, if I use '--with-included-gettext' for
> configure, the problem still exists, even though this would suggest
> eliminating the need for libintl.h.  Any ideas?

Groan! I looked in grep/configure.in and found this:

dnl FIXME: this overcomes a flaw in using non-Cygwin tools with symlinks.
if test x$ac_cv_prog_CC = xcl ; then
  AC_MSG_RESULT([copying libgettext.h to intl/libintl.h])
  if test -f $nls_cv_header_intl ; then
    rm $nls_cv_header_intl
  fi
  cp $srcdir/$nls_cv_header_libgt $nls_cv_header_intl
fi

Looks like you need to use export CC=cl to get around that.

> Second problem encountered: 
>  
>   After copying a real libintl.h file into ../grep/intl, the make compiles
> the c files okay and then tries to work with a file called libintl.a.  I
get
> the following output.  Could anyone give me a clue as to what is going
> wrong?  Is there an incompatability with VC++ compiler/linker?  I tried
> adding '--with-included-gettext' to the configure and starting over with a
> clean build directory.  No change. 
> 
>   cl.exe  -Z7 -Od  -o grep.exe  grep.obj dfa.obj kwset.obj obstack.obj
> getopt.obj
>   getopt1.obj search.obj btowc.obj regex.obj ../intl/libintl.a
>   Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 12.00.8804 for
> 80x86
>   Copyright (C) Microsoft Corp 1984-1998. All rights reserved.
> 
>   Command line warning D4024 : unrecognized source file type
> '../intl/libintl.a',


This is just a goofy hack in the old grep build system. It should not
cause problems linking.

>   ../intl/libintl.a
>   regex.obj : error LNK2001: unresolved external symbol _alloca
>   libintl.a(dcgettext.obj) : error LNK2001: unresolved external symbol
> _alloca
>   libintl.a(localealias.obj) : error LNK2001: unresolved external symbol
> _alloca
>   grep.exe : fatal error LNK1120: 1 unresolved externals
>   make[3]: *** [grep.exe] Error 2
>   make[3]: Leaving directory `/cygdrive/c/snkeck/snbuild/grep/src'

This is also caused by the CC=cl thing.

From configure.in:

if test x$ac_cv_prog_CC = xcl ; then
  AC_DEFINE(alloca, _alloca)
fi

cheers
Mo

             reply	other threads:[~2002-02-28 23:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-05 10:53 Bruce Edson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-28 14:12 Bruce Edson
2002-02-28 15:55 ` Mo DeJong

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=26F9F6EAB586D411850700B0D049E6E4014D2E84@shasta.pdx.steptech.com \
    --to=bruce@steptech.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).