mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
building on i686 fails with wrong multilib library path #6389
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#6389
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @andreasbaumann on GitHub (Nov 23, 2017).
Please provide the following information
qBittorrent version and Operating System
git version
d74efd839fIf on linux, libtorrent and Qt version
n/a
What is the problem
./configure --prefix=/usr
fails with:
What is the expected behavior
32-bit libraries on a true 32-bit system are in /usr/lib, at
least on Archlinux32
Steps to reproduce
./confgiure --prefix
Extra info(if any)
The problem is in the m4/ax_boost_system.m4 macro. It sets LDFLAGS in wrong ways.
Similar problems arise with CPPFLAGS, CXXFLAGS and setting -DFORTIFY_SOURCE=2
without -O2.
I consider this an upstream issue with the autoconf-archive macros.
@andreasbaumann commented on GitHub (Nov 23, 2017):
I'm overwritting them in 'configure.ac' after the AX_BOOST_BASE which just sets BOOST_LDFLAGS
incorrectly:
@andreasbaumann commented on GitHub (Nov 23, 2017):
The problem around fortify, optimization and CPPFLAGS has disappeared by miracle (cannot reproduce).
The BOOST_LDFLAGS problem remains and the workaround mentioned above works (though
I know, this is not a permanent and proper fix to the problem).
@surfernsk commented on GitHub (Nov 23, 2017):
@andreasbaumann same on Fedora, solved it with a patch /m4/ax_boost_base.m4
@andreasbaumann commented on GitHub (Nov 23, 2017):
@surfernsk thanks, that's the proper way of patching. :-)