*** saidi <saidi!~saidi@unaffiliated/saidi> has quit IRC | 00:07 | |
*** dp is now known as bq | 00:18 | |
mikernl91 | Hi everyone...I'm trying to add my own fstab to rootfs(of target) the problem is that 2 recipes are trying to install it and the error "file /etc/fstab conflicts between attempted installs" is shown.The implicated recipes are base-files_%.bb and dev-rootfs_%.bb. The latter is my recipe and the one i want to be the responsible to install | 01:04 |
---|---|---|
mikernl91 | fstab(without modifying anything else), i tried to usethe update-alternatives.bbclass without luck.The following is what i tried in my dev-rootfs_%.bb recipe ALTERNATIVE_base-files= "fstab"ALTERNATIVE_LINK_NAME[fstab] = "/etc/fstab"ALTERNATIVE_TARGET = "/etc/fstab"do_install () { install -d ${D}${sysconfdir} install -m 0755 ${MY_ETC}/fstab | 01:04 |
mikernl91 | ${D}${sysconfdir}/fstab}I hope you can give me any clue on this... thank you very much! | 01:04 |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 01:16 | |
*** camus <camus!~Instantbi@222.67.188.174> has joined #yocto | 01:42 | |
*** kaspter <kaspter!~Instantbi@101.93.194.160> has quit IRC | 01:45 | |
*** camus is now known as kaspter | 01:45 | |
kergoth | mikernl91: alternatives only works if all recipes providing the file use it. | 02:03 |
kergoth | mikernl91: you'd need to also bbappend base-files to use it there too | 02:03 |
kergoth | but you could just bbappend base-files to alter fstab directly rather than using your own recipe for it instead | 02:03 |
mikernl91 | kergoth: Thanks for the reply! | 02:47 |
mikernl91 | actually i did what you mentioned but, the reason i use another recipe is because i want to be able to to modify this fstab based on the image-recipe i'm building, i.e. adding the dev-rootfs in my IMAGE_INSTALL. Also i tried to use ROOTFS_POSTPROCESS_COMMAND but following this discussion https://narkive.com/XcannnRd:3.552.52 it looks like it is | 02:56 |
mikernl91 | better to avoid POSTPROCESS | 02:56 |
*** fl0v0 <fl0v0!~fvo@i5E869306.versanet.de> has joined #yocto | 03:26 | |
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto | 03:30 | |
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto | 03:31 | |
*** vmeson <vmeson!~rmacleod@24-52-239-53.cable.teksavvy.com> has quit IRC | 03:48 | |
*** bq is now known as bokchoi | 03:56 | |
*** wooosaiiii <wooosaiiii!~prix@89-212-21-243.static.t-2.net> has quit IRC | 05:04 | |
*** creich <creich!~unknown@2003:f6:af40:9410::39b> has joined #yocto | 05:13 | |
*** mikernl91 <mikernl91!bda60e5a@189.166.14.90> has quit IRC | 06:46 | |
*** kaspter <kaspter!~Instantbi@222.67.188.174> has quit IRC | 08:02 | |
*** kaspter <kaspter!~Instantbi@222.67.188.181> has joined #yocto | 08:04 | |
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto | 08:16 | |
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC | 08:21 | |
*** jwwww <jwwww!~magnet@lfbn-mon-1-581-143.w2-4.abo.wanadoo.fr> has joined #yocto | 08:53 | |
jwwww | Hello. | 08:53 |
*** Bunio_FH <Bunio_FH!~bunio@81-18-201-214.static.chello.pl> has joined #yocto | 09:20 | |
*** goliath <goliath!~goliath@2001:67c:20a1:1140:f4ff:ab63:d53:ed40> has joined #yocto | 09:30 | |
*** tlwoerner <tlwoerner!~Trevor@unaffiliated/tlwoerner> has quit IRC | 09:46 | |
*** tlwoerner <tlwoerner!~Trevor@unaffiliated/tlwoerner> has joined #yocto | 09:48 | |
*** pohly <pohly!~pohly@dyndsl-085-016-033-123.ewe-ip-backbone.de> has joined #yocto | 09:57 | |
*** goliath <goliath!~goliath@2001:67c:20a1:1140:f4ff:ab63:d53:ed40> has quit IRC | 11:13 | |
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC | 11:21 | |
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto | 12:12 | |
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto | 12:48 | |
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto | 12:57 | |
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC | 13:02 | |
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto | 13:04 | |
*** stuom1 <stuom1!3eecd81d@62.236.216.29> has joined #yocto | 13:25 | |
stuom1 | anybody have experience on situation where autotools based recipe seemingly succeeds without any problems but the actual files are not in the baked image? | 13:27 |
*** stuom1 <stuom1!3eecd81d@62.236.216.29> has quit IRC | 14:29 | |
*** mikernl91 <mikernl91!bda60e5a@189.166.14.90> has joined #yocto | 15:19 | |
*** bachp <bachp!bachpmatri@gateway/shell/matrix.org/x-ibaxlwrdhilhjprs> has left #yocto | 15:57 | |
*** vmeson <vmeson!~rmacleod@24-52-239-53.cable.teksavvy.com> has joined #yocto | 16:00 | |
*** stephano <stephano!~stephano@c-73-164-244-205.hsd1.or.comcast.net> has joined #yocto | 16:22 | |
*** Bunio_FH <Bunio_FH!~bunio@81-18-201-214.static.chello.pl> has quit IRC | 16:29 | |
*** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has joined #yocto | 16:55 | |
*** PaowZ <PaowZ!~PaowZ___@pai34-7-83-152-182-24.fbx.proxad.net> has quit IRC | 17:15 | |
*** tgamblin <tgamblin!~tgamblin@CPE64777de11593-CM64777de11590.cpe.net.cable.rogers.com> has quit IRC | 17:26 | |
*** tgamblin <tgamblin!~tgamblin@CPE64777de11593-CM64777de11590.cpe.net.cable.rogers.com> has joined #yocto | 17:28 | |
*** mikernl91 <mikernl91!bda60e5a@189.166.14.90> has left #yocto | 17:59 | |
*** micka <micka!~micka@reverse-75.fdn.fr> has quit IRC | 18:12 | |
*** micka <micka!~micka@reverse-75.fdn.fr> has joined #yocto | 18:12 | |
*** goliath <goliath!~goliath@clnet-p04-043.ikbnet.co.at> has joined #yocto | 19:24 | |
JPEW | Hmm.... glibc dlopen()'s libgcc_s in some cases, but it's not in RDEPENDS so it won't necessarily get pulled into the rootfs... | 19:45 |
khem | thats one but there are more whack-a-moles | 19:53 |
khem | e.g. if app use system() API to open random binaries | 19:53 |
khem | we only detect shlibs that too only direct deps | 19:54 |
kergoth | that's where explicit rdepends aditions come in, we can only do so much | 19:54 |
* khem nods | 19:54 | |
JPEW | Sure, I'm more interested in where the correct place to add the RDEPENDS is. My first instict would be to add it to the glibc package | 20:09 |
JPEW | RDEPENDS_${PN} += "libgcc" | 20:09 |
JPEW | This of course, rebuilds *everything* so I'm a little leery :) | 20:10 |
*** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has quit IRC | 20:12 | |
khem | that is not really correct representation, glibc does not need it | 20:22 |
khem | but you might want to override the pthreads unwind behaviour | 20:22 |
khem | in app | 20:22 |
JPEW | The app is python | 20:23 |
khem | then it should ask for it | 20:23 |
*** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has joined #yocto | 21:11 | |
*** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has quit IRC | 21:29 | |
*** xyzzy42 <xyzzy42!~trentpi@198.162.93.26> has joined #yocto | 21:38 | |
xyzzy42 | I'm getting an error on the linux-libc-headers package build, "Failed to spawn fakeroot worker to run ...: Broken Pipe" | 21:39 |
xyzzy42 | Looking into that a bit, I find that if I try to manually run pseudo, out of tmp/sysroots-components/x86_64/pseudo-native/usr/bin/pseudo, it fails | 21:40 |
xyzzy42 | The reason is it was apparently compiled against my native glibc, 2.30, while when it runs, it's using a glibc from sysroot-uninative, which is version 2.26 | 21:41 |
xyzzy42 | should I expect psuedo to run when invoked directly? It doesn't require some kind of special invocation (LD_PRELOAD, fakeroot, etc) to use the correct libraries? | 21:43 |
khem | xyzzy42: whats your build host distro | 21:59 |
khem | uninative is preferred to be used and it seems thats in play in your build which is ok | 22:00 |
xyzzy42 | khem, fedora 31 | 22:01 |
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto | 22:03 | |
khem | xyzzy42: ok I think f31 is used on some of Autobuilders nodes too so this issue should have appeared ther | 22:12 |
*** pohly <pohly!~pohly@dyndsl-085-016-033-123.ewe-ip-backbone.de> has quit IRC | 22:12 | |
xyzzy42 | Am I correct the poky has built a native version of glibc 2.5.90 to link native executables against? | 22:13 |
khem | oh only uptill f30 are there https://autobuilder.yoctoproject.org/typhoon/#/workers | 22:13 |
khem | but I am sure there are users here who use f31, I dont so I have not seen the issue myself | 22:14 |
xyzzy42 | This is an old poky I'm using, so it's possible that the issue isn't present anymore | 22:15 |
khem | xyzzy42: pseudo perhaps should be run in uninative env if you have used that to build it | 22:15 |
xyzzy42 | I didn't see any bugs or commits that appear related to this | 22:15 |
khem | hmmm which version of poky | 22:15 |
xyzzy42 | It's a snapshot that was taken a bit after rocko-18.0.1 | 22:16 |
khem | yes because there are tested distros and thats what would be recommended to build for a given release | 22:16 |
xyzzy42 | how would I see if psuedo-native was built in an uninative env? | 22:17 |
khem | :) so you should mention that first what does bitbake -e busybox | grep "^SANITY_TESTED_DISTROS=" say ? | 22:18 |
xyzzy42 | empty | 22:19 |
xyzzy42 | I'm sure this poky was not build on f31, since it predates f31 by almost 3 years | 22:19 |
xyzzy42 | but it's not like the distro is fundamentally at odds with building. There's some specific problem here. | 22:22 |
xyzzy42 | It seems to be related to the library choice being different at link time vs run time | 22:23 |
xyzzy42 | It's entirely unclear to me where the heck the libc-2.25.90.so in sysroots-uninative came from. I see no other files from a native build of glibc. As well, trying to combine the host gcc with another glibc seems unlikely to work very well. | 22:26 |
kergoth | host version is a large factor. getting an old release building on a new distro is non-trivial due to compiler changes (warnings changing to errors, etc) and glibc version incompatibilities, etc | 22:27 |
*** khem <khem!~khem@unaffiliated/khem> has quit IRC | 22:27 | |
kergoth | if you look through oe-core ou'll find fixes that went in for newer glibc versions | 22:27 |
kergoth | through git history, that is | 22:27 |
xyzzy42 | kergoth, yes, I've had to fix a few of those to get this far. host gcc+glib has issues with old version of package X | 22:29 |
xyzzy42 | here, it's not clear to me what poky is trying to do. I don't see any flaw in pseudo itself. It looks like poky is trying to link it against one glibc and run it with another, which is just broken by design. | 22:31 |
*** khem <khem!~khem@unaffiliated/khem> has joined #yocto | 22:39 | |
*** thannoy_ <thannoy_!~anthony@134-48-190-109.dsl.ovh.fr> has quit IRC | 22:41 | |
*** thannoy_ <thannoy_!~anthony@134-48-190-109.dsl.ovh.fr> has joined #yocto | 22:41 | |
xyzzy42 | I see where the glibc-2.25.90 is coming from. The uninative system downloads a pre-compiled c library and tries to use that. | 22:43 |
khem | xyzzy42: right, thats the way to nullify different libc APIs that different distros will otherwise offer | 22:44 |
xyzzy42 | looks like it's an attempt to allow copying binaries for host tools across different distributions | 22:44 |
khem | if you do not care for that then I would say disable the feature | 22:45 |
khem | conf/distro/poky.conf:require conf/distro/include/yocto-uninative.inc | 22:45 |
khem | conf/distro/poky.conf:INHERIT += "uninative" | 22:45 |
khem | comment those out | 22:45 |
xyzzy42 | Hmm, I don't see how that can work very well. What happens when a host library linked against the host's glibc is used in the same executable as the different uninative glibc? | 22:45 |
khem | generally that wont happen because it modifies the ldso | 22:59 |
khem | loading path | 22:59 |
khem | ldso will be used from uninative and that the hook to load the libs | 22:59 |
xyzzy42 | yes, I see the patchelf to change the interpreter to a local one. That's where it change the lib search order to uninative first | 23:00 |
xyzzy42 | also while "ldd native-build-exe" reports the incorrect libs, since it doesn't appear to reflect the ELF's interpreter and instead uses the host's | 23:01 |
xyzzy42 | but it seems like as soon as any build of a native executable uses a library which is not in uninative it will create the possibility of trying to pull in conflicting library versions | 23:02 |
xyzzy42 | I've tried to stop using uninative, I'm only interested in building an image, not a cross-distro SDK, but it looks like it's still getting pulled in. | 23:04 |
xyzzy42 | If there is a log line of "DEBUG: Inheriting /.../uninative.bbclass", that's means I've see got something inheriting it, right? | 23:05 |
xyzzy42 | Is the goal of uninative to replace _every_ host library with a locally built/downloaded one? | 23:10 |
khem | not all | 23:52 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!