X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org From: "Jean-Paul de Vooght" To: References: <019b01c924b8$23b5a8e0$9601a8c0 AT CAM DOT ARTIMI DOT COM> In-Reply-To: <019b01c924b8$23b5a8e0$9601a8c0@CAM.ARTIMI.COM> Subject: RE: RE: difficulties building graphviz 2.20.2 Date: Mon, 6 Oct 2008 15:15:29 +0200 Message-ID: <002201c927b5$9bb60150$d32203f0$@devooght@smallrivers.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Content-Language: en-gb 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 Thanks Dave! This did help me get passed iffe. I'll continue now on the graphviz mailing list trying to figure out why the build breaks building stuff under cmd/lefty. Cygwin is treated differently than UWIN when it comes to defining WIN32 and MSWIN32 which are only set for UWIN in CFLAGS and CSSFLAGS. When it comes to setting WITH_WIN32_TRUE and WITH_WIN32_FALSE though, configure bundles UWIN together with cygwin and assumes WITH_WIN32_TRUE. As a result, when making files under os and ws, the compiler aborts in cmd/lefty/ws/mswin32 complaining in gcommon about symbols which are not found in windows.h - which I do have installed. I suspect it's related. I already tried setting WIN32 and MSWIN32 which didn't work. Would be nice if there was a clean way out... I'll see if the graphviz dudes can help me out here... - JP > -----Original Message----- > From: Dave Korn [mailto:dave DOT korn AT artimi DOT com] > Sent: 02 October 2008 19:56 > To: cygwin AT cygwin DOT com > Subject: RE: difficulties building graphviz 2.20.2 > > JP de Vooght wrote on 02 October 2008 18:38: > > > [cut] > > Making all in vmalloc > > make[3]: Entering directory `/home/Jean-Paul/graphviz- > 2.20.2/lib/vmalloc' > > mkdir -p ../../FEATURE > > ../../iffe - set cc gcc : run ../../lib/vmalloc/features/vmalloc > > > ../../FEATURE/vmalloc > > > > Which hangs the build with a process running which I have to kill > outside > > of cygwin. > > > Any ideas? > > I seem to remember stumbling across this. I think I worked around it > by > running the "iffe" command manually to generate the FEATURE/vmalloc > file and > then restarting the make. > > 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/