[MacPorts] #27627: Bison 2.4.3 Stall On Config
MacPorts
noreply at macports.org
Fri Dec 10 13:03:08 PST 2010
#27627: Bison 2.4.3 Stall On Config
---------------------------------+------------------------------------------
Reporter: nDiScReEt@… | Owner: mww@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.9.2
Keywords: | Port: bison
---------------------------------+------------------------------------------
Changes (by ryandesign@…):
* cc: nDiScReEt@… (removed)
* owner: macports-tickets@… => mww@…
Old description:
> I have attempted to upgrade bison on my system and find myself
> failing/stalling in the config phase after checking for java on my
> system. The exact message shows:
>
> `checking how to link with libintl... -lintl -liconv -lc -Wl,-framework
> -Wl,CoreFoundation`
>
> `checking for valgrind... no`
>
> `checking whether we are using the GNU C++ compiler... yes`
>
> `checking whether /usr/bin/g++-4.0 accepts -g... yes`
>
> `checking dependency style of /usr/bin/g++-4.0... gcc3`
>
> `checking whether /usr/bin/g++-4.0 builds executables that work... yes`
>
> `checking for Java virtual machine... java`
>
> I have cleaned the port and then attempted to upgrade the port from bison
> 2.4.2 to bison 2.4.3 with the same result. I had let this issue sit for
> over 24 hour periods, twice! And still the same result.
>
> My system is a PowerPC G5 Dual running Mac OSX 10.5.8 using MacPorts
> 1.9.2.
New description:
I have attempted to upgrade bison on my system and find myself
failing/stalling in the config phase after checking for java on my system.
The exact message shows:
{{{
checking how to link with libintl... -lintl -liconv -lc -Wl,-framework
-Wl,CoreFoundation
checking for valgrind... no
checking whether we are using the GNU C++ compiler... yes
checking whether /usr/bin/g++-4.0 accepts -g... yes
checking dependency style of /usr/bin/g++-4.0... gcc3
checking whether /usr/bin/g++-4.0 builds executables that work... yes
checking for Java virtual machine... java
}}}
I have cleaned the port and then attempted to upgrade the port from bison
2.4.2 to bison 2.4.3 with the same result. I had let this issue sit for
over 24 hour periods, twice! And still the same result.
My system is a PowerPC G5 Dual running Mac OSX 10.5.8 using MacPorts
1.9.2.
--
--
Ticket URL: <https://trac.macports.org/ticket/27627#comment:1>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list