#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

#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 ---------------------------------+------------------------------------------ Comment(by nDiScReEt@…): Replying to [comment:2 jmr@…]:

I can't reproduce on the same hardware and OS. Attach the log files generated by both macports (look under `/opt/local/var/macports/logs`) and autoconf (look for config.log under the directory given by `port work bison`).

I did some different actions to find a resolution: My first solution attempt was to deactivate bison-2.4.2, clean the bison port, and then choose to install bison-2.4.3 but that produced the same result which is no success. My second solution attempt was to choose gcc42 from gcc_select and then do all the steps listed above. That worked. I wish there was a way to tell what gcc I had selected before I did the change. The files listed above are the files before I attempted to do the second solution. My steps: {{{ sudo gcc_select gcc42 sudo port -d deactivate bison sudo port -d clean --work bison sudo port -d install bison }}} These are the gcc version I have installed on my system: {{{ gcc_select -l Available versions: gcc40 gcc42 llvm-gcc42 mp-gcc42 mp-gcc45 }}} In conclusion my problem is solved. Thank you for your editing and quick response. -- Ticket URL: <https://trac.macports.org/ticket/27627#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS

#27627: Bison @2.4.3 configure test for gcj can take excessive time and memory ---------------------------------+------------------------------------------ Reporter: nDiScReEt@… | Owner: mww@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: bison ---------------------------------+------------------------------------------ Comment(by ilia_2s@…): I got same problems not for bison only but for other different ports and sources. I fixed this bu changing default compiler throught gcc_select. -- Ticket URL: <https://trac.macports.org/ticket/27627#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS

#27627: Bison @2.4.3 configure test for gcj can take excessive time and memory --------------------------+------------------- Reporter: nDiScReEt@… | Owner: mww@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Resolution: | Keywords: Port: bison | --------------------------+------------------- Comment (by larryv@…): Replying to [comment:6 reeskm@…]:

This bug kept occuring despite me setting the portfile to use gcc-4.2 explicitly or using a command line switch of -configure.compiler=apple-gcc-4.2! I was surprised to find that if I set my "port select gcc" back to apple-gcc-4.2 the problem went away.

Then `bison` should be fixed so it [[UsingTheRightCompiler|uses the right compiler]]. -- Ticket URL: <https://trac.macports.org/ticket/27627#comment:7> MacPorts <http://www.macports.org/> Ports system for OS X