I've recently gotten into writing chrome extensions a little, and of course wanted to write a Makefile to pack my extension for me. When I tried it with the chromium build, this is all I got: chromium --pack-extension=../myext.crx --pack-extension-key=../myext.pem --no-message-box [1:1:1946309928171:ERROR:base/native_library_linux.cc(32)] dlopen failed when trying to open /usr/lib64/chromium-browser/libffmpegsumo.so: /usr/lib64/chromium-browser/libffmpegsumo.so: cannot open shared object file: No such file or directory make: *** [crx] Error 29 I'm not entirely convinced that error is what's stopping it, especially since I already know it's a benign message (see http://phajdan-jr.blogspot.com/2010/12/www-clientchromium-and-missing.html for the uninitiated), but that's all I get. If there's another flag or something I can provide to give more information, I'm happy to do so. For more information about the command line switches I'm using to package the extension, see: http://code.google.com/chrome/extensions/packaging.html#H2-2 When I use the "Pack extension..." button inside Chromium, it works great (and that's how I generated my .pem file in the first place), which is what makes me think this may be a bug instead of just my error, but I'm happy to be wrong there! :) Reproducible: Always Steps to Reproduce: 1. write (or copy) a chrome extension 2. package it through the GUI 3. try to repackage through the commandline Actual Results: error message, no crx file built, and exiting with status 29 Expected Results: crx built successfully I also tried supplying full paths to the options, just in case that was the error, but I did not yet try closing chrome (in case it's somehow related to the single instance code, but I'm happy to try this if it'll be helpful).
Could you try running the command from gdb to see whether it crashes?
Well I feel kind of stupid now. --pack-extension doesn't expect a path to the desired crx file, it wants a path to the extension sources, of course. Wasn't thinking clearly this morning. When I make that change, it works fine. Sorry for the false alarm!
