Subject: pkg/18962: lang/gprolog is out of date
To: None <gnats-bugs@gnats.netbsd.org, brook@nmsu.edu>
From: None <jschauma@netmeister.org>
List: netbsd-bugs
Date: 11/07/2002 12:43:40
>Number:         18962
>Category:       pkg
>Synopsis:       lang/gprolog is out of date
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    pkg-manager
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Thu Nov 07 09:44:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Jan Schaumann
>Release:        NetBSD 1.6F
>Organization:
	
>Environment:
	
	
System: NetBSD www 1.6F NetBSD 1.6F (HERRCHEN) #0: Tue Aug 27 22:15:11 EDT 2002 jschauma@www:/src/sys/arch/i386/compile/HERRCHEN i386
Architecture: i386
Machine: i386
>Description:
	I.) lang/gprolog is of version 1.1.6, the MASTER_SITE has 1.2.16.

	II.) The old version has moved to
	ftp://ftp.inria.fr/INRIA/Projects/contraintes/gprolog/Old_Versions/

	Adjusting MASTER_SITES to fetch 1.1.6 from this location allows you to
	start the build, but it ultimately fails with:

	...
	gplc -c first_arg.wam
	gplc -c indexing.wam
	gplc -c wam_emit.wam
	cp pl2wam pl2wam0
	cp: pl2wam: No such file or directory
	*** Error code 1 (ignored)
	gplc -o pl2wam --no-fd-lib --min-bips pl2wam.o read_file.o bip_list.o  syn_sugar.o internal.o code_gen.o  reg_alloc.o inst_codif.o  first_arg.o indexing.o wam_emit.o
	/usr/pkgobj/lang/gprolog/work.i386/gprolog-1.1.6/src/BipsPl/libbips_pl.a(os_interf_c.o): In function `Temporary_File_3':
	os_interf_c.o(.text+0x14b8): warning: tempnam() possibly used unsafely, use mkstemp() or mkdtemp()
	/usr/pkgobj/lang/gprolog/work.i386/gprolog-1.1.6/src/BipsPl/libbips_pl.a(os_interf_c.o): In function `Temporary_Name_2':
	os_interf_c.o(.text+0x1427): warning: mktemp() possibly used unsafely, use mkstemp() or mkdtemp()
	gplc -c --fast-math fd2c.pl
	compilation failed
	*** Error code 1

>How-To-Repeat:
	I.) See Makefile.
	II.) cd .../lang/gprolog && make
>Fix:
	I.) Update to 1.2.16 -- may require modifying patches and testing
	    the installation.
	II.) Dunno, presumably solved by I.
>Release-Note:
>Audit-Trail:
>Unformatted: