-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cross-i686 compiler: keep sysroot /lib symlink #14401
Conversation
firefox-esr 68.1.0 complains: > 0:06.67 DEBUG: | /usr/lib/gcc/i686-pc-linux-gnu/9.2.0/../../../../i686-pc-linux-gnu/bin/ld: cannot find /lib/libc.so.6 inside /usr/i686-pc-linux-gnu > 0:06.67 DEBUG: | /usr/lib/gcc/i686-pc-linux-gnu/9.2.0/../../../../i686-pc-linux-gnu/bin/ld: cannot find /lib/ld-linux.so.2 inside /usr/i686-pc-linux-gnu
firefox-esr 68.1.0 complains: > 0:06.67 DEBUG: | /usr/lib/gcc/i686-pc-linux-gnu/9.2.0/../../../../i686-pc-linux-gnu/bin/ld: cannot find /lib/libc.so.6 inside /usr/i686-pc-linux-gnu > 0:06.67 DEBUG: | /usr/lib/gcc/i686-pc-linux-gnu/9.2.0/../../../../i686-pc-linux-gnu/bin/ld: cannot find /lib/ld-linux.so.2 inside /usr/i686-pc-linux-gnu [skip ci]
(Unrelated to you actual PR)
That's probably why nobody noticed before |
On September 11, 2019 7:51:08 PM UTC, Piraty ***@***.***> wrote:
(Unrelated to you actual PR)
You don't need to cross-compile from x86_64* to i686 and are better off
using a masterdir with the desired arch instead:
```
./xbps-src -m masterdir-i686 binary-bootstrap i686
./xbps-src -m masterdir-i686 pkg foo
```
That's probably why nobody noticed before
Well, I knew we can bootstrap i686 in x86_64.
I tested that build in my PR, see first comment.
--
Danh
|
Ping |
I looked into it, but cannot reproduce so far. Crosscompiling various packages from an x86_64 masterdir to i686 didn't show anything unusual.
Can you please provide a command to show off the issue? Please use a fresh masterdir ( |
Weird, I can't reproduce the issue anymore. |
|
When packaging Firefox ESR 68.1.0 #14229 , and cross compile i686 from x86_64,
I received this complains:
I didn't run into this complain when packaging aarch64 from x86_64,
I have a different problem when packaging ppc64le from x86_64