all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: Failure building ctags with MinGW.
Date: Fri, 18 Dec 2009 16:24:36 +0100	[thread overview]
Message-ID: <878wd0s3t7.fsf@telefonica.net> (raw)
In-Reply-To: 8363847jcg.fsf@gnu.org

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Óscar_Fuentes <ofv@wanadoo.es>
>> Date: Thu, 17 Dec 2009 22:18:11 +0100
>> 
>> The build was picking GNUWin32's regex.h. Removing it and rebuilding
>> solved the problem.
>
> Which package did that regex.h come from?  Perhaps we should add
> something to PROBLEMS.

The package is regex. That machine contains a full GNUWin32 install,
comprising all packages.

> Hmm... actually, that's strange: shouldn't GCC find src/regex.h
> _before_ it looks in your system include directory?  Adding -v to the
> compilation command in lib-src shows that it should:
>
>     #include "..." search starts here:
>     #include <...> search starts here:
>      .
>      ../nt/inc
>      ../src
>      D:/usr/bin/../lib/gcc/mingw32/3.4.2/../../../../include
>      D:/usr/bin/../lib/gcc/mingw32/3.4.2/include
>     End of search list.
>
> Could you please look into this and see why it didn't work for you, or
> tell what am I missing?

The problem is that the build was configured with

--cflags -Ic:/apps/gnuwin32/include --ldflags -Lc:/gnuwin32/lib

(for adding graphics support.) With this settings, the include search
path sequence becomes

#include "..." search starts here:
#include <...> search starts here:
 .
 c:/apps/gnuwin32/include
 ../nt/inc
 ../src
 c:\apps\msys\1.0\mingw\bin\../lib/gcc/mingw32/4.4.0/../../../../include
 c:\apps\msys\1.0\mingw\bin\../lib/gcc/mingw32/4.4.0/include
 c:\apps\msys\1.0\mingw\bin\../lib/gcc/mingw32/4.4.0/include-fixed
 c:\apps\msys\1.0\mingw\bin\../lib/gcc/mingw32/4.4.0/../../../../mingw32/include
End of search list.

so it picks regex.h from gnuwin32 include directory.

I had to remove gnuwin32's unistd.h too, because it contains

#include <process.h>

which reads Emacs' src/process.h, which in turn includes unistd.h,
entering a recursive inclusion.

-- 
Óscar





  reply	other threads:[~2009-12-18 15:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-17 20:06 Failure building ctags with MinGW Óscar Fuentes
2009-12-17 21:18 ` Óscar Fuentes
2009-12-18  8:54   ` Eli Zaretskii
2009-12-18 15:24     ` Óscar Fuentes [this message]
2009-12-18 20:59       ` Eli Zaretskii
2009-12-18 21:10         ` Óscar Fuentes

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=878wd0s3t7.fsf@telefonica.net \
    --to=ofv@wanadoo.es \
    --cc=emacs-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.