From pfeifer@dbai.tuwien.ac.at  Tue Jan 16 05:22:00 2001
Return-Path: <pfeifer@dbai.tuwien.ac.at>
Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12])
	by hub.freebsd.org (Postfix) with ESMTP id ED98F37B401
	for <FreeBSD-gnats-submit@freebsd.org>; Tue, 16 Jan 2001 05:21:57 -0800 (PST)
Received: from taygeta.dbai.tuwien.ac.at (taygeta [128.130.111.77])
	by vexpert.dbai.tuwien.ac.at (8.11.1/8.11.1) with ESMTP id f0GDKq804049;
	Tue, 16 Jan 2001 14:20:52 +0100 (MET)
Received: (from pfeifer@localhost)
	by taygeta.dbai.tuwien.ac.at (8.11.1/8.11.1) id f0GDKp631317;
	Tue, 16 Jan 2001 14:20:51 +0100 (CET)
	(envelope-from pfeifer)
Message-Id: <200101161320.f0GDKp631317@taygeta.dbai.tuwien.ac.at>
Date: Tue, 16 Jan 2001 14:20:51 +0100 (CET)
From: pfeifer@dbai.tuwien.ac.at (Gerald Pfeifer)
Reply-To: pfeifer@dbai.tuwien.ac.at
To: FreeBSD-gnats-submit@freebsd.org
Cc: saper@system.pl
Subject: libtool, USE_LIBTOOL, and graphics/dia
X-Send-Pr-Version: 3.2

>Number:         24383
>Category:       ports
>Synopsis:       libtool, USE_LIBTOOL, and graphics/dia
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-ports
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Jan 16 05:30:00 PST 2001
>Closed-Date:    Sun Feb 25 18:45:07 PST 2001
>Last-Modified:  Sun Feb 25 18:47:16 PST 2001
>Originator:     Gerald Pfeifer
>Release:        FreeBSD 4.2-RELEASE i386
>Organization:
>Environment:

>Description:

	The graphics/dia port apparently needs libtool installed, yet this
	is not checked properly and the build fails in an unsuitable way.

	This is *not* necessarily a problem with the dia port, which does
	set USE_LIBTOOL in it's Makefile.

	In any case, however, this failure mode is a bad one. Either
 	$PORTSDIR/devel/libtool is absolutely required (which would be
	undesirable), then it shouldn't be skipped and the build should
	abort there.

	Or, which is *strongly* preferrable and in fact does in general
	work for other tools using libtool, an installed version of libtool
	is not required.

>How-To-Repeat:

% cd $PORTSDIR/graphics/dia
% make
===>  Extracting for dia-0.86
>Fix:

	


>Release-Note:
>Audit-Trail:

From: Dag-Erling Smorgrav <des@ofug.org>
To: pfeifer@dbai.tuwien.ac.at
Cc: FreeBSD-gnats-submit@FreeBSD.ORG, saper@system.pl
Subject: Re: ports/24383: libtool, USE_LIBTOOL, and graphics/dia
Date: 16 Jan 2001 15:38:54 +0100

 pfeifer@dbai.tuwien.ac.at (Gerald Pfeifer) writes:
 >  >> Checksum OK for dia-0.86.tar.gz.
 >  ===>   dia-0.86 depends on executable: gmake - found
 >  ===>   dia-0.86 depends on executable: libtool - not found
 >  ===>    Verifying install for libtool in /sw/FreeBSD/ports/devel/libtool
 >       >> No directory for libtool.  Skipping..
 
 Use porteasy (/usr/ports/misc/porteasy), it was written in part to
 avoid precisely this problem.
 
 DES
 -- 
 Dag-Erling Smorgrav - des@ofug.org
 

