New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
make install needs write permission in build directory #4235
Comments
From @AbigailCreated by @AbigailSome time ago, I reported that 'make install' needs write permission to Unfortunally, the problem has cropped up again in 5.7.2. Write permission If would be nice if the previous situation could be restored. Abigail Perl Info
|
From david_wallis@bmc.comCreated by dawallis@gyoza.bmc.com'make install' should not attempt to change any file or directory If I have changed to a different userid for the install, I probably Also, remember that developers may or may not have the password to Perl Info
|
From @eserte"david_wallis@bmc.com (via RT)" <perlbug-followup@perl.org> wrote:
Here's some analysis of the problem. The blibdirs sections of DynaLoader's blibdirs :: As it stands, this rule gets always fired in a static DynaLoader blibdirs :: $(INST_LIBDIR) : $(INST_AUTODIR) : $(INST_ARCHAUTODIR) : $(INST_BIN) : $(INST_SCRIPT) : $(INST_MAN1DIR) : $(INST_MAN3DIR) : This is not perfect, either, because GNU make emits some warnings Regards, -- |
From @schwernOn Thu, Nov 13, 2003 at 01:09:08PM +0000, Slaven Rezic wrote:
If it does then there's something wrong. blibdirs is touched at the end blibdirs is touched. The .exists files were set to the time of CORE/perl.h. But none of this seems to really be the problem. Running make with I need to be able to extend the blibdirs target if I'm going to keep Try this. --- lib/ExtUtils/MM_Any.pm 10 Nov 2003 08:34:41 -0000 1.67 - my $make = "\nblibdirs :: \n";
Make can't depend on a directory target. That's what caused the whole See http://nntp.x.perl.org/group/perl.makemaker/1481 for details. -- |
Migrated from rt.perl.org#7321 (status was 'open')
Searchable as RT7321$
The text was updated successfully, but these errors were encountered: