Re: bison error on OSX: "error_one_per_line" (?)

[Akim Demaille]

| i don't understand your comment "but it is not the same version as the
| usual one" .... which version of what?

error_at_line comes from the GNU Lib C.

| and the relevant info from config.log is (fail on check):
| 
| configure:16667: checking for error_at_line
| configure:16691: cc -o conftest -O3 -L/System/Library/Frameworks
| -L/usr/lib -L/usr/local/lib -L/usr/X11R6/lib
| -L/usr/local/BerkeleyDB/lib
| 
|         -fno-common -fno-rtti -fno-strict-aliasing
|         -I/System/Library/Frameworks -I/usr/local/include
|         -I/usr/X11R6/include
| 
|         -I/usr/local/BerkeleyDB/include -L/System/Library/Frameworks
|         -L/usr/lib -L/usr/local/lib -L/usr/X11R6/lib
|         -L/usr/local/BerkeleyDB/lib conftest.c  >&5
| 
| /usr/bin/ld: Undefined symbols:
| _error_at_line
| configure:16694: $? = 1
| configure: failed program was:
| #line 16672 "configure"
| #include "confdefs.h"
| 
| #ifdef F77_DUMMY_MAIN
| #  ifdef __cplusplus
|      extern "C"
| #  endif
|    int F77_DUMMY_MAIN() { return 1; }
| #endif
| int
| main ()
| {
| error_at_line (0, 0, "", 0, "");
|   ;
|   return 0;
| }
| configure:16710: result: no
| 
| and, after make install, bison --version NO LONGER gives me an error .....

Still, I need to see the traces *before* you changed configure.