Tru64 and 2.2 problems

Ken Murchison ken at
Thu Jul 24 15:59:45 EDT 2003

Scott Adkins wrote:

> --On Thursday, July 24, 2003 2:56 PM -0400 Ken Murchison 
> <ken at> wrote:
>> Scott Adkins wrote:
>>> Even though your suggestions were good, they weren't applicable to this
>>> particular issue.  In fact, running the find command to find all the
>>> source files with indented directives only showed up a couple lines as
>>> follows (using a slightly different command than you supplied):
>>>  % find . -name '*.[ch]' | xargs egrep '^[: :]+#'
>>>  ./sieve/addr-lex.c: #pragma warn -rch
>>>  ./sieve/addr-lex.c: #pragma warn -use
>>>  ./sieve/sieve-lex.c: #pragma warn -rch
>>>  ./sieve/sieve-lex.c: #pragma warn -use
>>> Even though it has no bearing on the problem I was having, it is worth
>>> fixing those few lines (by removing the single space before the #pragma)
>>> just to increase the portability of the source code.
>> These files are generated by flex, and I don't think we want to get into
>> massaging its output.  Are you saying that the leading space is illegal,
>> or that your compiler just doesn't like it?
> Well, I looked at those files and thought they would be generated by flex,
> but when I untarred the distribution, they were already there.  Are they
> recreated on the fly, or are the ones provided in the distribution used?

They are included in the distribution so that you don't need flex and 
yacc.  If you use CVS, then these will be built on the fly.

Kenneth Murchison     Oceana Matrix Ltd.
Software Engineer     21 Princeton Place
716-662-8973 x26      Orchard Park, NY 14127
--PGP Public Key--

More information about the Info-cyrus mailing list