Software: Apache/2.4.41 (Ubuntu). PHP/8.0.30 

uname -a: Linux apirnd 5.4.0-204-generic #224-Ubuntu SMP Thu Dec 5 13:38:28 UTC 2024 x86_64 

uid=33(www-data) gid=33(www-data) groups=33(www-data) 

Safe-mode: OFF (not secure)

/usr/share/doc/autogen/autogen.html/   drwxr-xr-x
Free 13.4 GB of 57.97 GB (23.11%)
                            Encoder    Tools    Proc.    FTP brute    Sec.    SQL    PHP-code    Update    Self remove    Logout    

Viewing file:     Naming-Conflicts.html (4.16 KB)      -rw-r--r--

7.17 Naming Conflicts

AutoOpts generates a header file that contains many C preprocessing macros and several external names. For the most part, they begin with either opt_ or option, or else they end with _opt. If this happens to conflict with other macros you are using, or if you are compiling multiple option sets in the same compilation unit, the conflicts can be avoided. You may specify an external name prefix (see program attributes) for all of the names generated for each set of option definitions.

Among these macros, several take an option name as a macro argument. Sometimes, this will inconveniently conflict. For example, if you specify an option named, debug, the emitted code will presume that DEBUG is not a preprocessing name. Or also, if you are building on a Windows platform, you may find that MicroSoft has usurped a number of user space names in its header files. Consequently, you will get a preprocessing error if you use, for example, HAVE_OPT(DEBUG) or HAVE_OPT(INTERNAL) (see HAVE_OPT) in your code. You may trigger an obvious warning for such conflicts by specifying the guard-option-names attribute (see program attributes). That emitted code will also #undef-ine the conflicting name.