[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
undocumented M4 environment variable
From: |
EXCOFFIER, Denis \(CS SYSTEMES INFORMATION\) |
Subject: |
undocumented M4 environment variable |
Date: |
Wed, 23 May 2007 15:01:25 +0200 |
Hello,
I use bison-2.3a and discovered that the bison program reacts at the
environment variable "M4": if it is set, it is supposed to contain a
replacement program for the compiled-in m4.
This is not indicated in the documentation, and i suggest that it must be. That
way, third parties (like maintainers of gcc-4.2.0) would find it a bad idea to
install an environment variable M4="/tmp/.../gcc-4.2.0/missing m4" in the case
where m4 is not present in the $PATH during the build of gcc-4.2.0. Currently,
the result is "Broken Pipe", return code 141, no other explanation available.
By the way, i also suggest that you use the environment variable "BISON_M4"
instead of the very short "M4" for that purpose.
You may find useful to forward this to the gcc-bug list.
Regards.
Denis Excoffier.
This e-mail is intended only for the above addressee. It may contain privileged
information.
If you are not the addressee you must not copy, distribute, disclose or use any
of the information in it.
If you have received it in error please delete it and immediately notify the
sender.
Security Notice: all e-mail, sent to or from this address, may be accessed by
someone other than the recipient, for system management and security reasons.
This access is controlled under Regulation of security reasons.
This access is controlled under Regulation of Investigatory Powers Act 2000,
Lawful Business Practises.
- undocumented M4 environment variable,
EXCOFFIER, Denis \(CS SYSTEMES INFORMATION\) <=