The Samba-Bugzilla – Bug 10548
Samba 4.X fails to build on e.g. FreeBSD due to link flag ordering bug
Last modified: 2016-08-01 19:26:02 UTC
When a library or system (like cups) provides an RPATH,
e.g. with -Wl,-R or -Wl,-rpath, this was added by waf
to the LINKFLAGS, wich was later prepended to our RPATH.
But if the path by chance contains an older version of
one of our internal libraries like talloc, this would lead
to linking the too old talloc into our binaries.
This has been observed on, e.g., FreeBSD, but it is a general
Created attachment 9845 [details]
patch for 4.0, cherry-picked from master
Patch from master for 4.0.
Added cherry-pick and bug info.
Created attachment 9846 [details]
patch for v4-1-test, picked from master
Patch from master.
Added cherry-pick-info and bug-info.
Assigning to Karolin for inclusion in 4.0.NEXT and 4.1.NEXT
Pushed to autobuild-v[4-1|4-0]-test.
Since the patch is pushed to the branches, shouldn't the bug be switchet to resolved?
(In reply to comment #5)
> Since the patch is pushed to the branches, shouldn't the bug be switchet to
Pushed to both branches.
Closing out bug report.
This fix is completely broken I'm afraid and either needs reverting or fixing.
Take a look at:
Waf is a broken build system, does not correctly cross compile, has wasted 6+ hours of my time and WE MUST MOVE AWAY FROM IT !
(In reply to Jeremy Allison from comment #7)
> This fix is completely broken I'm afraid and either needs reverting or fixing.
> Take a look at:
> for details.
> Waf is a broken build system, does not correctly cross compile, has wasted 6+ > hours of my time and WE MUST MOVE AWAY FROM IT !
Jeremy, could you please stop hijacking bugs?
We should have a bug for failure to cross-compile.
And this would imho be a feature enhancement, since
for all I can tell, this never worked for our waf build.
But maybe I am wrong.
Anyways. This bug here is fixed. The freebsd build works just fine.
And the error that shows up in the description of bug #11165 has no relationship to the patches attached to this bug. the linkflags.remove(x) does not appear in these patches.
Closing the bug again and removing the misleading dependency.
*** Bug 10515 has been marked as a duplicate of this bug. ***