Yikes! Wisdom and Common Sense.

You're absolutely right. The first time I ran make I ran out of room. I then ran make clean and just as I was about to move the perl-5.24.3 directory to another filesystem with much more room - believe it or not - my power went out.

The next day I completed the relocation. I reran Configure and then make and that's when I started getting the No Makefile errors. My (apparently naive) assumption was that running make clean brought me back to the point just before I ran Configure the first time. Anyway, I've since downloaded the tarball again and this time make fails much earlier, which surprises me. I should mention that while the Makefiles were 0 bytes other files in the same directory were the same size as the files I subsequently downloaded from CPAN as modules.

Writing Makefile for Encode::JP Generating a Unix-style Makefile Writing Makefile for Encode::KR Generating a Unix-style Makefile Writing Makefile for Encode::Symbol Generating a Unix-style Makefile Writing Makefile for Encode::TW Generating a Unix-style Makefile Writing Makefile for Encode::Unicode Generating a Unix-style Makefile Writing Makefile for Encode make[1]: Entering directory '/backups/build/perl-5.24.3/cpan/Encode' make: Not a recognized flag: w usage: make [-einqrst] [-k|-S] [-d[A|adg[1|2]mstv]] [-D variable] [-f +makefile] [-j [jobs]] [variable=value ...] [target ...] make[1]: *** [Makefile:643: subdirs] Error 2 make[1]: Leaving directory '/backups/build/perl-5.24.3/cpan/Encode' make[1]: Entering directory '/backups/build/perl-5.24.3/cpan/Encode' make: Not a recognized flag: w usage: make [-einqrst] [-k|-S] [-d[A|adg[1|2]mstv]] [-D variable] [-f +makefile] [-j [jobs]] [variable=value ...] [target ...] make[1]: *** [Makefile:643: subdirs] Error 2 make[1]: Leaving directory '/backups/build/perl-5.24.3/cpan/Encode' Unsuccessful make(cpan/Encode): code=512 at make_ext.pl line 569. make: *** [makefile:620: lib/auto/Encode/Encode.so] Error 25

line 643 of ./cpan/Encode/Makefile looks like this:

+636 # --- MakeMaker subdirs section: +637 +638 # The default clean, realclean and test targets in this Makefil +e +639 # have automatically been given entries for each subdir. +640 +641 +642 subdirs :: +643 $(NOECHO) cd Byte && $(MAKE) $(USEMAKEFILE) $(FIRST_MAKEFIL +E) all $(PASTHRU) +644 +645 subdirs :: +646 $(NOECHO) cd CN && $(MAKE) $(USEMAKEFILE) $(FIRST_MAKEFILE) + all $(PASTHRU) +647 +648 subdirs :: +649 $(NOECHO) cd EBCDIC && $(MAKE) $(USEMAKEFILE) $(FIRST_MAKEF +ILE) all $(PASTHRU) +650 +651 subdirs :: +652 $(NOECHO) cd JP && $(MAKE) $(USEMAKEFILE) $(FIRST_MAKEFILE) + all $(PASTHRU) +653 +654 subdirs :: +655 $(NOECHO) cd KR && $(MAKE) $(USEMAKEFILE) $(FIRST_MAKEFILE) + all $(PASTHRU)

If this helps with the variable values:

+8 # +9 # MakeMaker ARGV: (q[INSTALLDIRS=perl], q[INSTALLMAN1DIR=non +e], q[INSTALLMAN3DIR=none], q[PERL_CORE=1], q[LIBPERL_A=libper l.a], q[LINKTYPE=dynamic]) .... +83 PREFIX = $(PERLPREFIX) +84 PERLPREFIX = /opt/freeware ....... +127 FIRST_MAKEFILE = Makefile ..... +156 MAKE = make ........... +303 # --- MakeMaker tools_other section: +304 SHELL = /bin/sh +305 CHMOD = chmod +306 CP = cp +307 MV = mv +308 NOOP = $(TRUE) +309 NOECHO = @ ..... +330 USEMAKEFILE = -f .... +365 # --- MakeMaker cflags section: +366 +367 CCFLAGS = -D_THREAD_SAFE -D_ALL_SOURCE -D_ANSI_C_SOURCE -D_POS +IX_SOURCE -DUSE_NATIVE_DLOPEN -DNEED_PTHREAD_INIT -fwrapv -fno -strict-aliasing -pipe -maix64 -DUSE_64_BIT_ALL -D_FORTIFY_SOURCE=2 -W +all -Werror=declaration-after-statement -Wextra -Wc++-compat - Wwrite-strings +368 OPTIMIZE = -O +369 PERLTYPE = +370 MPOLLUTE = +371 ..... +389 # --- MakeMaker pasthru section: +390 +391 PASTHRU = LIBPERL_A="$(LIBPERL_A)"\ +392 LINKTYPE="$(LINKTYPE)"\ +393 OPTIMIZE="$(OPTIMIZE)"\ +394 PREFIX="$(PREFIX)"\ +395 PASTHRU_INC="$(PASTHRU_INC)"

To the extent I understand what is failing, it looks like make is being passed a flag 'w' that it doesn't understand, but I don't see where that is happening or where the 'w' flag is coming from. I apologize for all the detail, but I simply don't know enough to distinguish the crap from the gold.


In reply to Re^2: perl-5.24.3 build woes by 2pipes
in thread perl-5.24.3 build woes by 2pipes

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.