[tei-council] Interpreting errors resulting from TEI build
mholmes at uvic.ca
Mon Apr 18 14:50:27 EDT 2011
If this is the latest equivalent output from Jenkins:
then I'm puzzled. It shows no errors or warnings at all. My build is
based on a fresh checkout from SVN, followed by "cd trunk/P5", then
"make". Since Jenkins should also be working from the latest source,
it's difficult to see why the results would be different. But I don't
know what "the global attribute trap" is, so maybe there's something
specific that needs to be done to make the checked-out source work properly.
Can someone else who has a working build environment (Piotr or Kevin,
perhaps) run a build and see if you get the same errors as me?
On 11-04-18 11:38 AM, Sebastian Rahtz wrote:
> Two things, from a quick glance with free wifi at an airport on holiday
> 1. If it does not say it's an error, it's probably just a warning - that probably applies to the rm messages
> 2. That message about @n looks to me like a mismatch of tei versions and xsl. I may be wrong, but my guess is that you met the global attribute trap.
> My advice is to check Jenkins and see if he reports errors. If not, it's your setup; if he does, then it's recent changes.
> Carved in stone on my iPad
University of Victoria Humanities Computing and Media Centre
(mholmes at uvic.ca)
More information about the tei-council