X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; q=dns; s=default; b=kSJ6WihxEOWRhoi2e3sbRo2Zxyuk
	A332HYkuHeFza+LiEIJNqBVEy0vVVeUSNzPGZ8MJmn1pzaG6QzArSpCxLP9Rh0zQ
	3dj/AoDIipxoMLCd3KS95ZEllnAJo5ZDlXuhpSgCkLEeo8cyVyp1Yu3uzdXeHSnP
	3TU5PJ6xa2KBzhI=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; s=default; bh=JbpCjgnInyyXX7ZxsO5vKqPCEko=; b=hg
	vp4xKmtIbxZXb9BrxtWAyaSNRDVvow9pjiw/hN3m0pjnhkQTIbMOL306AaWpc3Lv
	mq61cBKnm6b9JqbMXEkW21Wd48UIcq5fdag4CFENneMrmjMFyRo73awphMq/S3HR
	05V8XjOVhSewbBambLN621jLu0V9IyMlP/aZJ3S0g=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=1.2 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,T_RP_MATCHES_RCVD autolearn=no version=3.3.2
X-HELO: etr-usa.com
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: posix vs. win32 paths (segfault vs. gdb)
From: Warren Young <wyml AT etr-usa DOT com>
In-Reply-To: <CA+Ei1Of8xBkUTTqp+fiHKcxZcCSkDC1rVdyUnt3Riy_wfTLLFA@mail.gmail.com>
Date: Thu, 10 Dec 2015 15:58:25 -0700
Message-Id: <2C683C64-3342-45F7-9A8B-B8C3D2B06037@etr-usa.com>
References: <CA+Ei1Of8xBkUTTqp+fiHKcxZcCSkDC1rVdyUnt3Riy_wfTLLFA AT mail DOT gmail DOT com>
To: The Cygwin Mailing List <cygwin AT cygwin DOT com>
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id tBAMwlda031867

On Dec 9, 2015, at 11:53 AM, Martin Landa <landa DOT martin AT gmail DOT com> wrote:
> 
> I am trying
> to compile GRASS GIS program on cygwin using *mingw32-w64* toolchain.

MinGW isn’t really on topic here.  Although these are Cygwin packages, build problems using them are typically not Cygwin problems.

Cygwin GNU make and MinGW GNU make behave quite differently, even though they’re built from the same source code.  The two key differences are that MinGW make uses cmd.exe for shell commands instead of /bin/sh, and that MinGW make can’t understand Cygwin’s POSIX paths.

Consequently, a package that supports building under both Cygwin and MinGW must have two different build systems.  The makefiles must differ.

GIS is a pretty specialized field, and GRASS is huge, so you’ll be lucky if anyone on the list has even tried what you’re proposing.  (Which is why I’m bothering to respond in the first place, even though I am not a GRASS user, and the closest I’ve gotten to GIS is the “ooo, maps” level of spectator appreciation.)

> First of all tried to launch this command from terminal:

Good, you’ve already tried the first thing I thought of asking.

Not everyone would even recognize that monstrosity as a single command, much less know enough to try and run it to see what happens.  Good job.

> and it failed with Segmentation fault.
> 
> Then I tried to launch it via gdb (so I changed last line to `gdb
> --args /home/landa/grass_trunk/dist.x86_64-w64-mingw32/bin/db.columns.exe
> --html-description` and type `run`:

You should prefix “gdb” with the PATH and LC_ALL environment overrides to fully match what GNU make is doing.

I don’t know if it matters, but let’s not introduce unnecessary variables.

> if I change path to this file from posix to win32 then the program
> run successfully without any error and produce desired output.

That sounds like the GRASS build process detected a POSIX-like environment, so it assumed that the resulting executables would also understand POSIX paths, which they won’t if built by MinGW GCC.

That means that either GRASS requires a POSIX environment, or it has a separate build process for MinGW, which you aren’t using by building under Cygwin.

Have you read this?

  https://trac.osgeo.org/grass/wiki/CompileOnWindows
--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple