[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bison error on OSX: "error_one_per_line" (?)
From: |
Akim Demaille |
Subject: |
Re: bison error on OSX: "error_one_per_line" (?) |
Date: |
01 Jul 2002 17:15:06 +0200 |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Honest Recruiter) |
>>>>> "R" == R Blake <R> writes:
R> hi, hmmmm........
R> well i *tried* running nm on error.o, only to find that,
R> unfortunately, error.o is not created! here's the dir ls after my
R> 'successful' make ....
R> address@hidden /Volumes/ServerSystem/ports/bison-1.49a/lib
R> Makefile bitset.o getopt.c libbison.a quotearg.h strspn.c
R> Makefile.am bitsetv.c getopt.h malloc.c quotearg.o tempname.c
R> Makefile.in bitsetv.h getopt.o memchr.c readpipe.c xalloc.h
R> alloca.c bitsetv.o getopt1.c memrchr.c readpipe.o xmalloc.c
R> ansi2knr.1 dirname.c getopt1.o mkstemp.c realloc.c xmalloc.o
R> ansi2knr.c dirname.h gettext.h obstack.c sbitset.c xstrdup.c
R> basename.c dirname.o hash.c obstack.h sbitset.h xstrdup.o
R> basename.o ebitset.c hash.h obstack.o sbitset.o xstrndup.c
R> bbitset.h ebitset.h hash.o quote.c stpcpy.c xstrndup.o bitset-int.h
R> ebitset.o lbitset.c quote.h strchr.c bitset.c error.c lbitset.h
R> quote.o strnlen.c bitset.h error.h lbitset.o quotearg.c strnlen.o
R> wondering if, perhaps, i'd accidentally deleted it (not likeley,
R> tho) i started over with a clean dist & make. There's still no
R> error.o! (full make session below ....)
R> a quick check shows that there's no reference to error.c in
R> ./Makefile, but that there *is* in ./libs/Makefile.in, and that
R> Makefile does pick up the reference in the "ac_config_files=" def'n
R> .....
R> am i missing something here?
Yep: the CC to bug-bison.
Other than that, I am the one who missed an important point: we
compile this file only when needed, and it appears it is not `needed'
on your platform, but it is not the same version as the usual one,
since it does not seem to provide `error_one_per_line'. That's weird.
Do you have a `man error_at_line' or something? Could you also look
for `error_at_line' in config.log? I have this on my machine:
configure:5418: checking for error_at_line
configure:5442: gcc -o conftest -g -O2 conftest.c >&5
configure:5445: $? = 0
configure:5448: test -s conftest
configure:5451: $? = 0
configure:5461: result: yes