On Mon 03 Jan 2005 20:52, Andrew Dougherty <[EMAIL PROTECTED]> wrote: > On Thu, 23 Dec 2004, H.Merijn Brand wrote: > > > In order to get in sync, I rebuilt config_h.SH with metaconfig, and the > > content was the same, but reshuffled (reordered) > > > > This cause HAS_QUAD to be too far down and also LONGLONG to be used before > > defined > > If I recall correctly, the dependencies in the metaconfig units control > the ordering in Configure, but not the ordering in config_h.SH. The > ordering in config_h.SH, I believe, is determined by a simple alphabetical > ordering of the units. That's what the a_dvisory/ directory is for. I > think there are some more details in the metaconfig/README file.
Sounds reasonable, except for the fact that I somehow don't see how and where a_dvisory is used, if used at all l1:/pro/3gl/CPAN/bin 112 > l ./ jmkmf* manilist* pat* patindex* patsnap* ../ kitpost* metaconfig* patbase* patlog* rt* cpan2dist.pl* kitsend* metagrep* patcil* patmake* rt-cli* cpanp* makeSH* metalint* patclean* patname* showpatch* cpanpd.pl* makedist* metaxref* patcol* patnotify* sshp* diff2unit.pl* manicheck* p4* patdiff* patpost* jmake* manifake* packinit* patftp* patsend* l1:/pro/3gl/CPAN/bin 113 > grep a_dvisory * Exit 1 l1:/pro/3gl/CPAN/bin 114 > cd ../metaconfig/ l1:/pro/3gl/CPAN/metaconfig 115 > grep a_dvisory * Binary file U matches l1:/pro/3gl/CPAN/metaconfig 116 > cd U l1:/pro/3gl/CPAN/metaconfig/U 117 > grep a_dvisory * README:a_dvisory/ README: The a_dvisory/ directory, then, is a place to put units that need l1:/pro/3gl/CPAN/metaconfig/U 118 > I'm contemplating some sort of tsort algorithm for config_h.SH sorting -- H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/) using perl-5.6.1, 5.8.5, & 5.9.x, and 809 on HP-UX 10.20 & 11.00, 11i, AIX 4.3, AIX 5.2, SuSE 9.1, and Win2k. http://www.cmve.net/~merijn/ http://archives.develooper.com/[email protected]/ [email protected] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
