Bug 123985

Comment 1 Edwin Groothuis 2008-05-25 20:20:13 UTC

Responsible Changed
From-To: freebsd-ports-bugs->ade

Over to maintainer (via the GNATS Auto Assign Tool)

Comment 2 Kris Kennaway 2008-05-25 20:44:53 UTC

Jonathan Lennox wrote:
>> Number:         123985
>> Category:       ports
>> Synopsis:       devel/autoconf262 doesn't build with system texinfo on FreeBSD 5.x
>> Confidential:   no
>> Severity:       serious
>> Priority:       medium
>> Responsible:    freebsd-ports-bugs
>> State:          open
>> Quarter:        
>> Keywords:       
>> Date-Required:
>> Class:          sw-bug
>> Submitter-Id:   current-users
>> Arrival-Date:   Sun May 25 19:20:02 UTC 2008
>> Closed-Date:
>> Last-Modified:
>> Originator:     Jonathan Lennox
>> Release:        FreeBSD 5.5-RELEASE-p20 i386
>> Organization:
> Columbia University
>> Environment:
> System: FreeBSD cnr.cs.columbia.edu 5.5-RELEASE-p20 FreeBSD 5.5-RELEASE-p20 #27: Thu Apr 17 12:35:22 EDT 2008 lennox@cnr.cs.columbia.edu:/usr/obj/usr/src/sys/CNR i386
> 
> 
> 	
>> Description:
> 
> The port devel/autoconf262 doesn't build using the system texinfo on FreeBSD
> 5.x.  The build fails as follows:
> 
> gmake[2]: Entering directory `/usr/ports/devel/autoconf262/work/autoconf-2.62/doc'
> Updating ./version.texi
> restore=: && backupdir=".am$$" && \
> 	am__cwd=`pwd` && cd . && \
> 	rm -rf $backupdir && mkdir $backupdir && \
> 	if (/bin/sh /usr/ports/devel/autoconf262/work/autoconf-2.62/build-aux/missing --run makeinfo --version) >/dev/null 2>&1; then \
> 	  for f in autoconf-2.62.info autoconf-2.62.info-[0-9] autoconf-2.62.info-[0-9][0-9] autoconf-2.62.i[0-9] autoconf-2.62.i[0-9][0-9]; do \
> 	    if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
> 	  done; \
> 	else :; fi && \
> 	cd "$am__cwd"; \
> 	if /bin/sh /usr/ports/devel/autoconf262/work/autoconf-2.62/build-aux/missing --run makeinfo --no-split  -I . \
> 	 -o autoconf-2.62.info autoconf-2.62.texi; \
> 	then \
> 	  rc=0; \
> 	  cd .; \
> 	else \
> 	  rc=$?; \
> 	  cd . && \
> 	  $restore $backupdir/* `echo "./autoconf-2.62.info" | sed 's|[^/]*$||'`; \
> 	fi; \
> 	rm -rf $backupdir; exit $rc
> autoconf-2.62.texi:1723: Unknown command `'.
> autoconf-2.62.texi:3353: Unknown command `'.
> autoconf-2.62.texi:3920: Unknown command `'.
> [Many more instances of "Unknown command" error omitted.]
> makeinfo: Removing output file `autoconf-2.62.info' due to errors; use --force to preserve.
> gmake[2]: *** [autoconf-2.62.info] Error 1
> gmake[2]: Leaving directory `/usr/ports/devel/autoconf262/work/autoconf-2.62/doc'
> gmake[1]: *** [all-recursive] Error 1
> gmake[1]: Leaving directory `/usr/ports/devel/autoconf262/work/autoconf-2.62'
> gmake: *** [all] Error 2
> *** Error code 2
> 
> 
>> How-To-Repeat:
> 
> On FreeBSD 5.x:
> 
> portinstall devel/autoconf262
> 
>> Fix:
> 
> The following patch fixes the problem, by using the version of makeinfo from
> the print/texinfo port on FreeBSD 5.x.
> 
> See also PRs ports/106379 and ports/106385, which fixed the same problem for
> m4 and automake respectively.
> 
> --- devel/autoconf262/Makefile.orig	Sun May 25 15:03:59 2008
> +++ devel/autoconf262/Makefile	Sun May 25 15:04:58 2008
> @@ -28,6 +28,13 @@ USE_GMAKE=	yes
>  USE_PERL5=	yes
>  INFO=		autoconf-${BUILD_VERSION}
>  
> +.include <bsd.port.pre.mk>
> +
> +.if ${OSVERSION} < 600000
> +BUILD_DEPENDS+=	${LOCALBASE}/bin/makeinfo:${PORTSDIR}/print/texinfo
> +CONFIGURE_ENV+=	MAKEINFO="${LOCALBASE}/bin/makeinfo"
> +.endif
> +
>  GNU_CONFIGURE=	yes
>  CONFIGURE_ENV+=	CONFIG_SHELL=${SH} M4=${LOCALBASE}/bin/gm4
>  CONFIGURE_ARGS=	--program-suffix=-${BUILD_VERSION} --without-lispdir
> @@ -57,4 +64,4 @@ post-install:
>  	@${INSTALL_SCRIPT} ${WRKSRC}/build-aux/${FILE} ${PREFIX}/share/autoconf-${BUILD_VERSION}
>  .endfor
>  
> -.include <bsd.port.mk>
> +.include <bsd.port.post.mk>

Note that support for all FreeBSD 5.x users will be ended on May 31, 
i.e. in 6 days.

Kris

Comment 3 Ade Lovett 2008-05-26 00:03:34 UTC

State Changed
From-To: open->closed

Given that support for 5.x is going away in 6 days time at the end of May, 
I see no reason to add this in, only to remove it again on June 1st.