• Do not register here on develop.twiki.org, login with your twiki.org account.
• Use View topic Item7848 for generic doc work for TWiki-6.1.1. Use View topic Item7851 for doc work on extensions that are not part of a release. More... Close
• Anything you create or change in standard webs (Main, TWiki, Sandbox etc) will be automatically reverted on every SVN update.
Does this site look broken?. Use the LitterTray web for test cases.

This may have something to do with resolving symlinks. Depending on your platform this be an expensive operation.

I have a serious complaint about mklinks.sh.

I use mklinks.sh so that my build process done't compalin too much about being unable to find plugin documentation topics, but when the tarfile is un-tared ay the prodcution site, the links on the new machine are "broken" becuase they point to a file on the old machine's file system.

In short, the build process does not de-reference symlinks. See Bugs:Item816

-- AJA

So sorry, but you know that the purpose of mklinks.sh is to enable a developer environment, and was never intended as a "staging post" for your own build procedure.

This is not 'my' build procedures, this is tools/build.pl using tools/MANIFEST as documented.

I've reported that the build process changed and broke but you ignored me.

My arrangement tries to be as 'separated as possible. I have the svn download area on one machine and the test platform on another. The idea is that the build process should be able to build a package that can, once the .htaccess has been set up and bin/configure run, installed anywhere.

To this end the buld process should not need to be run on a 'live site'. In fact the svn are very firmly should not be under Apache. The individual MANIFEST files and the MANIFEST file in tools/ should be adequate. The paths and libraries set up in tools/build.pl shgould be adequate. They were. Then something changed.

That was fine until about six weeksago when something changed in the BuildContrib. I gather from conversation that TW does run his svn area under Apache as a live site.

Now, unless the svn area is live -- which I am not willing to do for technical reasons - or mklinks.sh is run so that the pluigns apear to be there one of the stages of the build bombs out. In this example,

  • The plugins except for SpreadSheetPlugin have been linked with mklink.sh
  • The "... could not fully register ..." messages seem to be becuase the build process can't follow symlinks
  • The other error messages and the attempt to write errors to the root direcotry came about from changes to BuildContrib that I can't trace toa specific revision but were not there when I started using tools/build.pl
  • When I first used tools/build.pl I didn't need the links. I started using mklinks,sh to eliminate the "... cannot locate .." error. This is the only way I can get a sucessful build.
  • However, even so, the plugin topics are =tar='d as symlinks, which is what this bug is about. If I remove the symlinks the build doens't work at all.

$ perl build.pl release
Auto-adding install script to manifest
Building documentation....
Could not write "ARRAY(0x872f510)" to /warn200511.txt: Permission denied
Could not write "ARRAY(0x872f588)" to /warn200511.txt: Permission denied
Could not write "ARRAY(0x872f63c)" to /warn200511.txt: Permission denied
Could not write "ARRAY(0x8738170)" to /warn200511.txt: Permission denied
Could not write "ARRAY(0x8740a5c)" to /warn200511.txt: Permission denied
Could not write "ARRAY(0x874b614)" to /warn200511.txt: Permission denied
Could not write "ARRAY(0x875b3fc)" to /warn200511.txt: Permission denied
Could not write "ARRAY(0x875d94c)" to /warn200511.txt: Permission denied
Could not write "TWiki::I18N: falling back to English: TWiki::I18N::Fallback=HASH(0x877edec)" to /warn200511.txt: Permission denied
Could not write "Plugins: could not fully register CommentPlugin, no plugin topic" to /warn200511.txt: Permission denied
Could not write "Plugins: could not fully register EditTablePlugin, no plugin topic" to /warn200511.txt: Permission denied
Could not write "Plugins: could not fully register InterwikiPlugin, no plugin topic" to /warn200511.txt: Permission denied
Could not write "Plugins: could not fully register PreferencesPlugin, no plugin topic" to /warn200511.txt: Permission denied
Could not write "Plugins: could not fully register SlideShowPlugin, no plugin topic" to /warn200511.txt: Permission denied
Could not write "Plugins: could not fully register SmiliesPlugin, no plugin topic" to /warn200511.txt: Permission denied
Could not write "Plugins: could not fully register SpreadSheetPlugin, no plugin topic
TWiki::Plugins::SpreadSheetPlugin could not be loaded.  Errors were:
Can't locate TWiki/Plugins/SpreadSheetPlugin.pm in @INC (@INC contains: /home/anton/twiki/branches/DEVELOP/lib/CPAN/lib//arch/ /home/anton/twiki/branches/DEVELOP/lib/CPAN/lib//5.8.3/i386-linux-thread-multi/ /home/anton/twiki/branches/DEVELOP/lib/CPAN/lib//5.8.3/ /home/anton/twiki/branches/DEVELOP/lib/CPAN/lib// /home/anton/twiki/branches/DEVELOP/lib . /usr/lib/perl5/5.8.3/i386-linux-thread-multi /usr/lib/perl5/5.8.3 /usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.3 /usr/lib/perl5/vendor_perl/5.8.2/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.2 /usr/lib/perl5/vendor_perl/5.8.1/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.1 /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.0 /usr/lib/perl5/vendor_perl) at (eval 23) line 1.
BEGIN failed--compilation aborted at (eval 23) line 1.

----" to /warn200511.txt: Permission denied
Could not write "Plugins: could not fully register TablePlugin, no plugin topic" to /warn200511.txt: Permission denied
********************************
OopsException(accessdenied/no_such_web web=>TWiki topic=>TWikiDocumentation params=>view)
********************************
Documentation built
-- AJA

How grown builds should define their own MANIFEST file and user perl build.pl in tools. That's the recommended approach.

  • This is not 'my' build procedures, this is tools/build.pl using tools/MANIFEST as documented. -- AJA

The performance reduction is interesting. It is probably a result of the code for the default-enabled plugins suddenly becoming available. A 4-5 AthensMarks cost for initialising those plugins sounds on the high side, though. Does disabling the plugins in configure recover the lost AthensMarks?

CC

Anton, sorry for ignoring you, but I'm under terrific pressure at the moment and it's hard to be anything but terse.

I build the betas from an area that is not enabled under Apache. However it does have a valid bin/LocalLib.cfg and lib/LocalLib.cfg. These are necessary to provide the path components used by the build process.

I can't reproduce what you are seeing, and as such I need you to do just a little bit more debugging to determine what is wrong with your specific environment. Please. If you can identify a problem more narrowly, then I can help.....

CC

this problem occurred when the $TWiki::cfg{LogDir} configuration variable was introduced, but without providing a fallback default in TWiki.cfg (i think)

WN

Other settings, such as the library path, are made in the BEGIN block of tools/build.pl. Shouldn't this be set there too? The inforation about the "base" directory is avialable there, its is used to set the library path. -- AJA


Well, it could be, I suppose. Though in the BEGIN block for Build.pm rather than in build.pl. Try it and see! Anyway, these are warnings; I corrected them so they produce test instead of ARRAY refs, in which case you would have seen they are warnings.

CC

ItemTemplate
Summary running mklinks.sh reduces perofrmance by 4-5 athens marks
ReportedBy SvenDowideit
AppliesTo Engine
Priority Normal
CurrentState Closed
WaitingFor

Checkins 7298
Edit | Attach | Watch | Print version | History: r10 < r9 < r8 < r7 < r6 | Backlinks | Raw View |  Raw edit | More topic actions
Topic revision: r10 - 2005-11-06 - CrawfordCurrie
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback