mirror of
https://git.FreeBSD.org/ports.git
synced 2024-11-24 00:45:52 +00:00
The latest Bison is now in the base system (and has been for a while).
This port is no longer needed.
This commit is contained in:
David E. O'Brien
parent
c4aa1a08ac
commit
041e34d028
Notes:
svn2git
2021-03-31 03:12:20 +00:00
svn path=/head/; revision=22200
@ -1,28 +0,0 @@
|
||||
# New ports collection makefile for: bison
|
||||
# Version required: 1.28
|
||||
# Date created: 27 Mar 1999
|
||||
# Whom: Jerry Hicks
|
||||
#
|
||||
# $FreeBSD$
|
||||
#
|
||||
|
||||
DISTNAME= bison-1.28
|
||||
CATEGORIES= devel
|
||||
MASTER_SITES= ${MASTER_SITE_GNU}
|
||||
MASTER_SITE_SUBDIR= bison
|
||||
|
||||
MAINTAINER= wghicks@bellsouth.net
|
||||
|
||||
Y2K= http://www.gnu.org/software/year2000.html
|
||||
|
||||
GNU_CONFIGURE= yes
|
||||
|
||||
MAN1= bison.1
|
||||
|
||||
post-install:
|
||||
@if [ ! -f ${PREFIX}/info/dir ]; then \
|
||||
${SED} -ne '1,/Menu:/p' \/usr\/share\/info/dir > ${PREFIX}/info/dir; \
|
||||
fi
|
||||
@install-info ${PREFIX}/info/bison.info ${PREFIX}/info/dir
|
||||
|
||||
.include <bsd.port.mk>
|
||||
@ -1 +0,0 @@
|
||||
MD5 (bison-1.28.tar.gz) = 4afb3989f2270043c47c3daa1fa7ffab
|
||||
@ -1 +0,0 @@
|
||||
A parser generator from FSF, (mostly) compatible with Yacc
|
||||
@ -1,22 +0,0 @@
|
||||
Bison is a tool used to write parsers, such as the parser for GNU cc.
|
||||
It is similar to Yacc, which is included in the base FreeBSD system.
|
||||
|
||||
The main difference between Bison and Yacc that I know of is that
|
||||
Bison supports the @N construction, which gives you access to
|
||||
the starting and ending line number and character number associated
|
||||
with any of the symbols in the current rule.
|
||||
|
||||
Also, Bison supports the command `%expect N' which says not to mention
|
||||
the conflicts if there are N shift/reduce conflicts and no reduce/reduce
|
||||
conflicts.
|
||||
|
||||
The differences in the algorithms stem mainly from the horrible
|
||||
kludges that Johnson had to perpetrate to make Yacc fit in a PDP-11.
|
||||
|
||||
Also, Bison uses a faster but less space-efficient encoding for the
|
||||
parse tables (see Corbett's PhD thesis from Berkeley, "Static
|
||||
Semantics in Compiler Error Recovery", June 1985, Report No. UCB/CSD
|
||||
85/251), and more modern technique for generating the lookahead sets.
|
||||
(See "Efficient Construction of LALR(1) Lookahead Sets" by F. DeRemer
|
||||
and A. Pennello, in ACM TOPLS Vol 4 No 4, October 1982. Their
|
||||
technique is the standard one now.)
|
||||
@ -1,9 +0,0 @@
|
||||
bin/bison
|
||||
share/bison.hairy
|
||||
share/bison.simple
|
||||
@unexec install-info --delete %D/info/bison.info %D/info/dir
|
||||
info/bison.info
|
||||
share/locale/de/LC_MESSAGES/bison.mo
|
||||
share/locale/es/LC_MESSAGES/bison.mo
|
||||
share/locale/fr/LC_MESSAGES/bison.mo
|
||||
share/locale/nl/LC_MESSAGES/bison.mo
|
||||
@ -1,28 +0,0 @@
|
||||
# New ports collection makefile for: bison
|
||||
# Version required: 1.28
|
||||
# Date created: 27 Mar 1999
|
||||
# Whom: Jerry Hicks
|
||||
#
|
||||
# $FreeBSD$
|
||||
#
|
||||
|
||||
DISTNAME= bison-1.28
|
||||
CATEGORIES= devel
|
||||
MASTER_SITES= ${MASTER_SITE_GNU}
|
||||
MASTER_SITE_SUBDIR= bison
|
||||
|
||||
MAINTAINER= wghicks@bellsouth.net
|
||||
|
||||
Y2K= http://www.gnu.org/software/year2000.html
|
||||
|
||||
GNU_CONFIGURE= yes
|
||||
|
||||
MAN1= bison.1
|
||||
|
||||
post-install:
|
||||
@if [ ! -f ${PREFIX}/info/dir ]; then \
|
||||
${SED} -ne '1,/Menu:/p' \/usr\/share\/info/dir > ${PREFIX}/info/dir; \
|
||||
fi
|
||||
@install-info ${PREFIX}/info/bison.info ${PREFIX}/info/dir
|
||||
|
||||
.include <bsd.port.mk>
|
||||
@ -1 +0,0 @@
|
||||
MD5 (bison-1.28.tar.gz) = 4afb3989f2270043c47c3daa1fa7ffab
|
||||
@ -1 +0,0 @@
|
||||
A parser generator from FSF, (mostly) compatible with Yacc
|
||||
@ -1,22 +0,0 @@
|
||||
Bison is a tool used to write parsers, such as the parser for GNU cc.
|
||||
It is similar to Yacc, which is included in the base FreeBSD system.
|
||||
|
||||
The main difference between Bison and Yacc that I know of is that
|
||||
Bison supports the @N construction, which gives you access to
|
||||
the starting and ending line number and character number associated
|
||||
with any of the symbols in the current rule.
|
||||
|
||||
Also, Bison supports the command `%expect N' which says not to mention
|
||||
the conflicts if there are N shift/reduce conflicts and no reduce/reduce
|
||||
conflicts.
|
||||
|
||||
The differences in the algorithms stem mainly from the horrible
|
||||
kludges that Johnson had to perpetrate to make Yacc fit in a PDP-11.
|
||||
|
||||
Also, Bison uses a faster but less space-efficient encoding for the
|
||||
parse tables (see Corbett's PhD thesis from Berkeley, "Static
|
||||
Semantics in Compiler Error Recovery", June 1985, Report No. UCB/CSD
|
||||
85/251), and more modern technique for generating the lookahead sets.
|
||||
(See "Efficient Construction of LALR(1) Lookahead Sets" by F. DeRemer
|
||||
and A. Pennello, in ACM TOPLS Vol 4 No 4, October 1982. Their
|
||||
technique is the standard one now.)
|
||||
@ -1,9 +0,0 @@
|
||||
bin/bison
|
||||
share/bison.hairy
|
||||
share/bison.simple
|
||||
@unexec install-info --delete %D/info/bison.info %D/info/dir
|
||||
info/bison.info
|
||||
share/locale/de/LC_MESSAGES/bison.mo
|
||||
share/locale/es/LC_MESSAGES/bison.mo
|
||||
share/locale/fr/LC_MESSAGES/bison.mo
|
||||
share/locale/nl/LC_MESSAGES/bison.mo
|
||||
@ -1,28 +0,0 @@
|
||||
# New ports collection makefile for: bison
|
||||
# Version required: 1.28
|
||||
# Date created: 27 Mar 1999
|
||||
# Whom: Jerry Hicks
|
||||
#
|
||||
# $FreeBSD$
|
||||
#
|
||||
|
||||
DISTNAME= bison-1.28
|
||||
CATEGORIES= devel
|
||||
MASTER_SITES= ${MASTER_SITE_GNU}
|
||||
MASTER_SITE_SUBDIR= bison
|
||||
|
||||
MAINTAINER= wghicks@bellsouth.net
|
||||
|
||||
Y2K= http://www.gnu.org/software/year2000.html
|
||||
|
||||
GNU_CONFIGURE= yes
|
||||
|
||||
MAN1= bison.1
|
||||
|
||||
post-install:
|
||||
@if [ ! -f ${PREFIX}/info/dir ]; then \
|
||||
${SED} -ne '1,/Menu:/p' \/usr\/share\/info/dir > ${PREFIX}/info/dir; \
|
||||
fi
|
||||
@install-info ${PREFIX}/info/bison.info ${PREFIX}/info/dir
|
||||
|
||||
.include <bsd.port.mk>
|
||||
@ -1 +0,0 @@
|
||||
MD5 (bison-1.28.tar.gz) = 4afb3989f2270043c47c3daa1fa7ffab
|
||||
@ -1 +0,0 @@
|
||||
A parser generator from FSF, (mostly) compatible with Yacc
|
||||
@ -1,22 +0,0 @@
|
||||
Bison is a tool used to write parsers, such as the parser for GNU cc.
|
||||
It is similar to Yacc, which is included in the base FreeBSD system.
|
||||
|
||||
The main difference between Bison and Yacc that I know of is that
|
||||
Bison supports the @N construction, which gives you access to
|
||||
the starting and ending line number and character number associated
|
||||
with any of the symbols in the current rule.
|
||||
|
||||
Also, Bison supports the command `%expect N' which says not to mention
|
||||
the conflicts if there are N shift/reduce conflicts and no reduce/reduce
|
||||
conflicts.
|
||||
|
||||
The differences in the algorithms stem mainly from the horrible
|
||||
kludges that Johnson had to perpetrate to make Yacc fit in a PDP-11.
|
||||
|
||||
Also, Bison uses a faster but less space-efficient encoding for the
|
||||
parse tables (see Corbett's PhD thesis from Berkeley, "Static
|
||||
Semantics in Compiler Error Recovery", June 1985, Report No. UCB/CSD
|
||||
85/251), and more modern technique for generating the lookahead sets.
|
||||
(See "Efficient Construction of LALR(1) Lookahead Sets" by F. DeRemer
|
||||
and A. Pennello, in ACM TOPLS Vol 4 No 4, October 1982. Their
|
||||
technique is the standard one now.)
|
||||
@ -1,9 +0,0 @@
|
||||
bin/bison
|
||||
share/bison.hairy
|
||||
share/bison.simple
|
||||
@unexec install-info --delete %D/info/bison.info %D/info/dir
|
||||
info/bison.info
|
||||
share/locale/de/LC_MESSAGES/bison.mo
|
||||
share/locale/es/LC_MESSAGES/bison.mo
|
||||
share/locale/fr/LC_MESSAGES/bison.mo
|
||||
share/locale/nl/LC_MESSAGES/bison.mo
|
||||
@ -1,28 +0,0 @@
|
||||
# New ports collection makefile for: bison
|
||||
# Version required: 1.28
|
||||
# Date created: 27 Mar 1999
|
||||
# Whom: Jerry Hicks
|
||||
#
|
||||
# $FreeBSD$
|
||||
#
|
||||
|
||||
DISTNAME= bison-1.28
|
||||
CATEGORIES= devel
|
||||
MASTER_SITES= ${MASTER_SITE_GNU}
|
||||
MASTER_SITE_SUBDIR= bison
|
||||
|
||||
MAINTAINER= wghicks@bellsouth.net
|
||||
|
||||
Y2K= http://www.gnu.org/software/year2000.html
|
||||
|
||||
GNU_CONFIGURE= yes
|
||||
|
||||
MAN1= bison.1
|
||||
|
||||
post-install:
|
||||
@if [ ! -f ${PREFIX}/info/dir ]; then \
|
||||
${SED} -ne '1,/Menu:/p' \/usr\/share\/info/dir > ${PREFIX}/info/dir; \
|
||||
fi
|
||||
@install-info ${PREFIX}/info/bison.info ${PREFIX}/info/dir
|
||||
|
||||
.include <bsd.port.mk>
|
||||
@ -1 +0,0 @@
|
||||
MD5 (bison-1.28.tar.gz) = 4afb3989f2270043c47c3daa1fa7ffab
|
||||
@ -1 +0,0 @@
|
||||
A parser generator from FSF, (mostly) compatible with Yacc
|
||||
@ -1,22 +0,0 @@
|
||||
Bison is a tool used to write parsers, such as the parser for GNU cc.
|
||||
It is similar to Yacc, which is included in the base FreeBSD system.
|
||||
|
||||
The main difference between Bison and Yacc that I know of is that
|
||||
Bison supports the @N construction, which gives you access to
|
||||
the starting and ending line number and character number associated
|
||||
with any of the symbols in the current rule.
|
||||
|
||||
Also, Bison supports the command `%expect N' which says not to mention
|
||||
the conflicts if there are N shift/reduce conflicts and no reduce/reduce
|
||||
conflicts.
|
||||
|
||||
The differences in the algorithms stem mainly from the horrible
|
||||
kludges that Johnson had to perpetrate to make Yacc fit in a PDP-11.
|
||||
|
||||
Also, Bison uses a faster but less space-efficient encoding for the
|
||||
parse tables (see Corbett's PhD thesis from Berkeley, "Static
|
||||
Semantics in Compiler Error Recovery", June 1985, Report No. UCB/CSD
|
||||
85/251), and more modern technique for generating the lookahead sets.
|
||||
(See "Efficient Construction of LALR(1) Lookahead Sets" by F. DeRemer
|
||||
and A. Pennello, in ACM TOPLS Vol 4 No 4, October 1982. Their
|
||||
technique is the standard one now.)
|
||||
@ -1,9 +0,0 @@
|
||||
bin/bison
|
||||
share/bison.hairy
|
||||
share/bison.simple
|
||||
@unexec install-info --delete %D/info/bison.info %D/info/dir
|
||||
info/bison.info
|
||||
share/locale/de/LC_MESSAGES/bison.mo
|
||||
share/locale/es/LC_MESSAGES/bison.mo
|
||||
share/locale/fr/LC_MESSAGES/bison.mo
|
||||
share/locale/nl/LC_MESSAGES/bison.mo
|
||||
@ -1,28 +0,0 @@
|
||||
# New ports collection makefile for: bison
|
||||
# Version required: 1.28
|
||||
# Date created: 27 Mar 1999
|
||||
# Whom: Jerry Hicks
|
||||
#
|
||||
# $FreeBSD$
|
||||
#
|
||||
|
||||
DISTNAME= bison-1.28
|
||||
CATEGORIES= devel
|
||||
MASTER_SITES= ${MASTER_SITE_GNU}
|
||||
MASTER_SITE_SUBDIR= bison
|
||||
|
||||
MAINTAINER= wghicks@bellsouth.net
|
||||
|
||||
Y2K= http://www.gnu.org/software/year2000.html
|
||||
|
||||
GNU_CONFIGURE= yes
|
||||
|
||||
MAN1= bison.1
|
||||
|
||||
post-install:
|
||||
@if [ ! -f ${PREFIX}/info/dir ]; then \
|
||||
${SED} -ne '1,/Menu:/p' \/usr\/share\/info/dir > ${PREFIX}/info/dir; \
|
||||
fi
|
||||
@install-info ${PREFIX}/info/bison.info ${PREFIX}/info/dir
|
||||
|
||||
.include <bsd.port.mk>
|
||||
@ -1 +0,0 @@
|
||||
MD5 (bison-1.28.tar.gz) = 4afb3989f2270043c47c3daa1fa7ffab
|
||||
@ -1 +0,0 @@
|
||||
A parser generator from FSF, (mostly) compatible with Yacc
|
||||
@ -1,22 +0,0 @@
|
||||
Bison is a tool used to write parsers, such as the parser for GNU cc.
|
||||
It is similar to Yacc, which is included in the base FreeBSD system.
|
||||
|
||||
The main difference between Bison and Yacc that I know of is that
|
||||
Bison supports the @N construction, which gives you access to
|
||||
the starting and ending line number and character number associated
|
||||
with any of the symbols in the current rule.
|
||||
|
||||
Also, Bison supports the command `%expect N' which says not to mention
|
||||
the conflicts if there are N shift/reduce conflicts and no reduce/reduce
|
||||
conflicts.
|
||||
|
||||
The differences in the algorithms stem mainly from the horrible
|
||||
kludges that Johnson had to perpetrate to make Yacc fit in a PDP-11.
|
||||
|
||||
Also, Bison uses a faster but less space-efficient encoding for the
|
||||
parse tables (see Corbett's PhD thesis from Berkeley, "Static
|
||||
Semantics in Compiler Error Recovery", June 1985, Report No. UCB/CSD
|
||||
85/251), and more modern technique for generating the lookahead sets.
|
||||
(See "Efficient Construction of LALR(1) Lookahead Sets" by F. DeRemer
|
||||
and A. Pennello, in ACM TOPLS Vol 4 No 4, October 1982. Their
|
||||
technique is the standard one now.)
|
||||
@ -1,9 +0,0 @@
|
||||
bin/bison
|
||||
share/bison.hairy
|
||||
share/bison.simple
|
||||
@unexec install-info --delete %D/info/bison.info %D/info/dir
|
||||
info/bison.info
|
||||
share/locale/de/LC_MESSAGES/bison.mo
|
||||
share/locale/es/LC_MESSAGES/bison.mo
|
||||
share/locale/fr/LC_MESSAGES/bison.mo
|
||||
share/locale/nl/LC_MESSAGES/bison.mo
|
||||
@ -1,28 +0,0 @@
|
||||
# New ports collection makefile for: bison
|
||||
# Version required: 1.28
|
||||
# Date created: 27 Mar 1999
|
||||
# Whom: Jerry Hicks
|
||||
#
|
||||
# $FreeBSD$
|
||||
#
|
||||
|
||||
DISTNAME= bison-1.28
|
||||
CATEGORIES= devel
|
||||
MASTER_SITES= ${MASTER_SITE_GNU}
|
||||
MASTER_SITE_SUBDIR= bison
|
||||
|
||||
MAINTAINER= wghicks@bellsouth.net
|
||||
|
||||
Y2K= http://www.gnu.org/software/year2000.html
|
||||
|
||||
GNU_CONFIGURE= yes
|
||||
|
||||
MAN1= bison.1
|
||||
|
||||
post-install:
|
||||
@if [ ! -f ${PREFIX}/info/dir ]; then \
|
||||
${SED} -ne '1,/Menu:/p' \/usr\/share\/info/dir > ${PREFIX}/info/dir; \
|
||||
fi
|
||||
@install-info ${PREFIX}/info/bison.info ${PREFIX}/info/dir
|
||||
|
||||
.include <bsd.port.mk>
|
||||
@ -1 +0,0 @@
|
||||
MD5 (bison-1.28.tar.gz) = 4afb3989f2270043c47c3daa1fa7ffab
|
||||
@ -1 +0,0 @@
|
||||
A parser generator from FSF, (mostly) compatible with Yacc
|
||||
@ -1,22 +0,0 @@
|
||||
Bison is a tool used to write parsers, such as the parser for GNU cc.
|
||||
It is similar to Yacc, which is included in the base FreeBSD system.
|
||||
|
||||
The main difference between Bison and Yacc that I know of is that
|
||||
Bison supports the @N construction, which gives you access to
|
||||
the starting and ending line number and character number associated
|
||||
with any of the symbols in the current rule.
|
||||
|
||||
Also, Bison supports the command `%expect N' which says not to mention
|
||||
the conflicts if there are N shift/reduce conflicts and no reduce/reduce
|
||||
conflicts.
|
||||
|
||||
The differences in the algorithms stem mainly from the horrible
|
||||
kludges that Johnson had to perpetrate to make Yacc fit in a PDP-11.
|
||||
|
||||
Also, Bison uses a faster but less space-efficient encoding for the
|
||||
parse tables (see Corbett's PhD thesis from Berkeley, "Static
|
||||
Semantics in Compiler Error Recovery", June 1985, Report No. UCB/CSD
|
||||
85/251), and more modern technique for generating the lookahead sets.
|
||||
(See "Efficient Construction of LALR(1) Lookahead Sets" by F. DeRemer
|
||||
and A. Pennello, in ACM TOPLS Vol 4 No 4, October 1982. Their
|
||||
technique is the standard one now.)
|
||||
@ -1,9 +0,0 @@
|
||||
bin/bison
|
||||
share/bison.hairy
|
||||
share/bison.simple
|
||||
@unexec install-info --delete %D/info/bison.info %D/info/dir
|
||||
info/bison.info
|
||||
share/locale/de/LC_MESSAGES/bison.mo
|
||||
share/locale/es/LC_MESSAGES/bison.mo
|
||||
share/locale/fr/LC_MESSAGES/bison.mo
|
||||
share/locale/nl/LC_MESSAGES/bison.mo
|
||||
Loading…
Reference in New Issue
Block a user