NetBSD Problem Report #12675

Received: (qmail 13762 invoked from network); 16 Apr 2001 03:06:31 -0000
Message-Id: <200104160306.f3G36Oe13204@colwyn.zhadum.de>
Date: Mon, 16 Apr 2001 05:06:24 +0200 (CEST)
From: Matthias Scheler <tron@colwyn.zhadum.de>
Reply-To: tron@colwyn.zhadum.de
To: gnats-bugs@gnats.netbsd.org
Subject: "bash" package can't be build on NetBSD 1.5 system
X-Send-Pr-Version: 3.95

>Number:         12675
>Category:       pkg
>Synopsis:       "bash" package can't be build on NetBSD 1.5 system
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    pkg-manager
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Apr 16 03:07:00 +0000 2001
>Closed-Date:    Mon Apr 16 11:36:31 +0000 2001
>Last-Modified:  Mon Apr 16 20:03:01 +0000 2001
>Originator:     
>Release:        pkgsrc of 2001/04/16
>Organization:
Matthias Scheler                                         http://core.de/~tron/
>Environment:
System: NetBSD colwyn.zhadum.de 1.5.1_BETA NetBSD 1.5.1_BETA (COLWYN) #1: Tue Apr 10 10:01:12 CEST 2001 tron@colwyn.zhadum.de:/src/sys/compile/COLWYN i386


>Description:
Building version 2.05 of the "bash" package fails on a system with NetBSD 1.5
from the release branch:

