X-Spam-Check-By: sourceware.org From: "Dave Korn" To: "'Brian Hassink'" Cc: Subject: [PING boost maintainer] RE: boost 1.33.1-2 filesystem issue (was RE: Fatal Error w/ cygwin 1-5-23-*) Date: Mon, 1 Jan 2007 17:49:20 -0000 Message-ID: <034d01c72dcd$2a4ddd00$a501a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <467C77F6373BDE4BB16A3E8A62C039550D9B91@Exchserv.hatteras.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On 31 December 2006 19:50, Brian Hassink wrote: [ List Cc'd back in so the boost maintainer can see what we're doing. ] > Here's how I built the test case included earlier in this thread... > >> g++ -I/usr/include/boost-1_33_1 -Wall -g -o test.o -c test.cpp >> g++ -o test.exe test.o -lboost_filesystem-gcc-mt-s Well, I can reproduce this, but I don't know if recompiling is going to help; there's no DLLs involved here, and the problem fixed in gcc-3.4.4-3 relates to passing C++ string class objects between dlls and exes. I'm going to try rebuilding the boost package JFTHOI, but I don't expect it to make any difference. I also notice this comment in the boost package build script: # There are some problems with Boost DLLs for Cygwin. Mostly the fact that it # does not generate import libraries. So there will be only static Boost libs # until the problem gets sorted out. which concurs with what I discovered when I tried building the upstream sources. Finally, PING! boost maintainer: build-boost.sh has CRLF line endings. Trivially fixable with d2u. cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/