| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
and Linux/x86-64 (if /proc/cpuinfo and uname fail)
|
|
|
|
|
|
|
| |
the CPU type, however currently every OS has it set to 'all'. And since
instead it seems I need to specialize on compiler, I've changed
supports_shared to set that, and also changed the Windows config so it
only attempts a DLL build with Visual Studio.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
automatically generated, along with the time, the command line arguments,
the target compiler/CPU, and the enabled modules.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
which is pretty unfriendly. Die with an error instead.
|
|
|
|
|
|
| |
OS/arch/compiler restrictions on the required module, only on the requiree.
Since normally the required module will use a subset of the functionality,
that is probably OK, but something to be aware of.
|
|
|
|
| |
and in readme.txt
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
currently existing variables and the first 60 characters of their
values.
Simplify match_any_of - it just uses it's first two arguments and then
matches against the rest, rather than forcing them to be joined into a
single string (that it would just split and iterate over anyway).
Add support for two new compiler config vars, dll_import_flags and
dll_export_flags
When autoconfig prints that it has guessed something, provide the name
of the variable that can be used to override it.
|
|
|
|
|
| |
whatever the current user/group is. If you wish to override, edit the
makefile or override the INSTALL_CMD_* variables on the command line.
|
| |
|
| |
|
|
|
|
| |
fewer explicit coercions.
|
|
|
|
| |
commonly used options are near the top.
|
|
|
|
|
|
|
|
|
|
| |
Wrap lines a little tighter in the output of --help
Change the order of checks so we don't display that a module was not
used due to use of --no-asm when in fact the module would not run on
the target CPU anyway. Similiarly don't say "loaded only on request" if
it is incompatible with the target, since someone attempting to actually
load the module would immediately get an error.
|
|
|
|
|
| |
compiler. That tends to give the most useful diagnostic output, since
CPU restrictions are the most common in modules.
|
|
|
|
|
|
|
|
|
|
|
| |
use the generic variable reading routines).
Instead of hardcoding the module sets (historically, 'unix', 'beos', and
'win32') into the script, have each module specify which group(s) (if any) it
should be considered a member of in its modinfo.txt file.
Add a new module set compression which contains (currently) the zlib and bzip2
modules.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
--endian=(little|big|none): control processor endianness and override
a default, eg so you can configure for a big-endian Alpha. Use none to
prevent any macros.
--unaligned-mem=(yes|no): control if the unaligned memory macro will
be enabled. Currently this has no effect but there are coming
optimizations which may use it.
--arch-info=<name>: Print some information about that CPU (submodel
names, endian defaults, etc).
|
| |
|
|
|
|
| |
the script is guessing things.
|
|
|
|
|
| |
Don't warn about modules that are only loaded on request when they in
fact have been requested.
|
| |
|
|
|
|
|
| |
All too often this information gets out of of date, so trust the user is
specifying something that makes sense if they use --cc, --cpu, or --os.
|
| |
|
|
|
|
|
| |
since we only need it because of that stupid GCC long long warning,
and that doesn't show up on 64-bit machines.
|
| |
|
|
|
|
|
|
| |
purpose. Relevant information is moved closer to the option description,
for instance the help line for the --cc option also includes the list of
known compilers.
|
|
|
|
|
| |
each individually with --cc, --os, and --cpu. Any that are not specified
on the command line are guessed via the old autoconfiguration logic.
|
|
|
|
| |
hardcoding them into that function.
|
|
|
|
|
|
|
|
| |
binary name, which caused the obvious conflicts.
Spit guess_triple into three independent functions. Make the guessing of
OS depend much more on Perl's $^O variable; only fall back if that is not
recognized.
|
| |
|
|
|
|
|
| |
0 or 1 depending on if the target CPU can handle an unaligned read or
write. This will be true on x86 and x86-64 (are there others?)
|
| |
|
|
|
|
| |
be marked as 1.7.0 at least.
|
|
|
|
|
|
| |
Currently it is only set for x86 and x86-64 as they are two of the few
architectures which are not bi-endian, and we're not doing any detection
(nor is there any way for a user to override the selection yet).
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now three classes are defined: 'request', 'auto', and 'asm_ok'. The 'auto'
class is loaded automatically if the platform support matches up with
what we are building for (this is the former default). The 'request' mode
means it is only loaded if specifically requested by name. The 'asm_ok'
module is marked for all modules that use any assembler (including inline
assembler). This normally functions like 'auto', unless --debug is passed
to configure, in which case it is treated as 'request'.
Modules which do not specify a load behavior are given a default of
'request'.
|
| |
|