Subject: pkg/28917: cad/gschem won't build
To: None <pkg-manager@netbsd.org, gnats-admin@netbsd.org,>
From: None <dgriffi@cs.csubak.edu>
List: pkgsrc-bugs
Date: 01/09/2005 06:30:00
>Number: 28917
>Category: pkg
>Synopsis: cad/gschem won't build
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: pkg-manager
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Sun Jan 09 06:30:00 +0000 2005
>Originator: David Griffith
>Release: 2.0 / i386
>Organization:
>Environment:
NetBSD zaphod 2.0 NetBSD 2.0 (GENERIC) #0: Wed Dec 1 10:58:25 UTC 2004 builds@build:/big/builds/ab/netbsd-2-0-RELEASE/i386/200411300000Z-obj/big/builds/ab/netbsd-2-0-RELEASE/src/sys/arch/i386/compile/GENERIC i386
>Description:
The current gEDA suite is version 20040111; almost a year old. One of its components, gschem, has build problems. Trying to build pkgsrc/cad/gschem directly or by dependency (pkgsrc/cad/geda), yields this:
In file included from ../noweb/a_pan.nw:56:
../include/prototype.h:30: error: conflicting types for `g_key_file_new'
/usr/tmp/pkg_build/cad/gschem/work.zaphod/.buildlink/include/glib/glib-2.0/glib/gkeyfile.h:53: error: previous declaration of `g_key_file_new'
*** Error code 1
Stop.
make: stopped in /usr/tmp/pkg_build/cad/gschem/work.zaphod/geda-gschem-20040111/src
*** Error code 1
Stop.
make: stopped in /usr/tmp/pkg_build/cad/gschem/work.zaphod/geda-gschem-20040111/src
*** Error code 1
Stop.
make: stopped in /usr/tmp/pkg_build/cad/gschem/work.zaphod/geda-gschem-20040111
*** Error code 1
Stop.
make: stopped in /usr/tmp/pkg_build/cad/gschem/work.zaphod/geda-gschem-20040111
*** Error code 1
Stop.
make: stopped in /usr/pkgsrc/cad/gschem
*** Error code 1
Stop.
make: stopped in /usr/pkgsrc/cad/gschem
zaphod:/usr/pkgsrc/cad/gschem$
>How-To-Repeat:
Simply try to rebuild pkgsrc/cad/gschem. FWIW, this problem happened exactly as before under NetBSD 1.6.2. I upgraded thinking that would fix the problem. No dice.
>Fix:
An upgrade to Release 20041228 would probably be best. I'm trying to hack the geda packages to do this, but would the maintainer please take a look?