- Jarkko's How to build Configure tweaked by Nick and Merijn.
+ Jarkko's How to build Configure tweaked by Nick and Merijn, and now
+ maintained by perl5-metaconfig
The Configure script and config_h.SH file in the Perl distribution are
-generated by a program called metaconfig. Metaconfig was originally
+generated by a program called metaconfig. Metaconfig was originally
written by Larry Wall, and was subsequently enhanced and maintained
by Raphael Manfredi. The binary that invokes the generation of the
Configure file is called mconfig.
You have presumably obtained the metaconfig from the repository e.g.
- $ git clone git://perl5.git.perl.org/metaconfig.git metaconfig
+ $ git clone github.com:perl5-metaconfig/metaconfig metaconfig
-or some other way to obtain this file, like a complete compressed archive
-from the previous pumpkin.
+When working with metaconfig you will generally have two git checkouts
+next to each other: (1) this metaconfig checkout; and (2) a checkout of
+the Perl 5 source code in which you will generate a new Configure
+script. In this README, we will refer to these directories as the
+'metaconfig' directory and the 'perl' directory.
-Normally this directory and perl directory are next to each other
-so ../perl will get you to perl and ../perl/../metaconfig will get you
-back here.
+Since these two directories are normally next to each other, so ../perl
+will get you to perl and ../perl/../metaconfig will get you back here.
+You should establish a symbolic link to the checkout in which Configure
+is generated such as this:
+
+ $ cd metaconfig
+ $ ln -s ../perl perl
+
+We will do the reverse symlinks later.
Contents of this directory:
a git clone of "dist". Optionally present. See (a) below.
This is where dist/meta resides as of 2016-04-01
dist:
- a symlink to the lib you actually use. For Merijn that is
- metaconfig/dist -> ../lib/dist
+ The folder where the original units from dist are in.
+ These may differ from dist-git, as upstream also moves
+ on and develops.
(a) You need to have dist installed so that you have metalint and metaconfig
- in your $PATH.
+ in your $PATH. As dist/meta binaries are now included in the git checkout,
+ you do NOT need to install dist/meta itself.
+
+ If you also want to play with or compare to the original meta/dist, you
+ can checkout that too.
+
The dist version used for perl is dist-3.5-20 in this directory, which is
a slightly modified version of the original, which you can get at GITHUB
repository https://github.com/rmanfredi/dist.git. If you'd like to keep
After make install, remove lib/U/d_debugging.U in your target lib, as perl
uses its own way to set/define debugging (see INSTALL)
- the dist-3.5-20 installation as used by Merijn is available on his CPAN as
- perl-meta-3.5-20.tgz
-
dist's 'Configure' is similar to perl's but perhaps not quite as polished.
There are some perl specific "dist units" in the 'U' directory.
The U directory also contains some patches to 'dist' which have already
been applied to dist-3.5-20 directory.
- We have not yet arranged for metaconfig to use perl's versions of the
+
+(aa) We have not yet arranged for metaconfig to use perl's versions of the
'units' by default so you need some housekeeping in the perl directory...
-(aa)
+ Then add metaconfig/bin to your $PATH or create aliases like
+
+ $ export MC5=/your/path/to/metaconfig
+ $ alias ml="perl $MC5/bin/mlint -O"
+ $ alias mc="perl $MC5/bin/mconfig -m -O"
+
+ examples in the rest of this README will just refer to mlint and mconfig
+ as if they appear in your $PATH
- If you plan to make changes to mconfig or mlint locally (and you probably
+(aaa)
+
+ If you plan to make changes to mconfig or mlint locally (and you might
want to, as both are written for perl4), consider installing mconfig and
mlint from the cmon subdirectory into your $PATH too. These are the
- non-autoloading versions and can easily be changed. Here is what I added
- at the beginning of mconfig:
-
- --8<---
- BEGIN { $ENV{LC_ALL} = "C"; }
- chdir "/pro/3gl/CPAN/perl";
- { my @Cc = qw( Configure config_h.SH );
- system "chown merijn @Cc";
- chmod 0775, @Cc;
- #-d "merijn" or mkdir "merijn";
- #system "cp -f Configure config_h.SH Porting/Glossary Porting/config.sh merijn/";
- system "ls", "-l", @Cc;
- }
- -->8---
-
- I also added the first two lines of that patch to mlint
-
-(b) You need to be in a/the Perl directory, i.e. either something from
- //depot/perl/... or one of its branches
- (e.g. Nick I-S is usually in //depot/perlio/...)
- and you need:
- 1) have a symlink to ../metaconfig/U called U
- 2) have a symlink to ../metaconfig/.package called .package
- 3) have a symlink to MANIFEST called MANIFEST.new
- 4) chmod +w Configure config_h.SH Porting/Glossary Porting/config*
-
-(c) Write the new unit as U/perl/d_bar.U ('perl' can also be 'modified',
- 'compline' or any other existing folder, except for 'all'). Choose
- the best appropriate subdir of U. See U/README for a description of
- the various subdirectories.)
-
-(d) Run metalint (or mlint) to see nits: as opposed to lint, the gripings
- of metalint are usually serious :-) and need fixing
-
- Exceptions are lots of
+ non-autoloading versions and can easily be changed. As these are used by
+ all team members, please communicate changes on github first.
+
+(b) You need to be in the 'perl' checkout directory, which you created the
+ symbolic link to, in preparation. In this working directory, you need
+ symbolic links too, which are already known to perl itself to ignore.
+ Assuming you have metaconfig and perl side by side on the same level:
+ ln -s ../metaconfig/U U
+ ln -s ../metaconfig/.package .package
+ ln -s MANIFEST MANIFEST.new
+ chmod +w Configure config_h.SH Porting/Glossary Porting/config*
+
+(c) Create a new file for the new unit as U/foo/d_bar.U
+ ('foo' is one of the existing folders in U except for 'all'. It most
+ likely will be 'perl', but it could also be 'modified', 'compline' or any
+ other existing folder). Choose the best appropriate subdir of U. See
+ U/README for a description of the various subdirectories.) You should
+ choose the closest existing unit file as a starting point, and first copy
+ it to the new file. For example, the unit for seeing if strtold_l() exists
+ was created as U/threads/d_strtold_l.U, copied from perl/d_strtold.U, then
+ adjusted. It goes under 'threads' because it is used only on threaded
+ perls.
+
+(d) Run "mlint -O" to see nits: as opposed to lint, the gripings of mlint
+ are usually serious and need fixing
+
+ Without -O, exceptions are lots of
Your private U/modified/issymlink.U overrides the public one.
due to the perl special units
- an alias to something like
- $ metalint |& grep -v -e '^ Your private U/'
- will make the process silence up on that (of course you can add an
- option to mlint to disable that warning (which is already disabled
- by the undocumented and forgotten -s option, but that also suppresses
- other warnings)
-
and
"End.U": stale ?MAKE: dependency '$W'.
which is apparently normal ...
--- the next steps are in the perl folder
+-- the next steps are in the perl folder, though the instructions below include
+ a 'cd perl' at each step, as a reminder. If you already are in 'perl',
+ disregard the reminders.
-(e) chmod +w Configure config_h.SH
+(e) There is a chicken and egg problem for newly created units. To get around
+ this, for such a unit, edit the file metaconfig.h and add to the comment
+ the appropropriate name. To continue the example above, we would add the
+ string HAS_STRTOLD_L at the end of the comment. This can be removed once
+ the code base has actual uses of the unit.
(f) mconfig -m -O to regenerate Configure and config_h.SH
(g) metaconfig does not deal with depends in config_h.SH, so some
reorganization is needed.
- perl Porting/config_h.SH
+ $ cd perl
+ $ perl Porting/config_h.pl
will fix the ordering
-
-(h) The messy not-yet-automated part is that the knowledge of the new symbol
+
+(h) The messy semi-automated part is that the knowledge of the new symbol
needs to be propagated to non-Configure lands like Win32, WinCE, Netware,
VMS, VOS, EPOC, ... see previous Configure changes to see which are these
heathen lands. Files to take care of are
{win32,wince,NetWare}/config_[hH]*, (Win32, WinCE, NetWare),
- configure.com (VMS), VOS/config* (since 5.9 VOS uses Configure, though),
- epoc/config.sh (EPOC). Depending on the kind of patch djgpp/config*
- might also need adjusting (for example when adding/changing the list
- of extensions)
+ configure.com (VMS), epoc/config.sh (EPOC). Depending on the kind of
+ patch djgpp/config* might also need adjusting (for example when
+ adding/changing the list of extensions)
- For Win32 the process is semi-automated - if you have a Win32
- machine to run dmake on ...
+ Most can be checked and updated by a tool Nicholas provided:
-(i) Edit U/mkglossary (right near the top) to point to where you keep
- dist's standard metaconfig units as well as your perl-specific ones.
+ $ cd perl
+ $ perl Porting/checkcfgvar.pl
-(j) Run U/mksample to freshen the Porting/config* and Porting/Glossary.
- Adjust the various compile-time options (e.g. 64bit, threads) as
- you see fit.
- You can skip this phase, it's not essential, just good housekeeping.
+ and if it shows differences,
-(k) Run the perl build chain
+ $ perl Porting/checkcfgvar.pl --regen --default=define
- make veryclean
- sh ./Configure -des -Dusedevel
+ (of course "define" can also be "undef" based on the changes you made
- The dependency for uconfig.h isn't carved in stone, so you might
- need to regenerate it
+ For Win32 the process is semi-automated -- if you have a Win32
+ machine to run dmake on
- perl regen/uconfig_h.pl
+ For vms, ('configure.com'), you likely will have to hand-edit in the
+ changes, using a similar unit as a starting point. There likely will be at
+ least 2 groups of changes. Rerun the tool until you've fixed everything it
+ finds.
- Then make and make test or make test_harness (with TEST_JOBS=5)
+(i) Check if U/mkglossary (right near the top) points to where you keep
+ dist's standard metaconfig units as well as your perl-specific ones.
- make all test_harness
+(j) Run the perl build chain
+
+ $ cd perl
+ $ make veryclean # Only if Configure already has been run
+ $ ./Configure -Duse64bitall -Dusethreads -Dusedevel -des
+ $ perl regen/uconfig_h.pl
+
+ Then make and make test or make test_harness
+
+ $ make -j12
+ $ env TEST_JOBS=13 make test_harness
Before you start committing, make sure that the other developers
are happy and run
- make test_porting
+ $ make test_porting
+
+ again
+
+(k) Optionally, run Porting/mksample to freshen the Porting/config*.
+ Adjust the various compile-time options (e.g. 64bit, threads) as
+ you see fit.
+ You can skip this step, it's not essential, just good housekeeping.
+
+ Most of this only works if you have run the core-tests with the new
+ generated files
+
+(kk) Run U/mkgloss.pl to freshen Porting/Glossary
+
+ You should at least check
+
+ $ perl U/mkgloss.pl | diff Porting/Glossary -
+
+ This will show two warnings that you can ignore:
+
+ U/mkglossary: couldn't find libdb_needs_pthread
+ U/mkglossary: couldn't find libdirs
+
+ all other things need a review
-- the next steps are in the metaconfig folder again
-(l) git add U/perl/foo/bar.U when you are ready ...
+(l) git add U/foo/bar.U when you are ready ...
(m) git commit -m "Your commit description"
(n) When all patches are applied, tested and committed, and you are happy,
git push
- Merijn prefers to do steps (l) through (n) in git-gui
+(o) Documentation on 'dist' may be found at these locations:
+ https://github.com/rmanfredi/dist/blob/master/mcon/man/mconfig.SH
+ https://manpages.debian.org/stretch/dist/metaconfig.1.en.html
https://perl5.git.perl.org / metaconfig.git / blobdiff