#43590: bashdb @4.2-0.8: broken by the recent bash update to 4.3 ---------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Keywords: | Port: bash bashdb ---------------------+-------------------------------- When configuring, bashdb fails with the following error message: {{{ checking for bash... /opt/local/bin/bash configure: WARNING: You have Bash GNU bash, version 4.3.11(1)-release (x86_64-apple-darwin10.8.0) Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software; you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. installed. configure: error: This package is only known to work with Bash 4.1 or 4.2. Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_bashdb/bashdb/work/bashdb-4.2-0.8" && ./configure --prefix=/opt/local --disable-dependency-tracking Exit code: 1 Error: Failed to configure bashdb, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_bashdb/bashdb/work/bashdb-4.2-0.8/config.log Error: org.macports.configure for port bashdb returned: configure failure: command execution failed DEBUG: Error code: NONE DEBUG: Backtrace: configure failure: command execution failed }}} This is because the bash port was updated to 4.3 as of r118612, which was in response to ticket #43173, which this ticket is split off of. The configure issue is fixed at least as of commit [http://sourceforge.net/p/bashdb/code/ci/66dd836aec50a53c829e9182d8f8092b1bcb... 66dd83] in upstream git, although it appears there are still other issues with 4.3, as more recently upstream commit [http://sourceforge.net/p/bashdb/code/ci/3900a7a1ba9507b366e733d30fc47f761da5... 3900a7] was needed to fix the testsuite with 4.3. So it seems there are two possible solutions: either move the bashdb port to track upstream git temporarily until there is a new release, or add a bash42 port for compatibility and have bashdb just use that. The former might be unstable and lead to other issues, but the latter might just be unnecessary duplication, so idk which one would be better/worse... anyways, attaching bashdb build logs... -- Ticket URL: <https://trac.macports.org/ticket/43590> MacPorts <http://www.macports.org/> Ports system for OS X