X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 421133870858 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1599893514; bh=yMfhKipdVVQMpylr8WR5JdgeMgwpNN+OTliPho1F1j8=; h=Subject:To:References:Date:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=ovG236XDxN/ACbAPGKdF8IovFgCUhTgFEDsAmSbFXZmd5QL8YXc5wl4YLdLzbpiQ2 t7/IBJ1SiUH2fVSQ9sdJPo98iDXB1iC4qzWItB7ak6d/4F3EXiK9/5N/sx2OtVZfnV McwlQe6YOEpTow1CRxkovKIA5iFfY8CNZObDzsX0= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 04DB43857C44 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=gy6Twe2BCZzYoh/AsXJxTcVYW7G4B2UEmAvDiKscUEI=; b=t4W+l934iHgBPrJXiIgpDUdrzURzhEr0u6qxmqW2WXcmtQwXdi8lZjy64BCVV75BuQ tfNH3GVYfqcW3Omer8UiWHJE36LmszgDSMmOgUIrM1tD1i19oL7kvOBKK5od16V3Tqh/ uwH2rtF5xT15dEcakHIVaQjx6d1F/EvnVWbxalv/CrpakGHYs+UgPopDFSpqoMiJxOGl Jo8q+u5X3gfr2AsiVLg8uUVR2+A9YJF/jnOer5wVdlibXvgJrg8j4hwPPLu5G8KsAG6A CfTYv+sX6TptmxiuWLj1c1e2TRDA/h5YEBQsE/phD6b+e8VDIVYw3pZF6J+eIXkMMO4R Q4xw== X-Gm-Message-State: AOAM532Zx717Bu2XWd/B6nS7Z6bdY83+08/D7634n7D94Wa+O9pMc1SL b+rYCcpb3/6i00hr56eSRFjkTRRoMm0= X-Google-Smtp-Source: ABdhPJzly4/YLxeC+PyWz9kXn2ND2oiiM4kJr8kV337LI5L+fyNBjmbUDGW6n6Zh94AzfG1PmPM6Og== X-Received: by 2002:a05:6402:ca7:: with SMTP id cn7mr6570288edb.143.1599893510910; Fri, 11 Sep 2020 23:51:50 -0700 (PDT) Subject: Re: Setting up a proper modelling environment in Cygwin To: cygwin AT cygwin DOT com References: <90d505d5-11fc-418d-02e4-73dd423a92ce AT gmail DOT com> <22263d73-bd15-3558-bdfe-7cc960db5f65 AT SystematicSw DOT ab DOT ca> Message-ID: Date: Sat, 12 Sep 2020 08:51:50 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 In-Reply-To: <22263d73-bd15-3558-bdfe-7cc960db5f65@SystematicSw.ab.ca> Content-Language: it X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, 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 AT cygwin DOT 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: , From: Marco Atzeri via Cygwin Reply-To: Marco Atzeri Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: cygwin-bounces AT cygwin DOT com Sender: "Cygwin" On 12.09.2020 07:39, Brian Inglis wrote: > On 2020-09-11 08:59, Marco Atzeri via Cygwin wrote: >> On 11.09.2020 04:37, Lawrence Bernardo via Cygwin wrote: >>> Dear Cygwin users and developers, >>> >>> I am trying to run some models based on the ROMS ocean modeling system. And >>> although I mainly run such models on Linux supercomputing systems, I >>> sometimes use Cygwin to make test runs. However, whenever I install Cygwin >>> on a new PC, I often find that my set up on an older PC I had been using >>> doesn't work properly. After looking deeper into the issues, it seems that >>> proper compilation requires that the same fortran compiler (gfortran in >>> this case) be used to compile the necessary components. >>> >>> And as far as I understand, these components would mainly be: > >>> - netcdf-fortran > >>> As the gfortran compiler version number used for these different components >>> is not indicated whenever I run cygwin setup-x86_64.exe, I am left to guess >>> which version numbers for each to select. Of course, another option would >>> be to accept the defaults for some components, and then compile my own >>> version of say, netcdf, but this attempt almost always fails, and I'm not >>> sure if this is due to conflicts with the already existing cygwin setup. >>> >>> Given the issues above, would anyone have any suggestions or >>> recommendations on how to best achieve the setup I would like to have? I >>> will greatly appreciate any help. > >> netcdf-fortran needs a rebuild >> >> $ zcat /usr/include/netcdf.mod | head -n 1 >> GFORTRAN module version '14' created from netcdf4.f90 > > Worse, setup.ini somehow now contains component package netcdf-fortran-debuginfo > but not netcdf-fortran itself! > of course they are called a bit differently libnetcdf-fortran-devel 4.5.2-1 libnetcdf-fortran_7 4.5.2-1 -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple