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:mime-version:date:message-id:subject:from:to :content-type; q=dns; s=default; b=pM9v1H6LAucBC6aQhWhUE/pP2kJyH QS/2iNwfMHYSQkqyGgdRIjq4NpOgUWn4xXjHWf1VijOLmVBC3XZzDDtz7h82+Tsz iiMs5Vw1jL3Keg8aluay3W/8BLIpwu5p4NXvOo/pZeCZtOdWjs+hDeZj/NCPATfg 0yWu27FIhUDnME= 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:mime-version:date:message-id:subject:from:to :content-type; s=default; bh=VRJQc8PLdT8AEO3QDkNBt4gTCjc=; b=wXO oNnsIESi26ijXjzln+pqV6CRKzS8Y3GDBRSVgivLwn+uFJBkRnU4Vlh6bzi9Dbk/ KjfJWjDbL6mdKeo2gugsxnm9mrMZzvLox+01o8v0/rlh4Qxj/4a4SGB+Luj/p5I0 RDa/LtK54X+V5gXTUwXVOYchnRssbMfd4OyZvONQ= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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=2.5 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-wi0-f182.google.com MIME-Version: 1.0 X-Received: by 10.180.92.230 with SMTP id cp6mr11460958wib.80.1443127548399; Thu, 24 Sep 2015 13:45:48 -0700 (PDT) Date: Thu, 24 Sep 2015 22:45:48 +0200 Message-ID: Subject: Advices on compiling a C, C++, python and fortran code... From: Pierre Juillard To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Hi, I have found different emails related to compiling while linking libraries in a Cygwin environment. These mails are quite old (usually from year 2000 to 2003) and explain how linking either libpthread.a or libdl.a with the program being compiled. Manipulations indicated mention the need to create symbolic links to link to either cygwin1.dll or libcygwin, or to use specific compilation flags. Please, could someone tell me if such manipulations are still required to be able to compile Code_Aster in latest cygwin environment (I am using 2.2.1)? Most notably, this code is written Fortran90 + C + C++. Its compilation is managed by a quite complex python script that has been written to work on Linux workstations (Debian, Ubuntu...). The python script checks before compilation that the following libraries are found in the system: - libpthread.so or libpthread.a - libdl.so or libdl.a - libutil.so or libutil.a - libm.so or libm.a I confirm that the python script correctly found in the cygwin lib directory the following ones: libpthread.a libdl.a libutil.a libm.a Please, do I have with current cygwin version to use specific flags or to create specific symlink to make sure the code get correctly linked against these libraries? Also, once the executable will be obtained, and if I want to copy it on another Windws machine without Cygwin environment, do I have to make sure to copy as well cygwin1.dll library? If so, in which directory can I put it? I thank you in advance for your help. Best regards, Pierre -- 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