Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#42238 - [boost] extra # in vector.hpp

Attached to Project: Arch Linux
Opened by Oliver Gatti (livix) - Saturday, 04 October 2014, 10:19 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Wednesday, 29 October 2014, 11:24 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Bartłomiej Piotrowski (Barthalion)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I had encountered some error compiling a personal project. The error was something like "one extra # in file /usr/include/boost/fusion/container/vector/vector.hpp at line 24". Then I edited that file and changed line 24 from "#define FUSION_HASH #" to "#define FUSION_HASH". After that I managed to compile my project. I hope this report would be someway useful since it's my first one and I'm not sure why there was that extra #.

Additional info:
* package version(s) : extra/boost 1.56.0-1

Steps to reproduce:
compile something that requires the header /usr/include/boost/fusion/container/vector/vector.hpp
This task depends upon

Closed by  Bartłomiej Piotrowski (Barthalion)
Wednesday, 29 October 2014, 11:24 GMT
Reason for closing:  Upstream
Comment by Jan de Groot (JGC) - Saturday, 04 October 2014, 14:25 GMT
Can you give exact error messages? FUSION_HASH is defined as #, so that's why there's a # at the end of the line.
Comment by Richard Layman (2Pug) - Thursday, 23 October 2014, 06:40 GMT
  • Field changed: Percent Complete (100% → 0%)
I've found the same issue with a project that I'm working on. Everything built fine until I did an update a couple of weeks ago. I rewound my repo to known good build and it now fails with ...

/usr/include/boost/fusion/container/vector/vector.hpp:25: Error: '#' is not followed by a macro parameter
AUTOGEN: error: process for /home/work/daikin/dahmi/build/src/app/main.moc failed:
/usr/include/boost/fusion/container/vector/vector.hpp:25: Error: '#' is not followed by a macro parameter

moc failed...
src/app/CMakeFiles/dahmi_automoc.dir/build.make:49: recipe for target 'src/app/CMakeFiles/dahmi_automoc' failed
make[2]: *** [src/app/CMakeFiles/dahmi_automoc] Error 1
CMakeFiles/Makefile2:367: recipe for target 'src/app/CMakeFiles/dahmi_automoc.dir/all' failed
make[1]: *** [src/app/CMakeFiles/dahmi_automoc.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
/usr/include/boost/fusion/container/vector/vector.hpp:25: Error: '#' is not followed by a macro parameter
AUTOGEN: error: process for /home/work/daikin/dahmi/build/src/lib/qml/moc_qml.cpp failed:
/usr/include/boost/fusion/container/vector/vector.hpp:25: Error: '#' is not followed by a macro parameter
Comment by Richard Layman (2Pug) - Thursday, 23 October 2014, 13:13 GMT
Ok, I've done some testing and found out some more things about this issue. I've attached a stripped down version of the problem and found out how to make it happen but I'm still don't know how to fix it. I'm not sure if this is a fusion problem or a Qt problem, but everything works fine until you add a moc file to the main (which is needed by Qt). The reason I never saw this issue before was because I still had cached mocs in my CMake build, it wasn't until I cleared my cache (after I did my Arch update) that the problem showed up; so I probably had this issue even during the last known good build but never saw it due to the cached mocs. This looks like there's a conflict between fusion and qt. I'm going to talk to the fusion people first and see if they can find something. I wouldn't say this issue is 'Closed' yet unit I verify what it is.
(application/x-gzip)    fusion_error.tar.gz (2.6 KiB)
Comment by Richard Layman (2Pug) - Tuesday, 28 October 2014, 12:36 GMT
Ok, This turned out to be a bug created by Qt when it creates it's moc files. The fusion developers tracked it down and I've reported the bug to Qt and they are looking into it. You can make this as closed as far as I'm concerned.
Comment by Bartłomiej Piotrowski (Barthalion) - Tuesday, 28 October 2014, 17:52 GMT
Could you post the url here for reference?
Comment by Richard Layman (2Pug) - Wednesday, 29 October 2014, 11:14 GMT
Bug report to fusion
https://svn.boost.org/trac/boost/ticket/10688

Bug report to Qt
https://bugreports.qt-project.org/browse/QTBUG-42233

Qt Change
https://codereview.qt-project.org/#/c/98285/

Looks like they already fixed it and the fix is in the qt-base 5.4 branch
Comment by Bartłomiej Piotrowski (Barthalion) - Wednesday, 29 October 2014, 11:23 GMT
Thank you. I bet that our Qt maintainer will backport it if you create a new task.

Loading...