| All Forums |
Register |
Login |
Search |
Subscriptions |
My Profile |
Inbox |
| Tool Warehouse |
FAQs |
Resources |
Help |
Member List |
Address Book |
Logout |
|
|
bison on SUA
|
Logged in as: Guest |
| Users viewing this topic: none |
|
Login  |
|
|
 bison on SUA - Feb. 3, '06, 1:59:11 PM
|
|
|
demyn
Posts: 34
Joined: Jun. 20, '05,
Status: offline
|
Hi ... bison built for 3.5 fails on SUA:
bash-3.00$ bison -d scan.y
Broken pipe
bash-3.00$
I've tried a couple different .y files with the same result. Is this part of a larger compatibility issue? Is there a 5.2 download available? Should I try building bison from source?
Thanks,
Demyn
|
|
|
|
|
RE: bison on SUA - Feb. 6, '06, 2:55:47 AM
|
|
|
Rodney
Posts: 3695
Joined: Jul. 9, '02,
From: /Tools lab
Status: online
|
I see that you are running bash so you must have the fixed utility download
from MS (a fix to the libc 3.5 shared library on 5.2/SUA). So that's good.
Right now everything is available as the 3.5 builds for 5.2.
Most have shown themselves to be working fine in "3.5 backward compatability mode".
What the specific problem is that you've hit I don't know (you're the first to report it).
Is it just when you specify the '-d' option that you get "Broken Pipe"?
There's nothing tricky about building bison. Just a straight "./configure" should do it.
Bison hasn't changed in several years. So it's been stable.
|
|
|
|
|
RE: bison on SUA - Feb. 7, '06, 7:02:57 PM
|
|
|
demyn
Posts: 34
Joined: Jun. 20, '05,
Status: offline
|
It's not the -d option.
I'm trying to build bison from source. ./configure fails -- does this look familiar?
-- thanks in advance, Demyn
...
checking for msgmerge... /usr/local/bin/msgmerge
checking build system type... config/config.guess: unable to guess system type
This script, last modified 2002-12-23, has failed to recognize
the operating system you are using. It is advised that you
download the most up to date version of the config scripts from
ftp://ftp.gnu.org/pub/gnu/config/
If the version you run (config/config.guess) is already up to date, please
send the following data and any information you think might be
pertinent to <config-patches@gnu.org> in order to provide the needed
information to handle your system.
config.guess timestamp = 2002-12-23
uname -m = x86
uname -r = 5.2
uname -s = Interix
uname -v = SP-9.0.3790.2075
/usr/bin/uname -p = Intel_x86_Family15_Model2_Stepping9
/bin/uname -X =
System = Interix
Node = hydra012
Release = 5.2
Version = SP-9.0.3790.2075
Machine = x86
Processor = Intel_x86_Family15_Model2_Stepping9
HostSystem = Windows
HostRelease = 5.2
HostVersion = SP1
hostinfo =
/bin/universe =
/usr/bin/arch -k =
/bin/arch =
/usr/bin/oslevel =
/usr/convex/getsysinfo =
UNAME_MACHINE = x86
UNAME_RELEASE = 5.2
UNAME_SYSTEM = Interix
UNAME_VERSION = SP-9.0.3790.2075
config.sub: too many arguments
Try `config.sub --help' for more information.
configure: error: /bin/sh config/config.sub /dev/fs/L/Programs/VS8/VC/bin/CL.EXE /c /IC:\WINDOWS\SUA\usr\include /GS /no logo /D__OPENNT /D__INTERIX /D_POSIX_ /U_WIN32 /Dunix /D_ALL_SOURCE /D__STDC__ /Fodummy.o C:\WINDOWS\SUA mpbash-3
.00$
bash-3.00$
|
|
|
|
|
RE: bison on SUA - Feb. 7, '06, 7:32:05 PM
|
|
|
jerker_back
Posts: 68
Joined: Jul. 7, '05,
From: Sweden
Status: offline
|
Hi demyn
I didn't have any problems building bison-2.1 (latest from ftp.gnu.org) with gcc. I built GNU make, GNU m4 and flex first though (no /tools 3.5 at all). However, bison built with cc fails in the "synclines" tests (all 5). Why not try to build in the Korn shell? Have you updated the config.guess and config.sub files from GNU config (latest is 2006-01-29)?
> I see that you are running bash so you must have the fixed utility download
> from MS (a fix to the libc 3.5 shared library on 5.2/SUA). So that's good.
?? What's this? You mean the latest SDK from 2006-01-09?
best regards Jerker Bäck
|
|
|
|
|
RE: bison on SUA - Feb. 7, '06, 10:39:18 PM
|
|
|
Rodney
Posts: 3695
Joined: Jul. 9, '02,
From: /Tools lab
Status: online
|
Demyn it appears that you have not installed the "Interix SDK" _and_ the "Interix GNU SDK".
You need to have both installed. Then the configure script will find gcc and use it instead.
To do this just restart the install and you can choose to add just these components without
a full re-installation.
You can choose to built bison 2.1 or you can built 1.875 with a new "config.guess" file.
You can grab a new config.guess from the /Tools ftp site in "/pub".
> ?? What's this? You mean the latest SDK from 2006-01-09?
Yes. Demyn is running on Interix 5.2 with the 3.5 bash package which uses the
shared libraries. It loads the backward-compatable special 3.5 libc for 5.2.
< Message edited by Rodney -- Feb. 8, '06, 1:40:28 PM >
|
|
|
|
|
RE: bison on SUA - Feb. 8, '06, 1:33:53 PM
|
|
|
demyn
Posts: 34
Joined: Jun. 20, '05,
Status: offline
|
## ------------------------------ ##
## All 104 tests were successful. ##
## ------------------------------ ##
:)
A new config.guess solved the ./configure problem. The one on ftp://ftp.interopsystems.com/pub/ did not work, but the one from ftp://ftp.gnu.org/pub/gnu/config/ did. bison built without incident, and the original "Broken Pipe" error from the 3.5 build of bison is gone!
Rodney and Jerker, thank you for your suggestions.
-- Demyn
|
|
|
|
|
RE: bison on SUA - Feb. 8, '06, 3:06:49 PM
|
|
|
jerker_back
Posts: 68
Joined: Jul. 7, '05,
From: Sweden
Status: offline
|
What compiler did you use?
|
|
|
|
|
RE: bison on SUA - Feb. 8, '06, 3:36:58 PM
|
|
|
jerker_back
Posts: 68
Joined: Jul. 7, '05,
From: Sweden
Status: offline
|
By the way, related to bison:
Rodney, any advise about this?
Interix have yacc in /bin
bison installs a script yacc in /usr/local/bin like:
#! /bin/sh
exec /usr/local/bin/bison -y "$@"
Which one to use? Should we disable one of them?
Thanks jerker
|
|
|
|
|
RE: bison on SUA - Feb. 8, '06, 3:49:55 PM
|
|
|
demyn
Posts: 34
Joined: Jun. 20, '05,
Status: offline
|
./configure picked gcc.
Also, I'm no yacc expert, but we do have some code that requires bison.
- demyn
|
|
|
|
|
RE: bison on SUA - Feb. 8, '06, 5:22:10 PM
|
|
|
Rodney
Posts: 3695
Joined: Jul. 9, '02,
From: /Tools lab
Status: online
|
> Which one to use? Should we disable one of them?
I wouldn't disable one of them.
I've always used the one in /bin or the /Tools yacc (same ancestory;
the /Tools version goes into /usr/local/bin as well).
I've not run into anything that needed anything else. Demyn writes
that he has so it may depend on where you drive. For the most-part they both
should be able to process and generate the code.
But if you want to control it, use either the full path or the PATH settings.
|
|
|
|
|
RE: bison on SUA - Feb. 8, '06, 7:01:19 PM
|
|
|
jerker_back
Posts: 68
Joined: Jul. 7, '05,
From: Sweden
Status: offline
|
OK, I just didn't want to have conflicting versions
Strange things happens: I just build GNU sed (needed for GNU coreutils) and it said it used "GNU Bison version 1.28" and compiled the "bison.simple". How could this happen? I have bison-2.1 and bison.simple is renamed yacc.c (I think). This made me confused.
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
|
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
|
|
Printable Version
