boost: fails to build on mpc85xx + uClibc #1621
Comments
sairon
changed the title
|
I will look into it ASAP. On 27 July 2015 at 14:18, Jan Čermák notifications@github.com wrote:
Carlos Miguel Ferreira |
|
BTW, did you try to compile Boost.Log using the regular glibc for that On 27 July 2015 at 15:20, Carlos Ferreira carlosmf.pt@gmail.com wrote:
Carlos Miguel Ferreira |
|
I did not - but according to all the clues (OK with musl, OK on other architectures, plus the linked issue), it should be OK with anything else than the specific combination of uClibc + PPC target. The patch sent by Romain Naour fixes the issue but I can't decide whether it is an acceptable solution or just a hack. You may also disable the problematic library only on the specific target but it'd require some refactoring of DefineBoostLibrary macro (because it does add all the libraries to the boost metapackage anyway). |
|
I'm more inclined to disable the package for that specific combination (target + uclibc). That patch messes with the code itself so i'm reluctant in accepting it without the approval of the Boost devs. Since uclibc is an outdated lib and no longer maintained, it should be avoided whenever possible. |
This update solves two issues: 1) Incompatibility with the combination of using Target mpc85xx and uclibc at the same time[1]. - For now, Boost is disabled when the respective combination is detected. 2) The selection of Boost.Locale was not activating the build with full language support. [1] - openwrt#1621 Signed-off-by: Carlos Ferreira <carlosmf.pt@gmail.com>
|
FYY I decided to disable Boost for the problematic combination. @thess From my part, this issue is solved. |
|
Great, thanks. It think it should be also backported to for-15.05 branch to make boost available on mpc85xx. And I'm still hoping to receive an answer for my question if/where I can check for failing builds of CC packages. |
|
@sairon release builds are done manually and usually someone will come around and open a ticket if a package is failing. |
|
Thanks @sbyx, so it seems that boost on mpc85xx dropped off the radar... |
|
Yes @sairon. Its a matter of bug reporting, when someone hits a problem. In this specific case, it was the combination of target and uclibc. |
Major Updates
- Added support for Python 3.5.
- Removed the restriction for the target MPC85xx when using uclibc [1].
- No longer required since uclibc was removed from trunk.
- Added option to force static compilation.
- Added option to force linking statically to the C++ standard library and compiler runtime support libraries.
- Added option to disable multithreading support. It can be helpfull for those who wish to fully optimise their code.
- Some boost libraries will require multithreading to be active. For those, this option is active as a requirement.
Minor Updates
- Added -fPIC to CFLags [2].
- python requires independent position code.
References:
[1] - openwrt#1621
[2] - openwrt#1938
Signed-off-by: Carlos M. Ferreira <carlosmf.pt@gmail.com>
|
FYI |
Major Updates
- Added support for Python 3.5.
- Removed the restriction for the target MPC85xx when using uclibc [1].
- No longer required since uclibc was removed from trunk.
- Added option to force static compilation.
- Added option to force linking statically to the C++ standard library and compiler runtime support libraries.
- Added option to disable multithreading support. It can be helpfull for those who wish to fully optimise their code.
- Some boost libraries will require multithreading to be active. For those, this option is active as a requirement.
Minor Updates
- Added -fPIC to CFLags [2].
- python requires independent position code.
References:
[1] - openwrt#1621
[2] - openwrt#1938
Signed-off-by: Carlos M. Ferreira <carlosmf.pt@gmail.com>
Major Updates
- Added support for Python 3.5.
- Removed the restriction for the target MPC85xx when using uclibc [1].
- No longer required since uclibc was removed from trunk.
- Added option to force static compilation.
- Added option to force linking statically to the C++ standard library and compiler runtime support libraries.
- Added option to disable multithreading support. It can be helpfull for those who wish to fully optimise their code.
- Some boost libraries will require multithreading to be active. For those, this option is active as a requirement.
Minor Updates
- Added -fPIC to CFLags [2].
- python requires independent position code when statically compiling.
References:
[1] - openwrt#1621
[2] - openwrt#1938
Signed-off-by: Carlos M. Ferreira <carlosmf.pt@gmail.com>
|
@thess this issue can be closed. Can you do it please? |
|
@sairon - Issue is over 1 yr old and uClibc no longer supported. Closing this. If there is still any issues with the current version and target support, please open a new issue. Better yet, submit a new PR to solve the problem. |
It seems that boost is not available for mpc85xx architecture, while it's available for other ones. After some searching, I found out that problem might be the same as reported in Buildroot few months ago: https://patchwork.ozlabs.org/patch/472878/
@ClaymorePT, can you decide what to do - whether to disable failing libraries for mpc85xx or to include the proposed patch?
Also, can anyone tell me (maybe @jow-, @sbyx or @thess), where can I find what package builds are currently failing? It seems to me that buildbot broken packages page (e.g. http://buildbot.openwrt.org:8010/broken_packages/mpc85xx/) contains only results for openwrt trunk + latest packages, where boost builds fine, probably because there's musl instead of uClibc.
The text was updated successfully, but these errors were encountered: