Le Mercredi 19 Avril 2006 15:20, Dan Nicholson a écrit :

> Hi David,
>
> It does indeed look like there is some issue with flex or bison are
> being invoked.  However, I'd like to ask a favor.  I realize this is
> incredibly hypocritical, but could you set LC_ALL=C during the build?
> I can't understand the output above.

Hi ! Thanks for your answer... Of course, I can set LC_ALL=C, but I can also 
translate the above messages, which should be faster than re-compiling the 
whole thing !
The first says :

/usr/share/misc/bison.simple:164:5:  warning : "YYMAXDEPTH" is not defined
In file included from mcopidl.all_cc.cc:4:
scanner.cc:743:5: warning : « YY_STACK_USED » is not defined
scanner.cc:1783:5: warning : « YY_ALWAYS_INTERACTIVE » is not defined
scanner.cc:2077:5: warning : « YY_MAIN » is not defined
scanner.cc:2056: warning : « void* yy_flex_realloc(void*, yy_size_t) » is 
defined but has never been used.

The second one claims :
In file included from dcopidl.all_cc.cc:3:
scanner.cc:966:5: warning : « YY_STACK_USED » is not defined
scanner.cc:2200:5: warning : « YY_ALWAYS_INTERACTIVE » is not defined
scanner.cc:2494:5: warning : « YY_MAIN » is not defined
scanner.cc:2473: warning : « void* yy_flex_realloc(void*, yy_size_t) » is 
defined but has never been used

Hope this helps.
I forgot to say in my previous message that I had a strange message 
complaining that there was an error in file /usr/share/misc/bison.simple
So I investigated on this and could find this file anywhere on my system. So I 
went on ftp.gnu.org and had a look at all archives related to bison. It seems 
that this file, and /usr/share/misc/bison.hairy are not provided anymore 
since version 1.35. I've picked both files from the bison1.35 archive, but it 
doesn't solve the problem...
Thanks for your help.
>
> Thanks,
>
> --
> Dan

Attachment: pgpzijWuYmoTF.pgp
Description: PGP signature

-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to