summaryrefslogtreecommitdiff
path: root/win32
Commit message (Collapse)AuthorAgeFilesLines
* Fix spelling: precedeFelipe Gasper2021-06-151-1/+1
|
* Configure: apply recent metaconfig changesKarl Williamson2021-06-122-0/+8
| | | | Several new probes have been added.
* Configure changes for HAS_NON_INT_BITFIELDSKarl Williamson2021-06-122-0/+2
| | | | | | | | | | | This probe has been available without my realizing it had been merged. Some compilers, chiefly IBM, use only integer-size bitfields, warning when presented with other-sized ones. Allowing other-sized fields is an extension to the C standard. These warnings don't affect the correctness of the code generated, but very many are generated per run, potentially overwhelming the reader into not noticing warnings that are important.
* replace all instances of PERL_IMPLICIT_CONTEXT with MULTIPLICITYTomasz Konojacki2021-06-092-2/+2
| | | | | | | | | | | | Since the removal of PERL_OBJECT (acfe0abcedaf592fb4b9cb69ce3468308ae99d91) PERL_IMPLICIT_CONTEXT and MULTIPLICITY have been synonymous and they're being used interchangeably. To simplify the code, this commit replaces all instances of PERL_IMPLICIT_CONTEXT with MULTIPLICITY. PERL_IMPLICIT_CONTEXT will stay defined for compatibility with XS modules.
* Bump the perl version in various places for 5.35.1Max Maischein2021-05-232-2/+2
| | | | | Ideally, this would've been done earlier in the process of developing 5.35, but here we are
* perldelta: add a new delta for v5.35.1Ricardo Signes2021-05-203-4/+8
|
* New perldeltaSawyer X2021-05-213-4/+8
|
* Bump to 5.35.0:Sawyer X2021-05-212-18/+18
| | | | | | * Apparently, first you bump, then you update perldelta. * 5.35.0 *might* be released tomorrow (likely) but not certainly. * I've set it to tomorrow so Module::CoreList won't be upset.
* set -fwrapv on by default unconditionallyTony Cook2021-05-141-2/+3
| | | | | | | | | This was broken on gcc 10, and we want -fwrapv for all versions of gcc that we support. We also want a developer to be able to disable it easily (GCCWRAPV=undef) so it remains a flag rather than hard-coding -frwapv below.
* Merge all perldelta files to create perl534delta.podSawyer X2021-05-043-48/+8
|
* Bump perl version in various places for 5.34.0Sawyer X2021-05-042-18/+18
|
* new perldelta for 5.33.10Todd Rinaldo2021-04-203-4/+8
| | | | | 5.33.10 isn't going to happen but it looks like we bump to the bogus release and THEN switch to RC1.
* win32.c: make reading UTF-8 characters from the console possibleTomasz Konojacki2021-04-141-1/+125
| | | | | | | | | | | | | Due to a bug in Windows, ReadFile() and ReadConsoleA() (and thus _read()), return zeros instead of non-ASCII characters when the console codepage is set to 65001. See this ticket for more details: https://github.com/microsoft/terminal/issues/4551 This commit works around that bug by using ReadConsoleW() inside win32_read() when the passed fd points to the console and the console codepage is set to 65001. Fixes #18701
* Bump the Perl version to 5.33.9Nicolas R2021-03-202-2/+2
|
* new perldelta for 5.33.9Nicolas R2021-03-203-4/+8
|
* bump version to 5.33.8reneeb2021-02-202-2/+2
|
* add new perldelta for 5.33.8reneeb2021-02-203-4/+8
|
* Set $Config{libpth} properly for MinGW buildsTomasz Konojacki2021-01-301-6/+10
| | | | | | | | | | | | | | | | | | | | | | Previously the default libpth consisted of just a single folder and failed to include the directory that contains the majority of the libraries. This is a fairly important issue but no one noticed it for two reasons: 1. EU::MM on Windows *always* links XS modules with the libraries from $Config{libs}, so you'd notice that linking doesn't work only if you needed a library that isn't listed there. 2. Strawberry Perl has a workaround for this issue[1]. I'm only using MinGW-w64 compilers, so I have no idea how library paths work on MinGW.org builds. It's possible that the previous libpth worked fine with them. Either way, this commit only adds new paths to libpth, it doesn't modify the one that was already there, so it's unlikely it will break anything. [1] - https://github.com/StrawberryPerl/Perl-Dist-Strawberry/blob/2112b8a590882e913e98e4aa2dced4f34c4fea79/lib/Perl/Dist/Strawberry/Step/InstallPerlCore.pm#L136
* win32: remove makefile.mk (#18511)xenu2021-01-282-1962/+1
| | | | | | | | | Makefile.mk is redundant with GNUmakefile. See https://www.nntp.perl.org/group/perl.perl5.porters/2021/01/msg258848.html for more details. We planned to remove it shortly after the introduction of GNUmakefile but that slipped through the cracks for some reason: https://github.com/Perl/perl5/issues/14341
* Restore build with some mingw.org compilers using mingw runtimes >= 3.21Steve Hay2021-01-264-4/+8
| | | | | | | | | | | | | | | | | | | | | | | MinGW runtime version 3.21 added a definition of mkstemp(), so requires a fix similar to f33b2f5852 for MinGW-w64's runtime 4.0 onwards. Based on a patch by Dan Collins on GH#15446. This commit also tweaks 43b3b04375, having discovered that mingw runtime 3.22 also contains a definition of timespec. For me, this fixes the build with my mingw.org 5.3.0 compiler using any of the mingw runtimes 3.21, 3.22.4 or 5.0 without breaking older versions such as 4.9.3 with the 3.20 runtime (or even with the withdrawn 4.0.3 runtime, which had __MINGW32_MAJOR/MINOR_VERSION set to 3.20 whilst adding new a __MINGW_MAJOR/MINOR_VERSION set to 4.0). However, 6.3.0 and 7.3.0 have other issues when compiling win32sck.c, while 8.2.0 and 9.2.0 have other issues again when compiling win32.c. See GH#18510 for more details. Also, C++ mode builds with some MinGW/MinGW-w64 compilers are still broken, as documented in 8a217c9aa7. See GH#16459 for more details.
* Import perl5321delta.podSteve Hay2021-01-231-0/+4
|
* Bump version to 5.33.7Richard Leach2021-01-213-3/+3
|
* New perldelta for 5.33.7Richard Leach2021-01-214-6/+10
|
* style: Detabify indentation of the C code maintained by the core.Michael G. Schwern2021-01-1714-2790/+2790
| | | | | | | | | | | This just detabifies to get rid of the mixed tab/space indentation. Applying consistent indentation and dealing with other tabs are another issue. Done with `expand -i`. * vutil.* left alone, it's part of version. * Left regen managed files alone for now.
* win32/makefile.mk - enable USE_QUADMATH builds (mingw compilers only) on MS ↵sisyphus2021-01-101-0/+61
| | | | Windows
* win32/GNUmakefile - enable USE_QUADMATH builds (mingw compilers only) on MS ↵sisyphus2021-01-101-0/+52
| | | | Windows
* win32/config_sh.PL - enable USE_QUADMATH builds (mingw compilers only) on MS ↵sisyphus2021-01-101-1/+27
| | | | Windows
* win32/config_H.gc - enable USE_QUADMATH builds (mingw compilers only) on MS ↵sisyphus2021-01-101-0/+8
| | | | Windows
* reinstate USE_LARGE_FILES for the packaged win32 config.h filesTony Cook2021-01-072-12/+38
| | | | | | | 8b3db1a0c enabled this, but a change based on the old disable- use-large-file rule in my d9f9953f74 disabled it, so re-enable it. This prevents some build warnings when building miniperl.
* win32/GNUmakefile - define __USE_MINGW_ANSI_STDIO by defaultsisyphus2020-12-271-3/+5
|
* win32/makefile.mk - define __USE_MINGW_ANSI_STDIO by defaultsisyphus2020-12-271-3/+5
|
* perlgov: the perl governance documentRicardo Signes2020-12-211-0/+4
|
* Bump version to 5.33.6Max Maischein2020-12-203-3/+3
|
* new perldelta for 5.33.6Max Maischein2020-12-204-6/+10
|
* Add Configure probe for getenv() buffer raceKarl Williamson2020-12-192-0/+2
| | | | | | Most implementations do not have a problem with two getenv()'s running simultaneously in different threads. But Posix doesn't require such good behavior. This adds a simple probe to test the current system.
* Add pod/perldocstyle.podJason McIntosh2020-12-191-0/+4
| | | | | | | | | | | | | | | | | Satisfies https://news.perlfoundation.org/post/grant_proposal_documentation_standards_perl7 Committer: Adding a new file underneath pod/ entails adding (i) an entry for that file in pod/perl.pod and (ii) entries in win32/pod.mak. (i) In turn requires, figuring out an appropriate category within perl.pod in which to place the new file. The entry should match that in MANIFEST and be consistent with the style of entries in MANIFEST. (ii) Requires running Porting/pod_rules.pl so that entries in win32/pod.mak are also generated for the corresponding *.man, *.html and *.tex files. Supersedes https://github.com/Perl/perl5/pull/18275.
* fix the results of my stupidityTony Cook2020-12-021-2/+0
| | | | | I added these definitions late in the process, thinking I hadn't already added them, but I had.
* append colon to USE_STRICT_BY_DEFAULT descriptionDavid Mitchell2020-12-012-2/+2
| | | | | | This stops autodoc.pl complaining that: USE_STRICT_BY_DEFAULT has no documentation
* win32 symlink: reindentTony Cook2020-12-011-33/+34
|
* win32 symlink: treats paths that look like directories as directoriesTony Cook2020-12-011-5/+23
|
* Win32: try to make the new stat pre-Vista compatibleTony Cook2020-12-011-1/+15
| | | | | | | | Skips the win32\stat.t execute flag test for handles pre-Vista This is intended mostly for allowing the Win2000 smoker to build and test. If we end up dropping pre-Vista support this commit can be removed (or reverted if it ends up in blead)
* pre-vista support for win32_symlinkTony Cook2020-12-011-1/+14
|
* Win32: don't include version specific config for prebuilt config_h.*Tony Cook2020-12-016-19/+25
| | | | | | | This fixes the problem where doing a regen_config_h with a compiler that supports stdbool.h would generate a config_h.* that would result in a build failure on older compilers that didn't support stdbool.h.
* lstat(), readlink() and unlink() treat directory junctions as symlinksTony Cook2020-12-011-18/+46
|
* remove ${^WIN32_SLOPPY_STAT}Tony Cook2020-12-012-8/+0
| | | | | The new implementation, like the UCRT implementation, always opens the specified file.
* win32 symlink: only use the unprivileged flag if windows is new enoughTony Cook2020-12-011-1/+9
|
* Win32: re-work FILETIME <=> time_t conversionsTony Cook2020-12-011-15/+41
| | | | | | | | | Current versions of Windows claim to support leap seconds, but the time conversion I was using ignores that possibility. Switch to using APIs (FileTimeToSystemTime() and SystemTimeToFileTime()) that are documented to support leap seconds that might be included in a FILETIME.
* Win32: implement our own stat(), and hence our own utimeTony Cook2020-12-011-209/+188
| | | | | | | | | | | | | | | | | | | | | | | This fixes at least two problems: - unlike UCRT, the MSVCRT used for gcc builds has a bug converting a FILETIME in an unlike current DST state, returning a time offset by an hour. Fixes GH #6080 - the MSVCRT apparently uses FindFirstFile() to fetch file information, but this doesn't follow symlinks(), so stat() ends up returning information about the symlink(), not the underlying file. This isn't an issue with the UCRT which opens the file as this implementation does. Currently this code calculates the time_t for st_*time, and the other way for utime() using a simple multiplication and offset between time_t and FILETIME values, but this may be incorrect if leap seconds are enabled. This code also requires Vista or later. Some of this is based on code by Tomasz Konojacki (xenu).
* Win32: implement symlink() and readlink()Tony Cook2020-12-018-49/+179
| | | | | | | | The API used requires Windows Vista or later. The API itself requires either elevated privileges or a sufficiently recent version of Windows 10 running in "Developer Mode", so some tests require updates.
* Win32: add lstat(), fetch st_dev and st_ino and fetch st_nlink for fstatTony Cook2020-12-018-422/+942
| | | | | | | | | | | | | | | We need lstat() for various modules to work well with symlinks, and the same modules often want to check for matches on the device and inode number. The values we're using for st_ino match those that the Python and Rust libraries use, and Go uses the same volume and file index values for testing if two stat objects refer to the same file. They aren't entirely unique, given ReFS uses 128-bit file ids, but the API used to check for this (GetFileInformationByHandleEx() for FileIdInfo) is only available on server operating systems, so I can't directly test it anyway.
View Lorry Controller Status