*** svalx_ is now known as svalx | 07:13 | |
*** svalx_ is now known as svalx | 07:18 | |
*** frinring_ is now known as frinring | 07:55 | |
*** svalx_1 is now known as svalx | 08:07 | |
*** radish_ is now known as radish | 11:00 | |
akaWolf | https://sailfishos.org/wiki/Build_Engineering nice article btw :) | 14:11 |
---|---|---|
deni | Whoops 😬 https://usercontent.irccloud-cdn.com/file/rpU03j5D/1538243946.JPG | 17:59 |
tortoisedoc | hey ho | 18:33 |
tortoisedoc | i have an issue with a package | 18:34 |
tortoisedoc | gcc in particular | 18:34 |
tortoisedoc | on the platform sdk, | 18:34 |
tortoisedoc | in a target, when installing gcc, I get "invalid cross-device link" | 18:34 |
tortoisedoc | the docs mention to ignore | 18:34 |
tortoisedoc | but then, subsequent packages cant resolve correctly /usr/bin/cc, even tho the file is there | 18:34 |
tortoisedoc | what's sb2 doing? | 18:35 |
tortoisedoc | mal : ping | 18:37 |
tortoisedoc | lbt : ping? | 18:37 |
mal | tortoisedoc: was? | 18:39 |
tortoisedoc | as per above :) | 18:39 |
tortoisedoc | mal : as per above? | 18:41 |
mal | tortoisedoc: hmm, trying to understand the issue, so you are trying to build gcc? | 18:41 |
tortoisedoc | mal : no, sorry, when installing gcc i get the "invalid cross-device link" | 18:43 |
tortoisedoc | then I follow the instructions from the platform sdk (mer), and ignore the error | 18:43 |
tortoisedoc | but then, when I install another package which requires /usr/bin/gcc, rpm cant resolve the file in question (/usr/bin/gcc) | 18:44 |
r0kk3rz | installing gcc? surely its already in the target | 19:07 |
mal | yes, why would it need to be installed manually | 19:09 |
tortoisedoc | r0kk3rz : okay, fair point; problem is, /usr/bin/gcc (and /usr/bin/cc) still are not recognized | 20:09 |
tortoisedoc | (even the preinstalled ones= | 20:09 |
tortoisedoc | (even the preinstalled ones) | 20:09 |
r0kk3rz | what needs those? | 20:09 |
tortoisedoc | rust compiler from sfietkonstantin | 20:10 |
tortoisedoc | and yes, tried on a fresh target -> same problem | 20:11 |
tortoisedoc | specifically http://repo.merproject.org/obs//home:/sfietkonstantin:/sailfish:/rust/sailfishos_i486/i486/rust-1.22.1-1.3.13.jolla.i486.rpm | 20:11 |
r0kk3rz | show output from build | 20:12 |
tortoisedoc | r0kk3rz : its rpm | 20:12 |
tortoisedoc | rpm -i for instance | 20:12 |
r0kk3rz | show output | 20:13 |
r0kk3rz | also, add the repo and install it properly | 20:14 |
tortoisedoc | https://pastebin.com/vfC7FTbs | 20:14 |
tortoisedoc | deps are installed | 20:14 |
tortoisedoc | binary seems to be the problem | 20:15 |
tortoisedoc | /usr/bin/cc specifically | 20:15 |
tortoisedoc | even --force fails | 20:15 |
tortoisedoc | I know that sb2 does some magic on the compiler (like gcc points to i486-meego-linux-gnu-gcc | 20:15 |
tortoisedoc | ) | 20:16 |
tortoisedoc | but the compiler works just fine and compiles | 20:16 |
tortoisedoc | sb2 -d does not help | 20:16 |
r0kk3rz | yes maybe that rust will need some mods to work with sb2 | 20:17 |
tortoisedoc | yeah | 20:21 |
tortoisedoc | well, good night | 20:21 |
coderus | What is fakeroot rpm -i inside target running in non-root sdk-build mode??? | 20:36 |
coderus | Don't you need to -m sdk-install -R for those things? | 20:37 |
r0kk3rz | in this instance i think the real issue is a dodgy Requires directive | 20:39 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!