Opened 11 years ago
Closed 10 years ago
#43590 closed defect (fixed)
bashdb @4.2-0.8: broken by the recent bash update to 4.3
Reported by: | cooljeanius (Eric Gallager) | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.2.1 |
Keywords: | Cc: | raimue (Rainer Müller), dbl001 (dbl), fhgwright (Fred Wright) | |
Port: | bashdb |
Description
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 66dd83 in upstream git, although it appears there are still other issues with 4.3, as more recently upstream commit 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...
Attachments (2)
Change History (7)
Changed 11 years ago by cooljeanius (Eric Gallager)
Changed 11 years ago by cooljeanius (Eric Gallager)
Attachment: | config.log added |
---|
the config.log that bashdb produced when it failed
comment:1 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | davidl@… added |
---|
Has duplicate #43849.
comment:2 Changed 10 years ago by ilg@…
It looks like the new bashdb-4.3-0.9 works with bash 4.3, perhaps it is worth trying to update.
comment:3 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | fw@… added; aecollins1@… removed |
---|---|
Owner: | changed from macports-tickets@… to aecollins1@… |
Port: | bash removed |
Has duplicate #46232.
comment:4 Changed 10 years ago by mf2k (Frank Schima)
Owner: | changed from aecollins1@… to macports-tickets@… |
---|
Port abandoned. See #47223.
comment:5 Changed 10 years ago by mf2k (Frank Schima)
Resolution: | → fixed |
---|---|
Status: | new → closed |
I updated it to the latest version (4.3-0.91) in r134669 and it builds now.
main.log for the bashdb configure failure