From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.13]) by sourceware.org (Postfix) with ESMTPS id 3A529386EC75 for ; Thu, 7 Jan 2021 17:21:48 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 3A529386EC75 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=SystematicSw.ab.ca Authentication-Results: sourceware.org; spf=none smtp.mailfrom=brian.inglis@systematicsw.ab.ca Received: from [192.168.1.104] ([24.64.172.44]) by shaw.ca with ESMTP id xYyoknVtrtdldxYypkX7cq; Thu, 07 Jan 2021 10:21:47 -0700 X-Authority-Analysis: v=2.4 cv=INe8tijG c=1 sm=1 tr=0 ts=5ff7432b a=kiZT5GMN3KAWqtYcXc+/4Q==:117 a=kiZT5GMN3KAWqtYcXc+/4Q==:17 a=IkcTkHD0fZMA:10 a=7gn1CcUKcHApy0fmI9IA:9 a=QEXdDO2ut3YA:10 Reply-To: cygwin@cygwin.com To: cygwin@cygwin.com References: From: Brian Inglis Organization: Systematic Software Subject: Re: problem using gcc-core for compile qemu Message-ID: <6d523871-6f00-951e-0b5d-afb260402c14@SystematicSw.ab.ca> Date: Thu, 7 Jan 2021 10:21:46 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-CA Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4xfNNJRnY0zosYaj6/sMijcxVEHrEIWetyNL6PzpQbthHNz/FHKLHWXEXs2CCPWkVJCKv+NCwHvP4L0x0NeyayGWynP1nb3mKGI6M93sRAI1Y46ygoKdMj pgsYuZlWONeOGvOh8HLr5gb71nkUcJfA0POtAKstHFTKpobaJYcPN56nbdbIAZV5HXs2RSX52W1EyATz2ZKDGS2Q9lUvZGj3xhQ= X-Spam-Status: No, score=-5.9 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jan 2021 17:21:49 -0000 On 2021-01-06 20:23, Juan carlos Rebate via Cygwin wrote: > Good morning happy new year, first of all I am going to ask you that > when you read my case, do not refer me to another tool, do not refer > me to another environment, but above all do not ask me to read because > I already read all of Google and there is no solution , but I refuse > to think that there is not, it is simply that nobody has bothered to > publish it. > I am using the gcc-core 9.3 package to compile qemu, I use this one > because mingw does not incorporate all the features that I am looking > for, and gcc is able to search for resources as it would in linux > whereas mingw cannot unless the paths are edited. > the problem that appears to me is the following: > ERROR: Unrecognized host OS (uname -s reports 'CYGWIN_NT-10.0'), there > are no options to indicate the target, there are no options to avoid > the operating system test, (at least not in a simple way). How could I > solve the failure? I beg that it be done as I have it configured If qemu used autotools then it could require only autoreconfig. You need to patch the configure script to recognize __CYGWIN__ and set Cygwin as targetos, then pick mainly Linux features if they are supported POSIX interfaces, otherwise have a look at the Mingw alternative, and pick features suitable for Cygwin. It might be easier or you might be better just changing the Mingw build to do what you want instead. In either case you could then submit the patches upstream on github as a PR (pull request: fork the project repo on github under your account, then clone your fork of the repo to your system, create a topic branch, make your changes and commits incrementally, then push the branch back to your fork of the repo on github, and submit a PR from that to the original upstream qemu repo). Even if they don't accept the PR, you can still pull and merge updates from the upstream repo to your fork and your clone. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in binary units and prefixes, physical quantities in SI.]