Subject: pkg/32801: gtk2 initial configuration problem on IRIX
To: None <pkg-manager@netbsd.org, gnats-admin@netbsd.org,>
From: None <stuart@zeus.com>
List: pkgsrc-bugs
Date: 02/12/2006 05:35:00
>Number:         32801
>Category:       pkg
>Synopsis:       gtk2 initial configuration problem on IRIX
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Feb 12 05:35:00 +0000 2006
>Originator:     Stuart Shelton
>Release:        n/a
>Organization:
>Environment:
IRIX64 octane 6.5 07010238 IP30
>Description:

When trying to build gtk2 from source, the process fails almost immedaitely with:

===> do-fetch [gtk2+-2.8.11nb1] ===> Checking for vulnerabilities in gtk2+-2.8.1
1nb1
=> Checksum SHA1 OK for gtk+-2.8.11.tar.bz2.
=> Checksum RMD160 OK for gtk+-2.8.11.tar.bz2.
work -> /usr/bsd/var/tmp/x11/gtk2/work
===> extract-message [gtk2+-2.8.11nb1] ===> Extracting for gtk2+-2.8.11nb1
==========================================================================
The supported build options for this package are:

        debug

You can select which build options to use by setting PKG_DEFAULT_OPTIONS
or the following variable.  Its current value is shown:

        PKG_OPTIONS.gtk2+ (not defined)

==========================================================================
===> install-depends [gtk2+-2.8.11nb1] ===> Required installed package xdg-dirs>=1.1: xdg-dirs-1.2nb1 found
===> install-depends [gtk2+-2.8.11nb1] ===> Required installed package atk>=1.10.3nb1: atk-1.10.3nb1 found
Input record `CONFIGURE_ENV=F77=fa...' too long
Input record number 16
Source line number 1
*** Error code 2

Stop.
bmake: stopped in /usr/bsd/src/x11/gtk2
*** Error code 1

Stop.
bmake: stopped in /usr/bsd/src/x11/gtk2
>How-To-Repeat:

cd /usr/bsd/src/x11/gtk2 ; bmake
>Fix:

Unknown.  IRIX is set to allow 65535 command-line arguments, and configure confirms this whenever it checks.

The pkg_chk script also fails with "line too long" messages, so I actually wonder if this is a problem with a core utility - awk, perhaps?