**** BEGIN LOGGING AT Tue Apr 23 02:59:57 2019 Apr 23 07:11:24 good morning Apr 23 07:12:23 jow: i'm learning ABI_VERSION now Apr 23 07:12:24 jow: I noticed commit https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=488e7ccfbc3afc66ad6df412c9ee57c33d75ca0f that bumped libnftnl 1.1.1 -> 1.1.2 and according to the https://abi-laboratory.pro/index.php?view=timeline&l=libnftnl there was ABI change Apr 23 07:13:06 jow: does it mean that commit was wrong as it didn't bumpd ABI_VERSION:=7 to 11? Apr 23 07:25:13 rmilecki: correct Apr 23 07:26:24 jow: is CMakeLists's SOVERSION a good source for ABI_VERSION? right now I'm looking at https://github.com/blunderer/libroxml/commit/a9cbea91bba7d3e4485d8ce6f6d235d43d44ab4e Apr 23 07:26:36 rmilecki: it is Apr 23 07:26:40 thanks Apr 23 07:27:38 rmilecki: https://github.com/KanjiMonster/maintainer-tools/blob/master/check-abi-versions.pl Apr 23 07:42:17 is also helpful, you can let it scan a directory of .ipk archives and it will provide suggstions Apr 23 07:42:17 bbl Apr 23 07:42:17 train arriving **** BEGIN LOGGING AT Tue Apr 23 07:42:34 2019 Apr 23 09:16:45 is the overwrite through overlay mechanism as talked about in the link still valid? https://lists.openwrt.org/pipermail/openwrt-devel/2016-October/003360.html Apr 23 09:21:31 charolastra: fwiw, this is what I'm using (I'm the Karl addressed there) https://zerobin.net/?bf7198830d6a43dc#BSf1Zczi11Kzp5gUiqUZSUsg8Z9nOJ7j4b4Wi/OoZts= Apr 23 09:22:14 that's still working on 1806 and master builds, so I haven't touched it since. Apr 23 09:23:31 and you place that in that base-files.mk overlay? Apr 23 09:25:55 that snippet is from my own package makefile, I never used the approach documented in that email Apr 23 09:40:54 charolastra: i added another way of handling that, let me find it Apr 23 09:42:06 charolastra: b5222924059f5146007a02e33d317f2c04d7dd0b ("base-files: add support for overlaying rootfs content") Apr 23 09:43:01 charolastra: so you package just need to come with "rootfs-overlay" directory Apr 23 09:43:31 $(INSTALL_DIR) $(1)/rootfs-overlay Apr 23 09:43:33 $(CP) $(PKG_BUILD_DIR)/customfile $(1)/rootfs-overlay/ Apr 23 09:44:33 did you add that to the "creating packages" wiki page? Apr 23 09:44:59 documenting that certain directories in your package would be magically treated like never before? Apr 23 09:46:20 karlp: i didn't Apr 23 09:47:34 ABI_VERSION isn't on that page either (yet) Apr 23 09:47:35 * ldir has ordered an apu2 - at a discounted price - yay! Apr 23 09:47:57 oh, it's because https://openwrt.org/docs/guide-developer/packages and https://openwrt.org/docs/guide-developer/package-policies are separate Apr 23 10:09:58 can somebody tell me how to reach the 192.168.1.1 page of openwrt (virtualized in virtual box probably still the same ip but i need to chnge it in order to reach it now i'm only redirected to my router 192.....) Apr 23 10:17:52 use your virtual box console to change the openwrt IP? Apr 23 10:31:06 on which platform/service/selfhostet thing should our unittest run? travis? jenkins? any preference? I've have to start lxc containers as I'm writing one fw3 unit tests for a bug. Apr 23 10:31:08 jow: ^ Apr 23 10:33:24 can somebody answer my question?? Apr 23 10:37:20 borix: use different IP ranges for different networks Apr 23 10:37:31 assuming I understood that"description" correctly Apr 23 10:37:57 i need the command that gives me access the router at 192.168.0.1 or 172.16.0.1 instead of 192.168.1.1 Apr 23 10:49:00 Borix: edit /etc/config/network, use uci.. wiki is friend on openwrt side of things... VM itself you need to figure out on your own Apr 23 10:50:49 borix: use the virtualbox console to reconfigure things. Apr 23 11:07:14 i tried with uci set network.lan.ipaddr='new-ip-address' and still not finding my openwrt(virtualized) Apr 23 11:12:26 remembered to "uci commit" too? also... is your VM network attached to any "real" network, or other menas how you want to reach the VM trough networking Apr 23 11:13:46 rmilecki: didn't have any luck with your solution. meaning creating a rootfs-overlay in the root folder isn't enough. do i need to $(CP) all indivudial files in the install routine of the makefile? Apr 23 11:15:09 charolastra: "cp" is already handled in functions.sh - see https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=b5222924059f5146007a02e33d317f2c04d7dd0b Apr 23 11:15:29 yeah, was refering to the 2 lines you posted above Apr 23 11:16:22 charolastra: oh, wait Apr 23 11:16:30 charolastra: you seem to need install-overlay step in your Makefile Apr 23 11:16:54 you *don't* manually deal with rootfs-overlay Apr 23 11:17:04 in /install-overlay you just use $(1) Apr 23 11:17:17 sorry, i misread that commit at first Apr 23 11:17:36 borix: you also need "ifup lan" to actually apply the new ip Apr 23 11:18:03 lynxis: no preference, they all suck Apr 23 11:18:39 charolastra: define Package/charolastra/install-overlay and inside do something like Apr 23 11:18:43 $(INSTALL_DIR) $(1)/lib/ Apr 23 11:18:45 $(INSTALL_DATA) $(PKG_INSTALL_DIR)/lib/custom.so $(1)/lib/ Apr 23 11:18:49 did it alreadt jow Apr 23 11:19:19 we need to document that /install-overlay Apr 23 11:20:34 borix: then you problem is elsewhere. check your virtual network settings in vbox, also see that they don't collide with your host network etc. Apr 23 11:20:35 that would be great. i'm not used to Makefiles :/ Apr 23 11:21:11 charolastra: /install-overlay uses the same "syntax" (method?) as /install Apr 23 11:21:20 charolastra: so you have luckily a lot of examples Apr 23 11:25:00 ah, now i get it Apr 23 11:27:05 charolastra: cool :) Apr 23 13:08:40 I am having trouble building python from a fresh copy of OpenWrt-18.06 Apr 23 13:09:27 Here is the error: bash: /home/brucet/buildbot/source/staging_dir/hostpkg/bin/pip: No such file or directory Apr 23 13:10:25 I understand that the host version pip is supposed to be installed in this directory. It is not. Apr 23 13:11:34 Here is the version of pip I have on the host machine: pip 9.0.1 from /usr/lib/python2.7/dist-packages (python 2.7) Apr 23 13:15:14 I believe the host version of pip is supposed to get installed as a byproduct of compiling python3. Apr 23 13:21:09 I just built python3 and still pip is not in staging_dir/hostpkg/bin/. Apr 23 13:28:09 I think the problem may be that python-setup tools does not install on my debian host machine Apr 23 13:29:38 Here is the error on the host machine when I try to install pip setuptools Apr 23 13:29:52 Could not find a version that satisfies the requirement python-setuptools (from versions: ) Apr 23 14:31:42 Is anyone here??? Apr 23 14:32:47 sometimes Apr 23 14:33:21 well. I already described the problem I am having. Apr 23 14:33:50 I had a working build environment. Apr 23 14:34:14 I think it fell apart when I upgraded pip on the host machine for cross compiling Apr 23 14:34:55 Maybe Openwrt python build requires an older version of python / pip?? Apr 23 14:39:20 When I try: Apr 23 14:39:25 make -j1 V=sc package/python-pip/compile Apr 23 14:39:40 It says there is no target for python-pip Apr 23 14:39:52 Its enabled in manuconfig Apr 23 14:40:39 It seems unbelievably difficult to create a working cross compile environment for OpenWrt Apr 23 14:41:02 Is there maybe a ready made virtual machine image for this? Apr 23 14:48:53 openwrt python packages aim to provide their entire infrastructure themselves, any dependency on host python packages is a bug Apr 23 14:49:35 Sounds nice in theory Apr 23 14:51:10 make package/python-pip/compile should work Apr 23 14:51:31 Nope Apr 23 14:52:04 This is a fresh copy of OpenWrt Apr 23 14:52:21 did you run ./scripts/feeds update; ./scripts/feeds install python-pip ? Apr 23 14:52:21 Did you enable python-pip in menuconfig? Apr 23 14:52:28 yes Apr 23 14:52:31 try clearing the build env tmp directory Apr 23 14:53:09 The core of the problem is in the directory staging_dir/hostpkg/bin Apr 23 14:53:29 The build system requires a version of pip in that directory Apr 23 14:54:21 Unfortunately, default make does not install a host version of pip in that directory. Apr 23 14:54:29 what about make package/python-pip/host/install ? Apr 23 14:54:35 sorry package/python-pip/host/compile Apr 23 14:54:46 Let me try Apr 23 14:54:59 I didn't know about the host directive. Apr 23 14:55:16 I am right now rebuilding without python in menuconfig Apr 23 14:55:27 I want to make sure that works Apr 23 14:55:33 ok Apr 23 14:55:48 I habe python3 in menuconfig and that works. Apr 23 14:57:00 Once this build finishes I will try to build package/python-pip/host/compile Apr 23 14:58:02 okay. if you keep facing issues, I suggest to raise an issue in the openwrt/packages github repo. Alexandru, the python maintainer is usually quite responsive Apr 23 14:58:25 and it should just work, in any case it is not meant to be complex or error prone unless you managed to hit some bug Apr 23 14:58:39 OK. I know alexandru Apr 23 15:00:19 I have been working with alexandru because I am creating new python package for OpenWrt Apr 23 15:00:54 I ran into trouble when I tried to make the package using a clean build (make dirclean) Apr 23 15:01:40 Now I can't even do a build from a fresh copy of OpenWrt without the new package Apr 23 15:01:46 Very frustrating Apr 23 15:13:35 brucetho_: that sounds odd. Whats is the issue you see? Apr 23 15:14:04 OK. The build without python (only python3) works fine Apr 23 15:14:26 I will add python and pip back and try the host compile Apr 23 15:17:14 The core issue is that there is supposed to be a host version of pip in staging_dir/hostpkg/bin Apr 23 15:17:25 It's not there Apr 23 15:20:15 make package/python-pip/host/compile does not work. No rule. The python-pip package is enabled in manuconfig Apr 23 15:23:16 Same problem Apr 23 15:24:10 Enabling pip in menuconfig causes python and associated packages to be enabled. Apr 23 15:26:30 try clearing the build env tmp directory: Can you clarify? Apr 23 15:27:25 Python build fails because (I think) pip was never built. Apr 23 15:28:08 And "make package/python-pip/host/compile" does not work. No rule Apr 23 15:30:21 thats very odd Apr 23 15:31:03 This is a fresh copy of OpenWrt from Github Apr 23 15:31:10 18.04 Apr 23 15:31:19 if you run package/feeds/packages/ do you see a working "python-pip" symlink? Or is it broken? Apr 23 15:31:28 *run ls -lh package/feeds/packages/ Apr 23 15:32:38 also yes, try rm -r tmp/ (not /tmp) to flush any cached manifests Apr 23 15:36:48 need to run, I hope you can solve it Apr 23 15:37:04 Trying it Apr 23 15:38:12 did you try a simple "make" first? Apr 23 15:38:20 to make sure everything needed is built Apr 23 15:38:26 yes Apr 23 15:38:49 the "No rule to make target" hints at the fact that the python-pip makefile is not properly staged, for wahtever reason Apr 23 15:39:03 ls -lh package/feeds/packages/ | grep piplrwxrwxrwx 1 brucet brucet 51 Apr 22 17:05 python-pip-conf -> ../../../feeds/packages/lang/python/python-pip-conf Apr 23 15:39:05 corrupt feed, missing host tools, too new host system, buildroot moved on filesystem after initial build Apr 23 15:39:29 OK. Apr 23 15:39:50 Note that there is no symlink for pip Apr 23 15:41:10 python-pip-conf builds Apr 23 15:41:34 I am very sorry, I was looking at the lede-17.01 branch in my package feed copy Apr 23 15:42:17 seems python-pip is now part of python / python3 respectively Apr 23 15:42:42 so make package/python/host/compile or package/python3/host/compile should stage pip or pip3 respectively Apr 23 15:43:04 but maybe your host system interacts in unintended ways with the python host build, leading to a pip failure Apr 23 15:43:06 Should I remove python-pip from menuconfig? Apr 23 15:43:12 nono, its fine Apr 23 15:43:29 just the make target for python-pip is package/python/... Apr 23 15:43:41 Ah Apr 23 15:43:43 since the python source package provides (among others) the python-pip binary package Apr 23 15:44:34 maybe also try a make package/python/host/{clean,compile} V=s Apr 23 15:45:00 also consider redirecting the entire output to a file, then you can search for bin/pip occurences in it Apr 23 15:45:43 ok, afk for real now, train arrives. bbl Apr 23 15:45:59 Thx Apr 23 16:29:46 Hi all, does anyone know where the kernel .config file is actually changed. I'm trying to follow the logic between package/linux/kernel/netfilter.mk and see how it sets a config such as CONFIG_NETFILER_XT_U32 Apr 23 16:30:33 But I can't see where it actually changes .config, I can see include/kernel.mk simply includes the .config so we have access to which ones are set. But which Makefile or script actually changes the kernel CONFIG to include the configuration selected via the user? Apr 23 16:30:36 thanks in advance Apr 23 16:44:17 I think I found the problem!!! Apr 23 16:44:55 There was a version of python2.7 installed under ~/.local/lib Apr 23 16:46:21 The build dependencies for python/host looked in that directory for a copy of pip (no idea why) Apr 23 16:48:14 Since it found pip there, it did not install pip in staging_dir/hostpkg/bin Apr 23 16:48:52 I assume this is a bug in the dependencies for building python in OpenWrt Apr 23 16:49:00 Should I file a bug? Apr 23 17:20:09 figured it out, I remember working on this ages ago. incluer/kernel-default.mk calls kconfig.pl to do the work Apr 23 17:56:22 rmilecki: did you backport the security fixes in brcmsmac? Apr 23 18:28:44 Hi any one haveing probs building from latest master/trunk? Apr 23 18:30:10 I did distclean and redid my config but still no joy Apr 23 18:33:21 Tapper: please paste the build error Apr 23 18:34:24 Is there a way to get a build log to rite to a txt file? I cant coppy and paste from the window because of how my screenreader works Apr 23 18:35:29 Tapper: yes in menuconfig under "Advanced configuration options (for developers)" -> "Enable log files during build process" Apr 23 18:35:41 the log files will be writen to the logs folder Apr 23 18:35:46 there you can grep for error Apr 23 18:36:07 OK thanks I will try again. Were will I find the log file? Apr 23 18:36:16 O thanks Apr 23 18:47:04 Hauke bluddy thing seems to be building now lol I am going to turn on loging anyway. Thanks for the help. Apr 23 18:54:22 can somebody help me with openwrt o virtualbox Apr 23 19:08:14 Is anyone else working on spi-nand on ath79 on 4.19? I'm seeing that the mfg. ID doesn't need the byte shift that upstream Linux code performs. Apr 23 19:09:35 (Patched with 5.x for gigadevice.c and extending for the GD5F1GQ4FxxG chip) Apr 23 19:12:39 (Make that now sucessfully `Creating 3 MTD partitions on "spi0.1"`) Apr 23 19:49:25 Related question -- is there a way to enable USES_UBIFS for a NOR build or otherwise be able to build PACKAGE_ubi-utils to be able to create/debug/mount UBI vols on a NOR-based build? Apr 23 19:50:11 PACKAGE_ubi-utils depends on NAND_SUPPORT depends on Apr 23 19:50:32 ... seems to depend on being a NAND-based target Apr 23 21:30:30 (ping, anyone out there?) Apr 23 22:06:22 Hauke: I think I never looked at brcmsmac at all Apr 23 22:07:55 rmilecki: ah no this was in brcmfmac Apr 23 22:08:05 I think you fixed it in master in februar Apr 23 22:14:23 Hauke: great :) Apr 23 22:16:38 rmilecki: https://blog.quarkslab.com/reverse-engineering-broadcom-wireless-chipsets.html Apr 23 22:16:48 they at least link this: https://github.com/torvalds/linux/commit/1b5e2423164b3670e8bc9174e4762d297990deff#diff-66ea469ce534d8c3ba7147099b87fe78 Apr 23 22:16:53 and this https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a4176ec356c73a46c07c181c6d04039fafa34a9f Apr 23 23:24:17 GCC will not build now. Apr 23 23:24:19 https://pastebin.com/E8rk2DrP Apr 23 23:24:28 What have I broke? Apr 23 23:45:04 no idea Apr 23 23:45:09 run make distclean Apr 23 23:45:58 nbd around? or anytone else who feels like fixing the 4.19 patch for tcp window check? Apr 24 00:04:29 https://bugs.openwrt.org/index.php?do=details&task_id=2253 Apr 24 00:05:28 Thanks mangix that did it. **** ENDING LOGGING AT Wed Apr 24 02:59:57 2019