--- Comment #23 from Tom Stellard <> ---
(In reply to Ron Olson from comment #22)
> Swift is very sensitive to the location of all parts of its toolchain; "lib"
> is hard-coded in some way or another across all the projects that make up
> the Swift toolchain. The past couple of months have been spent finding,
> analyzing, and replacing all appropriate instances of lib with lib64 and the
> result is Swift segfaults 100% of the time.
> That said, looking at /usr/lib64, it's populated with actual shared library
> files, while Swift puts its files inside subdirectories (e.g.
> /usr/lib/swift), so it's not dropping a bunch of .so files in /usr/lib.

Ok, can you add a comment to the spec file explaining why you are using

You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
package-review mailing list --
To unsubscribe send an email to

Reply via email to