| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
This was failing in smokes on AIX
|
| |
|
|
|
|
|
|
|
|
| |
These tests fail on the EN_US.UTF-8 locale.
Some fail due to a bug fixed in later AIX (lib/locale.t,
t/run/locale.t) and the other due to an apparent bug in the locale
itself.
https://perl5.test-smoke.org/report/5034327
|
| |
|
|
|
|
|
|
|
|
|
| |
The absence of these flags has never previously caused a problem
for running the probes, but on OpenVMS x86, warnings about long
symbols cause the probes to fail, probably because those symbols
are not getting optimized out as early in the new compiler. This
in turn causes the build to fail due to defining a homegrown
clockid_t which conflicts with the system version. So add the
flags that specify symbol handling (as well as everything else
being used to build Perl).
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is failing on smokes:
http://nntp.perl.org/group/perl.perl5.porters/266341
What I've noticed in working with changes to the locale handling code
(that isn't ready for v5.38) is that querylocale() has intermittent
failures, that aren't fully solved by using a mutex, and that versions
of Darwin earlier than major 20 have other problems with the POSIX 2008
API. These may be solved in Darwin 20 after disabling querylocale(),
but the failure rate was so infrequent that I'm unsure if it has been
fixed or just hasn't come up. So it is safest to just disable POSIX
2008 in Darwin for 5.38.
|
| |
|
|
| |
"layout" is a noun, while "lay out" a verb (somewhat).
|
| |
|
|
| |
This reverts commit ab28d7212b78f91ff5a0270d25b91a945c92c0e0.
|
| |
|
|
|
|
| |
necessary"
This reverts commit f6405b442f40de7d3697fcd885bfbfa9ba55eab0.
|
| |
|
|
| |
This reverts commit 3c544c1f6ee292e13d860f8d192ba0780a28c3ea.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
This reverts commit c56d7fa9134de66efe85a2fd70b28069c2629e0d.
Also un-TODO's the new test for this issue.
Fixes #21044
|
| |
|
|
| |
Regression test for #21044
|
| |
|
|
|
|
|
|
|
| |
# Conflicts:
# dist/ExtUtils-ParseXS/lib/ExtUtils/Typemaps.pm
# dist/ExtUtils-ParseXS/lib/ExtUtils/Typemaps/Cmd.pm
# dist/ExtUtils-ParseXS/lib/ExtUtils/Typemaps/InputMap.pm
# dist/ExtUtils-ParseXS/lib/ExtUtils/Typemaps/OutputMap.pm
# dist/ExtUtils-ParseXS/lib/ExtUtils/Typemaps/Type.pm
|
| |
|
|
|
| |
Encountered as an attempt to reference "2" from mis-typed
parameter type.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 9e254b0b5b145c9bfc3053e778e9f7fbb3760b45.
Date: Wed Apr 5 12:26:26 2023 -0600
This fixes GH #21040
The reverted commit caused failures in platforms using the musl library,
notably Alpine Linux. I came up with a fix for that, which instead
broke Windows. In looking at that I realized the original fix is
incomplete, and that things are too precarious to try to fix so close to
5.38.0. For example, I spent hours, due to a %p format printing 0 for
what turned out to be a non-NULL string pointer. I think it has to do
do with the fact that the failing code is in the middle of transitioning
between threads, and the printing got confused as a result.
The reverted commit was part of a series fixing #20155 and #20231. But
the earlier part of the series succeeded in fixing those, without that
commit, so reverting it should not cause things to break as a result.
This whole issue has to do with locales and threading. Those still
don't play well together. I have a series of well over 200 commits that
address this situation, for applying in early 5.39. My point is that we
are a long way from solving these kinds of issues; and they don't come
up that much in the field because they just don't get used. The
reverted commit would help if it worked properly, but it's not the only
thing wrong by a long shot.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
(aka README.win32)
The fix was in
commit 034a96a9c8546c2e080a802babba5ed9bc6c7798
Author: Elvin Aslanov <rwp.primary@gmail.com>
Date: Wed Apr 19 15:17:19 2023 +0200
Add MS Build Tools links
Add new section on Microsoft Build Tools, improve formatting.
|
| |
|
|
|
|
|
| |
Given this is a build option it is odd we have not mentioned
this in INSTALL. I know that Steffen didnt want this to be seen
as a "supported build mode" when it was introduced, but I think
its about time we documented it properly.
|
| |
|
|
|
|
|
|
|
| |
This separates out the code and content that is injected into one
of the lib/Config.* files, from the code that is part of configpm
itself. In particular this makes sure that nothing thinks that this
file contains usable POD.
Fixes https://github.com/Perl/perl5/issues/21045
|
| |
|
|
| |
Fix spelling on various files pertaining to core Perl.
|
| |
|
|
|
|
| |
Add new section on Microsoft Build Tools, improve formatting.
MSBT provides CLI compiler and other related tools (without the overhead of the Visual Studio IDE) to compile programs on Windows.
|
| |
|
|
|
| |
The deficiency mention removed by this commit was fixed earlier, but the
documentation did not get updated.
|
| |
|
|
|
| |
It was saying you had to use the Perl_foo(aTHX_ ...) form, which isn't
true.
|
| |
|
|
|
| |
Else... you'll get something recognizable back last century (e.g., 99 for 1999) , but what currently (123) looks more like https://en.wikipedia.org/wiki/Republic_of_China_calendar (112) than anything anyone else on the planet would understand!
Also, my correction ensures the man page will still be correct after the year 9999!
|
| |
|
|
|
| |
A strftime format is different from a printf one, and doesn't have the
constraints the latter has.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The comment from Tony Cook
https://github.com/Perl/perl5/issues/20373#issuecomment-1524256091
made me realize that this function doesn't fully work. It was added as
public API earlier in the 5.37 series, but we don't want it making it
into a stable release. This commit renames it so that the original name
will no longer work, but POSIX.xs can still, by changing to use the new
name.name
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The main exceptions being dist/, ext/, and Configure related
files, which will be updated in a subsequent commit. Files in the cpan/
directory are also omitted as they are not owned by the core.
'#define' has seven characters, so following it with a \t makes it look
like '#define ' when it is not, which then frustrates attempts to find
where a given define is. If you *know* then you do a
git grep -P 'define\s+WHATEVER'
but if don't or you forget, you can get very confused trying to find
where a given define is located. This fixes all such cases so they
actually are 'define WHATEVER' instead.
If this patch is getting in your way with blame analysis then view it
with the -w option to blame.
|
| |
|
|
|
|
| |
"#define\t" is annoying as it is it 8 spaces wide, so it looks like
"#define ", yet will not be found in a grep for "define foo" as the
space is actually a tab.
|
| |
|
|
|
|
| |
"#define\t" is annoying as it is it 8 spaces wide, so it looks like
"#define ", yet will not be found in a grep for "define foo" as the
space is actually a tab.
|
| |
|
|
|
|
|
|
| |
This cleans up the defines in dist/IO/poll.h.
"#define\t" is annoying as it is it 8 spaces wide, so it looks like
"#define ", yet will not be found in a grep for "define foo" as the
space is actually a tab.
|
| |
|
|
|
|
|
|
|
| |
This is broken out so it is easier for Tux to find and merge with
metaconfig.
View this patch with -w and you will see "no changes" except for
config_h.SH and Porting/config_h.pl both which needed to be changed to
ensure that they produce output that doesn't replicate the problem.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Currently this requires special handling on Linux and is broken
on Cygwin, since the compiler internal library directories
aren't in the normal search path.
Rather than searching ourselves, let the compiler do it, and check
it's vaguely functional.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
