Re: bison and bison2 conflict
On Tue, Feb 07, 2006 at 06:28:13PM -0500, Anthony M. Agelastos wrote: Hello, Basically, I want to have bison and bison2 coexist peacefully on the same machine. I installed math/opendx and it requires bison. Then, I try to install editors/openoffice.org-2.0 and it requires bison2. I get the message: === bison-2.1_1 conflicts with installed package(s): bison-1.75_2,1 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 Ideas? Workarounds? Would something like bison is a build dependency, so once you installed opendx successfully you can just remove it. Kris pgpbgg8IddkjZ.pgp Description: PGP signature
Re: bison and bison2 conflict
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 07, 2006, at 16:56 , Kris Kennaway wrote: On Tue, Feb 07, 2006 at 06:28:13PM -0500, Anthony M. Agelastos wrote: === bison-2.1_1 conflicts with installed package(s): bison-1.75_2,1 bison is a build dependency, so once you installed opendx successfully you can just remove it. It's also worth pointing out that sometime in the mid-term, we'll be running some experimental builds with bison-2.x as the USE_BISON, with the aim to remove the old, crufty, bison-1.75 Not going to happen for a while though, I've got some other large things on my plate right now. - -aDe -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFD6UsOpXS8U0IvffwRAnRqAKCaiqwtP/4LEZvzj9+70lhIA0UGHACdH5uY HrVxeE3+UEHcW00slBxTJHk= =fig6 -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bison
On Fri, Feb 28, 2003 at 08:43:49AM -0600, Jack L. Stone wrote: I know this was discussed many months ago, but I've forgotten what Bison is used for?? 'bison' is the GNU version of 'yacc'. 'yacc' (Yet Another Compiler Compiler) is a massively-useful but evidently forgotten tool for generating parsers. Yacc reads a file containing a BNF-like grammar that describes the syntax of whatever it is that you want to parse, and outputs C code that parses input in that format. For instance, if you wanted to parse timestamps, you might specify the grammar as date_time: date time /* Date and time */ | date /* Just a date, no time */ ; date: NUMBER '/' NUMBER '/' NUMBER/* /MM/DD */ | DAY_ABBR ' ' MON_ABBR ' ' NUMBER /* Mon Jan 13 */ ; time: NUMBER ':' NUMBER ':' NUMBER/* HH:MM:SS */ | NUMBER ':' NUMBER /* HH:MM */ ; Yacc is most often used in conjunction with 'lex' (or the GNU version, 'flex') which reads an input stream recognizes individual tokens (in this example: NUMBER, DAY_ABBR, and MON_ABBR) and feeds them back to Yacc. -- Andrew Arensburger, Systems guy University of Maryland [EMAIL PROTECTED] Office of Information Technology Enter any 12 digit prime number to continue: To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Bison
On Friday 28 February 2003 02:33 am, [EMAIL PROTECTED] wrote: Hi all! I am trying to 'make' the bison port, but it keeps failing. Has anyone experienced this problem? I have retried after cvsup every day this week, so - yes - my sources are up to date. Here's the last bit of the output: === Making all in doc makeinfo --no-split -I . `test -f 'bison.texinfo' || echo './'`bison.texinfo -o bison.info bison.texinfo:37: Unknown command `copying'. bison.texinfo:58: Unmatched [EMAIL PROTECTED]'. bison.texinfo:93: Unknown command `insertcopying'. makeinfo: Removing output file `bison.info' due to errors; use --force to preserve. *** Error code 2 Bison-1.75 needs a texinfo that is only available on FreeBSD-4.7 or later. You either have to upgrade your texinfo to what is on 4.7 or upgrade to 4.7 to use bison-1.75. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Bison
On Friday 28 February 2003 06:43 am, Jack L. Stone wrote: At 06:20 AM 2.28.2003 -0800, Kent Stewart wrote: On Friday 28 February 2003 02:33 am, [EMAIL PROTECTED] wrote: Hi all! I am trying to 'make' the bison port, but it keeps failing. Has anyone experienced this problem? I have retried after cvsup every day this week, so - yes - my sources are up to date. Here's the last bit of the output: === Making all in doc makeinfo --no-split -I . `test -f 'bison.texinfo' || echo './'`bison.texinfo -o bison.info bison.texinfo:37: Unknown command `copying'. bison.texinfo:58: Unmatched [EMAIL PROTECTED]'. bison.texinfo:93: Unknown command `insertcopying'. makeinfo: Removing output file `bison.info' due to errors; use --force to preserve. *** Error code 2 Bison-1.75 needs a texinfo that is only available on FreeBSD-4.7 or later. You either have to upgrade your texinfo to what is on 4.7 or upgrade to 4.7 to use bison-1.75. Kent I know this was discussed many months ago, but I've forgotten what Bison is used for?? I notice it doesn't exist on most of my servers and they all have 4.7. I think it is a finite state machine generator similar to yacc. The port description only talks about it being a file parser. It is a port that is used by a number of other ports during their build process. If it isn't on your systems, then, you haven't built any ports that needed bison. It is only installed on the computer that I use to build packages for use on my other systems. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
