Ticket #35210 (closed defect: fixed)
kdepim4: Parse error at "BOOST_JOIN"
| Reported by: | mparchet@… | Owned by: | sharky@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.1.1 |
| Keywords: | Cc: | michaelld@…, bjoern.ricks@…, mircsicz@…, nicos@…, mk@… | |
| Port: | kdepim4 |
Description
Hello,
I wold like to reinstall kdepim4 (after a uninstall ) but the kdepim4 build process stop due to an error. (see attachment)
Can you help me please ?
Best regards
mparchet
Attachments
Change History
comment:1 Changed 10 months ago by ryandesign@…
- Cc snc@… removed
- Owner changed from macports-tickets@… to snc@…
- Keywords kdepim4 removed
comment:2 Changed 10 months ago by mparchet@…
Hello,
I clean kdepim4 And I tried to build again but it's get alway an error.
Can you help me please ?
Best regards
mparchet
comment:3 Changed 10 months ago by snc@…
- Owner changed from snc@… to sharky@…
- Cc michaelld@… added; sharky@… removed
comment:4 Changed 9 months ago by greisberger@…
Same problem here.
A Google search with « Parse error at "BOOST_JOIN" » suggest a Qt MOC error with BOOST version >= 1.48
comment:5 Changed 7 months ago by macsforever2000@…
- Cc mircsicz@… added
Cc'ing reporter of duplicate #36544.
Actual error is:
:info:build opt/local/include/boost/type_traits/detail/has_binary_operator.hp:50: Parse error at "BOOST_JOIN"
comment:6 Changed 7 months ago by ryandesign@…
- Summary changed from Unable to build kdepim4 to kdepim4: Parse error at "BOOST_JOIN"
comment:7 Changed 7 months ago by mparchet@…
Hello,
It's a qt4.8.3 problem isen't it ?
What's your opinion about this bug ?
Tanks for your help
Best regards
mparchet
comment:10 Changed 7 months ago by nicos@…
It appears that other ports from KDE which depend on boost have the same problem, such as rocs.
A solution is proposed on https://bugs.kde.org/show_bug.cgi?id=304111 to solve the issue for all KDE. It requires however to patch automoc directly (see patch attached).
comment:11 Changed 7 months ago by mk@…
Committed in r98803. Hope it will do the trick for all ports in question.
comment:12 Changed 7 months ago by nicos@…
It seems to me that this issue has been solved with the previous commit. Would it be possible to confirm in order to close the ticket ?
comment:13 Changed 7 months ago by mparchet@…
Hello,
Yes, you can close this ticket : close: bug fixed.
Best regards
mparchet


The log says:
These "skipping completed" lines show that this was not a clean build attempt. Always clean and try again before filing a bug report:
If the problem occurs again after that, attach the new main.log file.