===> Building for bash-2.05
rm -f bracecomp.o
cc  -DPROGRAM='"bash"' -DCONF_HOSTTYPE='"i386"' -DCONF_OSTYPE='"netbsd"' -DCONF_MACHTYPE='"i386--netbsd"' -DCONF_VENDOR='""' -DSHELL  -DHAVE_CONFIG_H  -I/usr/pkg/include -I.  -I. -I./include -I./lib -I/usr/pkg/include -O2 -c bracecomp.c
bracecomp.c: In function `bash_brace_completion':
bracecomp.c:174: `rl_compignore_func_t' undeclared (first use in this function)
bracecomp.c:174: (Each undeclared identifier is reported only once
bracecomp.c:174: for each function it appears in.)
bracecomp.c:174: `orig_ignore_func' undeclared (first use in this function)
bracecomp.c:175: `rl_compentry_func_t' undeclared (first use in this function)
bracecomp.c:175: `orig_entry_func' undeclared (first use in this function)
bracecomp.c:176: `rl_quote_func_t' undeclared (first use in this function)
bracecomp.c:176: `orig_quoting_func' undeclared (first use in this function)
bracecomp.c:177: `rl_completion_func_t' undeclared (first use in this function)
bracecomp.c:177: `orig_attempt_func' undeclared (first use in this function)
bracecomp.c:178: syntax error before `int'
bracecomp.c:184: `orig_quoting_desired' undeclared (first use in this function)
bracecomp.c:186: `rl_filename_completion_function' undeclared (first use in this function)
bracecomp.c:187: syntax error before `)'
bracecomp.c:189: syntax error before `)'
bracecomp.c:192: `r' undeclared (first use in this function)
*** Error code 1

Stop.

Building the package on a NetBSD-current (1.5U) system works fine.

>How-To-Repeat:
cd pkgsrc/shell/bash2
make

>Fix:
None provide.

>Release-Note:
>Audit-Trail:

From: John Darrow <John.P.Darrow@wheaton.edu>
To: tron@colwyn.zhadum.de
Cc: netbsd-bugs@netbsd.org, gnats-bugs@netbsd.org
Subject: Re: pkg/12675: "bash" package can't be build on NetBSD 1.5 system
Date: Sun, 15 Apr 2001 23:06:56 -0500 (CDT)

 Matthias Scheler <tron@colwyn.zhadum.de> wrote:
 >
 >>Number:         12675
 >>Category:       pkg
 >>Synopsis:       "bash" package can't be build on NetBSD 1.5 system

 >>Description:
 >Building version 2.05 of the "bash" package fails on a system with NetBSD 1.5
 >from the release branch:
 >
 >===> Building for bash-2.05
 >rm -f bracecomp.o
 >cc  -DPROGRAM='"bash"' -DCONF_HOSTTYPE='"i386"' -DCONF_OSTYPE='"netbsd"' -DCONF_MACHTYPE='"i386--netbsd"' -DCONF_VENDOR='""' -DSHELL  -DHAVE_CONFIG_H  -I/usr/pkg/include -I.  -I. -I./include -I./lib -I/usr/pkg/include -O2 -c bracecomp.c
 >bracecomp.c: In function `bash_brace_completion':
 >bracecomp.c:174: `rl_compignore_func_t' undeclared (first use in this function)
 [many other undeclared types...]
 >*** Error code 1
 >
 >Stop.
 >
 >Building the package on a NetBSD-current (1.5U) system works fine.
 >
 >>How-To-Repeat:
 >cd pkgsrc/shell/bash2
 >make

 I'm gonna bet you've got the readline package installed on your 1.5.1_BETA
 system, and not on your 1.5U system.

 Because of the first -I/usr/pkg/include, the #include <readline/readline.h>
 in bracecomp.c picks up the readline.h in /usr/pkg/include/readline,
 instead of the one in ./lib/readline.  The former doesn't include the
 new rltypedefs.h file which defines all of the types in question.

 As a workaround, try moving /usr/pkg/include/readline out of the way
 temporarily.  I got a successful (e.g. I was able to run bash and execute
 some commands, including stuff with brace expansion) build of bash 2.05
 by doing this.

 A more permanent solution is needed, either updating the readline
 package and making bash depend on it, or figuring out some way to prevent
 that first -I/usr/pkg/include from getting in the way...

 jdarrow

 -- 
 John Darrow - Senior Technical Specialist               Office: 630/752-5201
 Computing Services, Wheaton College, Wheaton, IL 60187  Fax:    630/752-5968
 Alphapage: 6303160707@alphapage.airtouch.com            Pager:  630/316-0707
 Email:     John.P.Darrow@wheaton.edu

From: Matthias Scheler <tron@zhadum.de>
To: John Darrow <John.P.Darrow@wheaton.edu>
Cc: netbsd-bugs@netbsd.org, gnats-bugs@netbsd.org
Subject: Re: pkg/12675: "bash" package can't be build on NetBSD 1.5 system
Date: Mon, 16 Apr 2001 10:55:57 +0200

 On Sun, Apr 15, 2001 at 11:06:56PM -0500, John Darrow wrote:
 > I'm gonna bet you've got the readline package installed on your 1.5.1_BETA
 > system, and not on your 1.5U system.

 Wrong guess, it's installed on both systems. But you are on the right
 track.

 > Because of the first -I/usr/pkg/include, the #include <readline/readline.h>
 > in bracecomp.c picks up the readline.h in /usr/pkg/include/readline,
 > instead of the one in ./lib/readline.  The former doesn't include the
 > new rltypedefs.h file which defines all of the types in question.

 That sounds like the correct idea. But the culprit is probably the
 "USE_LIBINTL= yes" which is a NOP on 1.5U but adds "-I/usr/pkg/include"
 on 1.5.1_BETA.

 	Kind regards

 -- 
 Matthias Scheler                                         http://core.de/~tron/
State-Changed-From-To: open->closed 
State-Changed-By: tron 
State-Changed-When: Mon Apr 16 04:35:54 PDT 2001 
State-Changed-Why:  
Fixed following a hint by John Darrow. 

From: woods@weird.com (Greg A. Woods)
To: netbsd-bugs@NetBSD.ORG (NetBSD Bugs and PR posting List),
	gnats-bugs@gnats.netbsd.org (NetBSD GNATS submissions and followups)
Cc:  
Subject: Re: pkg/12675: "bash" package can't be build on NetBSD 1.5 system
Date: Mon, 16 Apr 2001 16:02:52 -0400 (EDT)

 [ On Monday, April 16, 2001 at 15:21:52 (-0400), Todd Vierling wrote: ]
 > Subject: Re: pkg/12675: "bash" package can't be build on NetBSD 1.5 system
 >
 > However, the major number of libintl in the base system should probably be
 > superbumped (to 10 or so) to make room for FSF expansion, to make the number
 > larger than the one in /usr/pkg/lib.

 In the past I've always thought that if the vendor used only even major
 and minor numbers then there'd be lots of room for end users to muck
 about creating their own shared libraries (which is rather critical for
 binary-only proprietary systems).

 You're probably right that bumping by 10 would help in the case where
 there are two levels of vendor.

 However I do really have to wonder about the use of any kind of
 numbering scheme to identify API changes across multiple levels of
 "vendors" in any non-proprietary "open-source" environment.  I would
 think that in this case the "vendor" closest to the "end user" would
 have the final say and that incrementing library version numbers by one
 (or perhaps by two if the "end user" is to be considered as a
 binary-only user) would be more than sufficient.  The only important
 distinction to be made is the difference between this "closest vendor"
 and any "OEM supplier" and to not leave any impression that the any
 number of these end user vendors might share any binary compatibility
 just because they use the same "OEM supplier" for some component.  The
 best way to do that might be to always provide an emulation for even
 similar systems.  Seems kinda heavy-weight, but then managing dynamic
 library versioning, especially when there's not clear one single vendor
 in control, is more or less a nightmare anyway.

 It would also help if the pkgsrc system followed the advice of the
 libtool manual and always always always bumped the shared library
 version numbers *every* time *any* change is made in the library
 release.  Never ever assume that any older binary (i.e. one linked
 against a previous version of a librray) will be 100% compatible with a
 newer release of the library.  If you're really lucky you can understand
 the changes from one release to another in the library code and
 increment only the appropriate major, minor, or patch number of the
 shared library and thus follow the search rules implemented by
 ld.[elf_]so for shared library versioning and forward compatability.

 -- 
 							Greg A. Woods

 +1 416 218-0098      VE3TCP      <gwoods@acm.org>     <woods@robohack.ca>
 Planix, Inc. <woods@planix.com>;   Secrets of the Weird <woods@weird.com>
>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.