| Summary: | dev-vcs/subversion-1.7.0: crosscompile failure during linking | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Thomas Sachau <tommy> |
| Component: | New packages | Assignee: | Thomas Sachau <tommy> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | edt, mario.fetka, pageexec |
| Priority: | Normal | ||
| Version: | autobuilds | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | build.log | ||
|
Description
Thomas Sachau
2011-10-13 18:31:44 UTC
I am seeing the same error during install with linking with both 1.7.0 and 1.7.1 Any update here? i would like to add, that this new build system is not parallel-build save, i today tried building 1.7.1 and during the first run it failed, because a cp did not find the source file, with MAKEOPTS="-j1" it does again get to the linking with the already mentioned error. After some more testing, looking at the build.log and the configure options, i have at least some workaround. The build system uses by default the no-undefined flag for LDFLAGS. This results in the failure with related message. As a workaround, it has a configure switch called "--disable-disallowing-of-undefined-references", which does remove the flag from LDFLAGS and allows me to cross-compile subversion with multilib-portage. So here are the issues with subversion-1.7.*: -no parallel build support -linking issue with --no-undefined LDFLAG (default enabled in the build system) I have not fully tested the 32bit version, so i cannot say, if this switch does cause any harm or if the resulting files may fail in some way. On another note: After i installed subversion-1.7*, the following cross-compile runs fine, so it seems to link against currently installed version instead of the actually compiled version, which causes the undefined symbols in the first place. Resolved with 1.7.4, should be on your local rsync mirror in a few hours. |