Hi,
msconvert
command fails on fedora 24 (devel branch) with Boost-1.60:
+ ./msconvert libpwiz-tiny.pwiz.1.1.1.mzML -v -o ./ --zlib --mzXML --64 --mz64 --inten64 format: mzXML m/z: Compression-Zlib, 64-bit intensity: Compression-Zlib, 64-bit rt: Compression-Zlib, 64-bit ByteOrder_LittleEndian indexed="true" outputPath: ./ extension: .mzXML contactFilename: filters: filenames: libpwiz-tiny.pwiz.1.1.1.mzML RPM build errors: boost::filesystem::create_directory: No such file or directory Please report this error to support@proteowizard.org. Attach the command output and this version information in your report: ProteoWizard release: 3.0.9283 (2016-1-11) ProteoWizard MSData: 3.0.9283 (2016-1-11) ProteoWizard Analysis: 3.0.9248 (2015-12-30) Build date: Jan 23 2016 14:58:14
Full build log: https://kojipkgs.fedoraproject.org//work/tasks/3397/12663397/build.log
It looks to me like it's working fine, you just don't have that input file libpwiz-tiny.pwiz.1.1.1.mzM where it needs to be.
It's same package previously built with success on Fedora 23 with Boost-1.58
Just Boost is changed on failed build.
https://kojipkgs.fedoraproject.org//packages/libpwiz/3.0.9283/1.fc24/data/logs/x86_64/build.log
But it does not appear to be a failed build, exactly - it's a failed test, which isn't good but isn't the same thing and may have nothing to do with Boost. Please try that step
./msconvert libpwiz-tiny.pwiz.1.1.1.mzML -v -o ./ --zlib --mzXML --64 --mz64 --inten64
manually and see if it works. Obviously the file libpwiz-tiny.pwiz.1.1.1.mzML will need to be present, which I suspect is the actual issue.
Indeed, it's a RPM build error due to
msconvert
test error.If it was so, it would be always failed.
Actually, it looks to me like the argument of
-o
option (that I previously used) is rejected with Boost-1.60:boost::filesystem::create_directory: No such file or directory
In fact,
works fine. Please, see this new build log: https://kojipkgs.fedoraproject.org//work/tasks/1515/12681515/build.log
Yes, I think you have identified the issue, something about "./" as an argument, and yes, I can see where that might be due to different behavior in Boost. I'll make sure the other proteowizard developers see this. For now, of course, you have a workaround. Thanks for letting us know!