[LibX] Error from xcreateextension.pl
nathanb at vt.edu
Tue Jul 10 08:46:03 PDT 2007
My guess based on the path in the error message is that you are running
xcreateextension.pl under Windows using a perl interpreter like
ActivePerl and either cygwyn or mingw to get the GNU/UNIX tools like rm,
cp, find, etc.
I am impressed that you got this far with xcreateextension.pl under
Windows. However, the script still contains some UNIX-specific hacks,
such as line 221, where it uses the ; operator to chain several commands
together--a staple of the UNIX command-line. Windows doesn't support
this operator on its command line, which is where the error in rm comes
from (it parses the -name from the find command and interprets it as
-n). Since this command line actually creates the .xpi by selectively
removing things we don't want bundled and then zipping the rest of the
stuff up, it dies on the next line because there is no .xpi file to chmod.
For the moment you can hack the xcreateextension.pl file to execute each
of those commands concatenated in system() to be a separate command (or
you could run the script under UNIX--your call). Be aware that the
output of find is piped into xargs with an absolute path pointing to
/bin/rm, so you might have to change that as well to point to wherever
your rm is located (maybe something like d:/bin/rm on your filesystem).
Wade Guidry wrote:
> I'm working on creating a new edition of libx for my library, using the
> source on mozdev.
> I'm almost there. My last error is coming from xcreateextension.pl
> When I run this command, I end up with the following:
> (lots of 'processing...' messages)
> Then, near the end...
> processing ../base/install.rdf to tmp2/install.rdf
> processing ../base/update.rdf to tmp2/update.rdf
> rm: invalid option -- n
> Try `rm --help' for more information.
> chmod: cannot access `d:/libx/libx/src/editions/crsn/libx-crsn.xpi': No such
> file or directory
> chmod g+w failed at xcreateextension.pl line 226.
> I don't seem to be able to find where the script is hitting the "invalid rm
> option" error.
> Has anyone run into this particular issue?
> Wade Guidry
> Systems Manager, CRSN
> ofc / cell: 503.801.2073
> fax: 503.815.8194
> wade at beachbooks.org
> Libx mailing list
> Libx at mozdev.org
More information about the Libx