Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-Id: From: garkier AT osc DOT kiku DOT dk (Morten Garkier Hendriksen) Subject: Build-problem: Paths messed up while crosscompiling (includes FIX) To: cygwin AT sourceware DOT cygnus DOT com Date: Thu, 27 May 1999 17:06:37 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hello! I have succesfully built a crosscompiler (host=i586-pc-linux-gnu target=i386-pc-cygwin) using the source dev-src.tar.bz2 from my local cygnus mirror. During the build there were a few catches, probably related to wrong paths in the makefiles. I guess you guys who know the structure of the source-tree can identify the problem, and you who don't can use my workaround..:-) During the build-phase a directory in the "root" (that is src/) called i386-pc-cygwin32 is created and som directories are linked/copied into this directory. In this directory I had to create the following links, to make the tree compile: i386-pc-cygwin32: ln -s ../config.sub . ln -s ../install-sh . ln -s ./newlib/configure.host . ln -s ../mkinstalldirs . and in the subdirectory i386-pc-cygwin32/winsup (which is created later) I had to do the following: ln -s ../libstdc++/ . to match the makefiles view of the world. Since I am not used to autoconfigure-scripts in this scale, I have not tried to hunt the problem myself. The above fix worked for me. Best regards Morten Hendriksen Tech. info (if anyone should need it) cygwin-version: 20.1 (from winsup/ChangeLog) Host OS: Debian 2.1/i386 compiler: EGCS (1.1.1) arch: i586 -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com