Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jnpyM-0006gA-9B for pljava-dev@arkaria.postgresql.org; Tue, 23 Jun 2020 20:56:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jnpyL-0006W0-6Y for pljava-dev@arkaria.postgresql.org; Tue, 23 Jun 2020 20:56:49 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jnpyK-0006Vt-Mp for pljava-dev@lists.postgresql.org; Tue, 23 Jun 2020 20:56:49 +0000 Received: from anastigmatix.net ([68.171.219.55]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jnpyE-0007et-76 for pljava-dev@lists.postgresql.org; Tue, 23 Jun 2020 20:56:47 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=anastigmatix.net; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Subject:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=Zw5tv35HLOBwHDt34y+qNG5pzT8WHFdxR5qUGiVFEaI=; b=euJsznBWHvidXu3bfTr/QzkWQE nlz4gWNODapyhmzvlLjZtUBgoRSHNcFDst08bQX+bQWDwRXVPLwsSkQgSUjcLVEVgU5zOlvCmmH+e +i91Nc1ER9pEPPeF+rlWzGsO/zZhW1VpxOofqwiNRyw1wgeO5D5GbOaNtWFwRUdb+LZrmQcrDVeep jjf2PlL5scEv0wOWs7X1qakYWPb2RoYe/gMfS+ng4msHHnFZUvlg0buNzat8VV7xl3CMbsn+BGUyH 9arf0tcs2rIg7+DehsjXlwyFJI+UqveLtBSO9LUfLU8cDrEBEwtBLR8jLEqwC1HJk51z//xRmD7HF ZUteycZw==; Received: from [184.19.31.139] (port=47022) by bay.acenet.us with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from ) id 1jnpyC-00EfN3-26; Tue, 23 Jun 2020 16:56:40 -0400 Subject: Re: Issues with mingw build To: Kartik Ohri , pljava-dev@lists.postgresql.org References: <5EC17E17.7070002@anastigmatix.net> <5ED7E74B.9020800@anastigmatix.net> <5EDA576E.2000204@anastigmatix.net> <5EDBA5D9.8090506@anastigmatix.net> <5EE7AE8C.2040201@anastigmatix.net> <5EECE4F7.30603@anastigmatix.net> <5EEE0ABA.3050404@anastigmatix.net> <5EEE2593.4070802@anastigmatix.net> From: Chapman Flack X-Enigmail-Draft-Status: N1110 Message-ID: <5EF26C87.2080304@anastigmatix.net> Date: Tue, 23 Jun 2020 16:56:39 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-OutGoing-Spam-Status: No, score=-95.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - bay.acenet.us X-AntiAbuse: Original Domain - lists.postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - anastigmatix.net X-Get-Message-Sender-Via: bay.acenet.us: authenticated_id: chap@anastigmatix.net X-Authenticated-Sender: bay.acenet.us: chap@anastigmatix.net X-Source: X-Source-Args: X-Source-Dir: X-From-Rewrite: unmodified, already matched List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 06/23/20 16:39, Kartik Ohri wrote: > The mingw build is working but it spins off its new console which makes it > impossible to detect errors and retrieve logs. It even stalls the build. I > have been trying to figure a way to get past this but have been unable to > do so till now. Do you have any suggestions on how to fix this ? I have never experienced a Mingw-w64 build personally, so I don't have much insight into the details. I understand that it involves starting a shell/console within which the environment is set up for doing the build. I've always assumed that isn't necessary for running the built artifacts. Can the Mingw-w64-built PostgreSQL server be run as an ordinary executable? If it can, then the test run after building should work in the usual way. I assume that when inside the msys2 shell, the filesystem you see is still the same filesystem, so redirecting output or error output of the commands into a file ought to work, and the file could be read outside of msys2. According to a MinGW mailing list thread [1], it looks possible to redirect output and error output, either using the familiar > and 2> or by using a 'redir' command in msys (which mustn't be confused with a standard Microsoft "network redirector" command of the same name). I also gather from that thread that there's an "echo %ERRORLEVEL%" to show the exit status of a command, so that could be used after the mvn command to get an indication of whether Maven thought it had succeeded. If these are things you've already tried and there were issues, some more details of what seems to go wrong where might help. Regards, -Chap [1] https://sourceforge.net/p/mingw/mailman/message/16209368/