[Win32] Why did they add '-perlio'

syphilis has asked for the wisdom of the Perl Monks concerning the following question:

Hi,

As I mentioned earlier my unthreaded builds of perl were, upon installation, being assigned an @INC that was empty.
Well .... silly me .... I had assumed that an archname of 'MSWin32-x64-multi-thread' would, upon becoming neither 'multi' nor threaded, change to simply 'MSWin32-x64'.
But, no - the win32/makefiles decree that it becomes 'MSWin32-x64-perlio' if USE_PERLIO is defined.
The fact that USE_PERLIO is also defined for the multi-threaded build is apparently unworthy of mention, even though defining USE_PERLIO is equally optional for both multi-thread and non-multi-thread builds of perl, AFAICS.

So why do they add '-perlio' for the unthreaded build only ?
Is there a good reason ? (Not that one is required, of course ... heaven forbid !!)

UPDATE - to elaborate a little on how this led to @INC being empty:
In these unthreaded builds I was specifying (eg) INST_ARCH=MSWin32-x64 and that didn't match the actual designated archname of MSWin32-x64-perlio .
Now, I don't exactly know why that resulted in an empty @INC, but the problem went away as soon as I changed to specifying INST_ARCH=MSWin32-x64-perlio .

Cheers,
Rob

Comment on [Win32] Why did they add '-perlio' Select or Download Code

Replies are listed 'Best First'.
Re: [Win32] Why did they add '-perlio' by ikegami (Patriarch) on Jun 23, 2022 at 07:36 UTC
It doesn't really matter what the arch name is. You can get it from the following: `eval "$( perl -V:archname )"` [download] (Well, once you rebuild your broken `perl`.)	[reply] [d/l] [select]
Re^2: [Win32] Why did they add '-perlio' by syphilis (Archbishop) on Jun 23, 2022 at 08:19 UTC
The problem was that the directory I specified for $(INST_ARCH) was different to $(ARCHNAME), as determined by the GNUmakefile. I still don't know whether that should lead to @INC being empty ... but I know from experience that it certainly does. If you're wondering what happens when such a mismatch occurs, `gmake install` puts the architecture-specific stuff into the directory specified by $(INST_ARCH), not the directory specified by $(ARCHNAME). There's no problem if (and only if) either: 1) $(INST_ARCH) is unset (undef); or 2) $(INST_ARCH) is set to $(ARCHNAME). I don't really see why it should matter. Everything would be fine if @INC was set in accordance with $(INST_ARCH). If it's so important that this not be allowed, then maybe it ought to be stated clearly that, when $(INST_ARCH) is set, it must be set to $(ARCHNAME). Cheers, Rob	[reply] [d/l]
Re: [Win32] Why did they add '-perlio' ( that one unix guy ) by Anonymous Monk on Jun 23, 2022 at 11:43 UTC
When it comes to win32 issues i always muse: Probably that one unix guy :D .... They'll let anybody buck with win32 traditions ... its been there a long time https://perl5.git.perl.org/perl5.git/blame/HEAD:/win32/Makefile Re^7: "versioned" builds of Win32 perl Re^7: empty @INC in fresh compile of 5.12.2 on win32 what does linux do?	[reply]
Re^2: [Win32] Why did they add '-perlio' ( that one unix guy ) by syphilis (Archbishop) on Jun 23, 2022 at 12:58 UTC
what does linux do? AFAICS linux does exactly what I expected Windows to do. I can't recall ever seeing the string "perlio" in a linux archname. Cheers, Rob	[reply]


"be consistent"
	PerlMonks