From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Dag-Erling Smorgrav <des@ofug.org>
Cc: <FreeBSD-gnats-submit@freebsd.org>, <saper@system.pl>
Subject: Re: ports/24383: libtool, USE_LIBTOOL, and graphics/dia
Date: Thu, 18 Jan 2001 01:46:45 +0100 (CET)

 On 16 Jan 2001, Dag-Erling Smorgrav wrote:
 > pfeifer@dbai.tuwien.ac.at (Gerald Pfeifer) writes:
 >>  >> Checksum OK for dia-0.86.tar.gz.
 >>  ===>   dia-0.86 depends on executable: gmake - found
 >>  ===>   dia-0.86 depends on executable: libtool - not found
 >>  ===>    Verifying install for libtool in /sw/FreeBSD/ports/devel/libtool
 >>       >> No directory for libtool.  Skipping..
 > Use porteasy (/usr/ports/misc/porteasy), it was written in part to
 > avoid precisely this problem.
 
 Thanks for the hint!
 
 You do agree, however, that the failure mode I reported is undesirable
 and should be fixed nevertheless, right?
 
 Gerald
 
 

From: Dag-Erling Smorgrav <des@ofug.org>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: <FreeBSD-gnats-submit@freebsd.org>, <saper@system.pl>
Subject: Re: ports/24383: libtool, USE_LIBTOOL, and graphics/dia
Date: 18 Jan 2001 10:43:06 +0100

 Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> writes:
 > You do agree, however, that the failure mode I reported is undesirable
 > and should be fixed nevertheless, right?
 
 Not really. I don't particularly like it, but I can see the reasoning
 for it, and since I almost always use porteasy anyway, it doesn't
 bother me.
 
 DES
 -- 
 Dag-Erling Smorgrav - des@ofug.org
 
State-Changed-From-To: open->closed 
State-Changed-By: steve 
State-Changed-When: Sun Feb 25 18:45:07 PST 2001 
State-Changed-Why:  
Add DES suggested you can either use porteasy.  Or you can use portcheckout. 
Thanks. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=24383 
>Unformatted:
 >> Checksum OK for dia-0.86.tar.gz.
 ===>   dia-0.86 depends on executable: gmake - found
 ===>   dia-0.86 depends on executable: libtool - not found
 ===>    Verifying install for libtool in /sw/FreeBSD/ports/devel/libtool
      >> No directory for libtool.  Skipping..
 ===>   dia-0.86 depends on shared library: xml.5 - found
 ===>   dia-0.86 depends on shared library: popt.0 - found
 ===>   dia-0.86 depends on shared library: X11.6 - found
 ===>   dia-0.86 depends on shared library: glib12.3 - found
 ===>   dia-0.86 depends on shared library: gtk12.2 - found
 ===>   dia-0.86 depends on shared library: Imlib.5 - found
 ===>  Applying FreeBSD patches for dia-0.86
 ===>  Configuring for dia-0.86
 libtool: not found
 creating cache ./config.cache
 checking for a BSD compatible install... /usr/bin/install -c -o root -g wheel
 checking whether build environment is sane... yes
 checking for gawk... no
 checking for mawk... no
 checking for nawk... no
 checking for awk... awk
 checking whether gmake sets ${MAKE}... yes
 checking whether to enable maintainer-specific portions of Makefiles... no
 checking how to run the C preprocessor... cc -E
 checking host system type... i386--freebsd4.2
 checking build system type... i386--freebsd4.2
 checking for ranlib... ranlib
 checking for gcc... cc
 checking whether the C compiler (cc -O -pipe ) works... yes
 checking whether the C compiler (cc -O -pipe ) is a cross-compiler... no
 checking whether we are using GNU C... yes
 checking whether cc accepts -g... yes
 checking dependency style of cc... none
 checking for ld used by GCC... /usr/libexec/elf/ld
 checking if the linker (/usr/libexec/elf/ld) is GNU ld... yes
 checking for BSD-compatible nm... /usr/bin/nm -B
 checking whether ln -s works... yes
 updating cache ./config.cache
 /ltconfig: Can't open /ltconfig: No such file or directory
 configure: error: libtool configure failed
 ===>  Script "configure" failed: here are the contents of "config.log"
 This file contains any messages produced by compilers while
 running configure, to aid debugging if configure makes a mistake.
 :	
 
