Re: [OpenWrt-Devel] Builds since yesterday afternoon not succeeding
Seems people are filing tickets about it now... https://dev.openwrt.org/ticket/7674 I had the same thing happen to me with uhttpd, (minus the lua stuff), where the build system didn't build openssl first. It seems that the build goes straight to 'install' targets, skipping the 'compile' targets. Also, when this was happening to me, `make dirclean' hasn't enough to fix it. I had to checkout from svn, which I think is very strange. The dirclean target isn't cleaning everything its supposed to, or we need another target that basically starts us at the beginning without having to go back to svn checkout... I think in the long run, having a correct build system is worth every penny. Why deal with this time-after-time. Additionally, having a correct build will make parallel builds better and with all these cores today, parallel builds are essential to not wasting an entire afternoon waiting for code to compile. Joe On Jul 26, 2010, at 9:38 PM, Jim Henderson wrote: On Tue, 27 Jul 2010 01:56:19 +0200, Benjamin Cama wrote: I'll give that a try. It's a little confusing, though, having builds that don't build, might it not be worth tracking down why and addressing that root cause, if only to prevent a repeat of the discussion? Yes, it's confusing. Maybe it should be in a FAQ. Finding the root cause may be interesting, but I think that to most people here, the benefits don't outweight the cost of tracking down these bugs. Fair enough - that trick did work for me, so I've got 22390 built. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Builds since yesterday afternoon not succeeding
Just read this thread today and want to mention, that if you run into build problems you should issue a make distclean (not dirclean) to get rid of all old stuff and extra packages (create patches of your manual changes first, so you can later re-apply them). Remember that trunk is ongoing development (equals alpha state) and that build problems and clean-ups are normal things there. Tip: Create a simple batch script to keep your downloads when doing a distclean like this... (ftp://ftp.maddes.net/maddes.net/openwrt/distclean_build.sh) mv dl dl_save make distclean mv dl_save dl My two cents Maddes On 27.07.2010 11:40, Joseph Roback wrote: Seems people are filing tickets about it now... https://dev.openwrt.org/ticket/7674 I had the same thing happen to me with uhttpd, (minus the lua stuff), where the build system didn't build openssl first. It seems that the build goes straight to 'install' targets, skipping the 'compile' targets. Also, when this was happening to me, `make dirclean' hasn't enough to fix it. I had to checkout from svn, which I think is very strange. The dirclean target isn't cleaning everything its supposed to, or we need another target that basically starts us at the beginning without having to go back to svn checkout... I think in the long run, having a correct build system is worth every penny. Why deal with this time-after-time. Additionally, having a correct build will make parallel builds better and with all these cores today, parallel builds are essential to not wasting an entire afternoon waiting for code to compile. Joe On Jul 26, 2010, at 9:38 PM, Jim Henderson wrote: On Tue, 27 Jul 2010 01:56:19 +0200, Benjamin Cama wrote: I'll give that a try. It's a little confusing, though, having builds that don't build, might it not be worth tracking down why and addressing that root cause, if only to prevent a repeat of the discussion? Yes, it's confusing. Maybe it should be in a FAQ. Finding the root cause may be interesting, but I think that to most people here, the benefits don't outweight the cost of tracking down these bugs. Fair enough - that trick did work for me, so I've got 22390 built. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Builds since yesterday afternoon not succeeding
On Tue, 27 Jul 2010 16:52:28 +0100, Matthias Buecher / Germany wrote: Just read this thread today and want to mention, that if you run into build problems you should issue a make distclean (not dirclean) to get rid of all old stuff and extra packages (create patches of your manual changes first, so you can later re-apply them). That's good to know - I didn't notice that distclean was an option, and have been just doing a make clean make world - so will change my workflow to do distclean instead. When I run into build issues, I normally wait at least one additional release before reporting an issue (and take some time to look through the svn logs to see what might've caused a problem - I usually try to pinpoint the cause of the problem so I can make a useful report). In this case, I'd had some troubles for about a day and nothing in the logs was making it clear to me why I was seeing a problem (indeed, the only updates seemed to be for a different platform than what I build for). Appreciate all the tips and everyone's help. I'm still fairly new to building this code - but I also like testing bleeding-edge code. :-) Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Builds since yesterday afternoon not succeeding
Hi, While I find the build process basically opaque, I think anything that can be done to make it better and ckearer is well worth it. For me some simple examples and some clearer explanation of the intent of the various makes would be a big help. i.e.- 1. rebuild all except toolset = ??? ( Saves LOTS of time ) 2. clear world and rebuild as if just downloaded to a new directory. 3. erase full directory tree, (try to) download all files and rebuild 4. save all downloaded files (somewhere) , erase full directory tree and rebuild FWIW - I usually do 4. manually but would rather do 1. if it really worked? Maybe it already does? warm regards, wiz On Tue, 27 Jul 2010, Jim Henderson wrote: On Tue, 27 Jul 2010 16:52:28 +0100, Matthias Buecher / Germany wrote: Just read this thread today and want to mention, that if you run into build problems you should issue a make distclean (not dirclean) to get rid of all old stuff and extra packages (create patches of your manual changes first, so you can later re-apply them). That's good to know - I didn't notice that distclean was an option, and have been just doing a make clean make world - so will change my workflow to do distclean instead. When I run into build issues, I normally wait at least one additional release before reporting an issue (and take some time to look through the svn logs to see what might've caused a problem - I usually try to pinpoint the cause of the problem so I can make a useful report). In this case, I'd had some troubles for about a day and nothing in the logs was making it clear to me why I was seeing a problem (indeed, the only updates seemed to be for a different platform than what I build for). Appreciate all the tips and everyone's help. I'm still fairly new to building this code - but I also like testing bleeding-edge code. :-) Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Builds since yesterday afternoon not succeeding
I've tried 22362,22380,22382,22388 from fresh SVN checkouts and all 4 of them worked. Before I even tried a `make dirclean' before rebuilding. I also tried manually deleting: `rm -rf bin build_dir staging_dir' ... I must have had something stale in my tree to cause this.. what I am not sure. Joe On Jul 25, 2010, at 11:26 PM, Jim Henderson wrote: On Sun, 25 Jul 2010 22:05:12 -0600, Joseph Roback wrote: I using r22388. After building miniupnpd manually and continuing the build, uhttpd failed because its dependency openssl was there. I manually build uhttpd make package/uhttpd-compile and then it was ok. I think the build system dependencies are screwed up somehow... It looks like that's the case. I'm trying building the releases between r22380 and r22388 to see if I can pinpoint where it stopped building. I don't know now why I went all the way back to r22344, I think I must've mistyped (meaning to go to 84), but I noticed the build date when going in to update the feeds. Something I do wish the feeds script would do (maybe it does?) is update to the same date/time as the main build. I end up manually going in and using svn update to update feeds/packages, feeds/xwrt, and feeds/luci (by date) to make sure I'm on the sources that would've been downloaded at the same time as the main openwrt code repository. It's not difficult to do, but if the feeds script could figure that out, that would be awesome for tracking things like this down. :-) I'll probably identify which is the last release to build tomorrow morning, it looks like r22380 is going to be successful, so I'll jump ahead to r22384 and try that next - that'll probably run while I'm sleeping. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Builds since yesterday afternoon not succeeding
Hi, Le lundi 26 juillet 2010 à 04:20 -0600, Joseph Roback a écrit : I've tried 22362,22380,22382,22388 from fresh SVN checkouts and all 4 of them worked. Before I even tried a `make dirclean' before rebuilding. I also tried manually deleting: `rm -rf bin build_dir staging_dir' ... I must have had something stale in my tree to cause this.. what I am not sure. This happens some times. I've also been catched by this some time ago, but learned to clean the offending package if I'm the only one seeing the problem. Regards, benjamin ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Builds since yesterday afternoon not succeeding
On Mon, 26 Jul 2010 17:41:25 +0200, Benjamin Cama wrote: Hi, Le lundi 26 juillet 2010 à 04:20 -0600, Joseph Roback a écrit : I've tried 22362,22380,22382,22388 from fresh SVN checkouts and all 4 of them worked. Before I even tried a `make dirclean' before rebuilding. I also tried manually deleting: `rm -rf bin build_dir staging_dir' ... I must have had something stale in my tree to cause this.. what I am not sure. This happens some times. I've also been catched by this some time ago, but learned to clean the offending package if I'm the only one seeing the problem. I've tracked it down to build 22385 - 22384 (which has the last commit at 22383) builds, 22385 doesn't for me. What process do you use to clean the offending package? Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Builds since yesterday afternoon not succeeding
On Mon, 26 Jul 2010 16:13:32 +, Jim Henderson wrote: I've tracked it down to build 22385 - 22384 (which has the last commit at 22383) builds, 22385 doesn't for me. Really strange, I backed down to 22383 and now it won't build that one either. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Builds since yesterday afternoon not succeeding
Le lundi 26 juillet 2010 à 16:13 +, Jim Henderson a écrit : I've tracked it down to build 22385 - 22384 (which has the last commit at 22383) builds, 22385 doesn't for me. But you said earlier that a later revision (22388) works; so, why bother ? Furthermore, these changesets don't seem to have anything to do with your problem. I think a clean checkout of r22385 would work; it's just that sometime, by doing a specific update/compile pattern, you end up with a non-working build. It's sad but can be fixed quickly by cleaning. What process do you use to clean the offending package? I just meant make package/foo/clean Regards, benjamin ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Builds since yesterday afternoon not succeeding
On Tue, 27 Jul 2010 00:37:13 +0200, Benjamin Cama wrote: Le lundi 26 juillet 2010 à 16:13 +, Jim Henderson a écrit : I've tracked it down to build 22385 - 22384 (which has the last commit at 22383) builds, 22385 doesn't for me. But you said earlier that a later revision (22388) works; so, why bother ? Furthermore, these changesets don't seem to have anything to do with your problem. I think a clean checkout of r22385 would work; it's just that sometime, by doing a specific update/compile pattern, you end up with a non-working build. It's sad but can be fixed quickly by cleaning. 22388 didn't build for me. Joseph said a fresh checkout built from him. What process do you use to clean the offending package? I just meant make package/foo/clean I'll give that a try. It's a little confusing, though, having builds that don't build, might it not be worth tracking down why and addressing that root cause, if only to prevent a repeat of the discussion? Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Builds since yesterday afternoon not succeeding
Le lundi 26 juillet 2010 à 23:11 +, Jim Henderson a écrit : 22388 didn't build for me. Joseph said a fresh checkout built from him. Sorry, I thought it was you. But you may give it a try. What process do you use to clean the offending package? I just meant make package/foo/clean I'll give that a try. It's a little confusing, though, having builds that don't build, might it not be worth tracking down why and addressing that root cause, if only to prevent a repeat of the discussion? Yes, it's confusing. Maybe it should be in a FAQ. Finding the root cause may be interesting, but I think that to most people here, the benefits don't outweight the cost of tracking down these bugs. Regards, benjamin ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Builds since yesterday afternoon not succeeding
On Tue, 27 Jul 2010 01:56:19 +0200, Benjamin Cama wrote: I'll give that a try. It's a little confusing, though, having builds that don't build, might it not be worth tracking down why and addressing that root cause, if only to prevent a repeat of the discussion? Yes, it's confusing. Maybe it should be in a FAQ. Finding the root cause may be interesting, but I think that to most people here, the benefits don't outweight the cost of tracking down these bugs. Fair enough - that trick did work for me, so I've got 22390 built. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Builds since yesterday afternoon not succeeding
When trying to build from the latest sources, I get the following output (with V=99) on 'make world': --- snip --- make[3]: Entering directory `/home/jhenderson/Downloads/openwrt/feeds/ packages/net/miniupnpd' ln -sf /home/jhenderson/Downloads/openwrt/build_dir/linux-ar71xx_generic/ miniupnpd-1.4/config.h.openwrt /home/jhenderson/Downloads/openwrt/ build_dir/linux-ar71xx_generic/miniupnpd-1.4/config.h make -C /home/jhenderson/Downloads/openwrt/build_dir/linux-ar71xx_generic/ miniupnpd-1.4 -f Makefile.openwrt AR=mips-openwrt-linux-uclibc-ar AS=mips-openwrt-linux-uclibc-gcc -c -Os -pipe -mips32r2 -mtune=mips32r2 - funit-at-a-time -fhonour-copts -msoft-float LD=mips-openwrt-linux-uclibc- ld NM=mips-openwrt-linux-uclibc-nm CC=mips-openwrt-linux-uclibc-gcc GCC=mips-openwrt-linux-uclibc-gcc CXX=mips-openwrt-linux-uclibc-g++ RANLIB=mips-openwrt-linux-uclibc-ranlib STRIP=mips-openwrt-linux-uclibc- strip OBJCOPY=mips-openwrt-linux-uclibc-objcopy OBJDUMP=mips-openwrt- linux-uclibc-objdump SIZE=mips-openwrt-linux-uclibc-size STAGING_DIR=/ home/jhenderson/Downloads/openwrt/staging_dir/target- mips_r2_uClibc-0.9.30.1 CFLAGS=-Os -pipe -mips32r2 -mtune=mips32r2 - funit-at-a-time -fhonour-copts -msoft-float -I/home/jhenderson/Downloads/ openwrt/staging_dir/target-mips_r2_uClibc-0.9.30.1/usr/include -I - DIPTABLES_143 LIBS=/home/jhenderson/Downloads/openwrt/staging_dir/ target-mips_r2_uClibc-0.9.30.1/usr/lib/libiptc.so /home/jhenderson/ Downloads/openwrt/staging_dir/target-mips_r2_uClibc-0.9.30.1/usr/lib/ libip4tc.so /home/jhenderson/Downloads/openwrt/staging_dir/target- mips_r2_uClibc-0.9.30.1/usr/lib/libip6tc.so make[4]: Entering directory `/home/jhenderson/Downloads/openwrt/build_dir/ linux-ar71xx_generic/miniupnpd-1.4' mips-openwrt-linux-uclibc-gcc -Os -pipe -mips32r2 -mtune=mips32r2 -funit- at-a-time -fhonour-copts -msoft-float -I/home/jhenderson/Downloads/ openwrt/staging_dir/target-mips_r2_uClibc-0.9.30.1/usr/include -I - DIPTABLES_143 -I/home/jhenderson/Downloads/openwrt/staging_dir/target- mips_r2_uClibc-0.9.30.1/usr/include -c -o netfilter/iptcrdr.o netfilter/ iptcrdr.c netfilter/iptcrdr.c:32:36: error: linux/netfilter/nf_nat.h: No such file or directory netfilter/iptcrdr.c: In function 'get_redirect_rule': netfilter/iptcrdr.c:161: error: 'iptc_handle_t' undeclared (first use in this function) netfilter/iptcrdr.c:161: error: (Each undeclared identifier is reported only once netfilter/iptcrdr.c:161: error: for each function it appears in.) netfilter/iptcrdr.c:161: error: expected ';' before 'h' netfilter/iptcrdr.c:167: error: 'h' undeclared (first use in this function) netfilter/iptcrdr.c:211: error: dereferencing pointer to incomplete type netfilter/iptcrdr.c:212: error: dereferencing pointer to incomplete type netfilter/iptcrdr.c: In function 'get_redirect_rule_by_index': netfilter/iptcrdr.c:245: error: 'iptc_handle_t' undeclared (first use in this function) netfilter/iptcrdr.c:245: error: expected ';' before 'h' netfilter/iptcrdr.c:251: error: 'h' undeclared (first use in this function) netfilter/iptcrdr.c:293: error: dereferencing pointer to incomplete type netfilter/iptcrdr.c:294: error: dereferencing pointer to incomplete type netfilter/iptcrdr.c: At top level: netfilter/iptcrdr.c:320: error: expected declaration specifiers or '...' before 'iptc_handle_t' netfilter/iptcrdr.c: In function 'delete_rule_and_commit': netfilter/iptcrdr.c:328: error: 'h' undeclared (first use in this function) netfilter/iptcrdr.c: In function 'delete_redirect_and_filter_rules': netfilter/iptcrdr.c:362: error: 'iptc_handle_t' undeclared (first use in this function) netfilter/iptcrdr.c:362: error: expected ';' before 'h' netfilter/iptcrdr.c:366: error: 'h' undeclared (first use in this function) netfilter/iptcrdr.c:426: error: too many arguments to function 'delete_rule_and_commit' netfilter/iptcrdr.c:430: error: too many arguments to function 'delete_rule_and_commit' netfilter/iptcrdr.c: In function 'get_dnat_target': netfilter/iptcrdr.c:487: error: invalid application of 'sizeof' to incomplete type 'struct ip_nat_multi_range' netfilter/iptcrdr.c:493: error: dereferencing pointer to incomplete type netfilter/iptcrdr.c:494: error: dereferencing pointer to incomplete type netfilter/iptcrdr.c:495: error: dereferencing pointer to incomplete type netfilter/iptcrdr.c:495: error: dereferencing pointer to incomplete type netfilter/iptcrdr.c:496: error: dereferencing pointer to incomplete type netfilter/iptcrdr.c:496: error: 'IP_NAT_RANGE_MAP_IPS' undeclared (first use in this function) netfilter/iptcrdr.c:497: error: dereferencing pointer to incomplete type netfilter/iptcrdr.c:497: error: dereferencing pointer to incomplete type netfilter/iptcrdr.c:498: error: dereferencing pointer to incomplete type netfilter/iptcrdr.c:498: error: 'IP_NAT_RANGE_PROTO_SPECIFIED' undeclared (first use in this function) netfilter/iptcrdr.c: In function 'iptc_init_verify_and_append': netfilter/iptcrdr.c:508: error: 'iptc_handle_t'
Re: [OpenWrt-Devel] Builds since yesterday afternoon not succeeding
On Sun, 25 Jul 2010 18:18:53 +, Jim Henderson wrote: When trying to build from the latest sources, I get the following output (with V=99) on 'make world': Seems to be working now. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Builds since yesterday afternoon not succeeding
I am experiencing the same errors. It happens to me even with `make -j1'. The miniupnpd package is being built before the iptables package, which miniupnpd depends on. It uses header files from the iptables package. The miniupnpd Makefile tries to set CFLAGS to CFLAGS=... -I$(firstword $(wildcard $(KERNEL_BUILD_DIR)/iptables-*/include)) -DIPTABLES_143 but the directory referenced, `$(KERNEL_BUILD_DIR)/iptables-*/include' doesn't exist until iptables is at least unpacked. There is a DEPENDS:=iptables in the miniupnpd Makefile. I've also tried putting a PKG_BUILD_DEPENDS:=iptables but no change. I honestly don't know what the difference between DEPENDS and PKG_BUILD_DEPENDS is, but neither seem to trigger iptables build before miniupnpd. Joe On Jul 25, 2010, at 8:49 PM, Jim Henderson wrote: On Sun, 25 Jul 2010 18:18:53 +, Jim Henderson wrote: When trying to build from the latest sources, I get the following output (with V=99) on 'make world': Seems to be working now. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Builds since yesterday afternoon not succeeding
Also interesting, if invoked to build miniupnpd manually, the iptables dependency seems to be honored. $ make package/feeds/packages/miniupnpd-compile Collecting package info: done make[1] package/feeds/packages/miniupnpd-compile make[2] -C package/libtool host-compile make[2] -C package/libtool compile make[2] -C package/iptables compile make[2] -C feeds/packages/net/miniupnpd compile The problem, repeatable every build, only seems to occur after `make clean make' of the entire trunk Joe On Jul 25, 2010, at 9:18 PM, Joseph Roback wrote: I am experiencing the same errors. It happens to me even with `make -j1'. The miniupnpd package is being built before the iptables package, which miniupnpd depends on. It uses header files from the iptables package. The miniupnpd Makefile tries to set CFLAGS to CFLAGS=... -I$(firstword $(wildcard $(KERNEL_BUILD_DIR)/iptables-*/include)) -DIPTABLES_143 but the directory referenced, `$(KERNEL_BUILD_DIR)/iptables-*/include' doesn't exist until iptables is at least unpacked. There is a DEPENDS:=iptables in the miniupnpd Makefile. I've also tried putting a PKG_BUILD_DEPENDS:=iptables but no change. I honestly don't know what the difference between DEPENDS and PKG_BUILD_DEPENDS is, but neither seem to trigger iptables build before miniupnpd. Joe On Jul 25, 2010, at 8:49 PM, Jim Henderson wrote: On Sun, 25 Jul 2010 18:18:53 +, Jim Henderson wrote: When trying to build from the latest sources, I get the following output (with V=99) on 'make world': Seems to be working now. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Builds since yesterday afternoon not succeeding
On Sun, 25 Jul 2010 21:44:52 -0600, Joseph Roback wrote: Also interesting, if invoked to build miniupnpd manually, the iptables dependency seems to be honored. $ make package/feeds/packages/miniupnpd-compile Collecting package info: done make[1] package/feeds/packages/miniupnpd-compile make[2] -C package/libtool host-compile make[2] -C package/libtool compile make[2] -C package/iptables compile make[2] -C feeds/packages/net/miniupnpd compile The problem, repeatable every build, only seems to occur after `make clean make' of the entire trunk I've noticed this in my testing - r22344 seems to build OK, r22348 doesn't. I'll see if I can narrow it down a bit more (I'm building r22344 now). Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Builds since yesterday afternoon not succeeding
I using r22388. After building miniupnpd manually and continuing the build, uhttpd failed because its dependency openssl was there. I manually build uhttpd make package/uhttpd-compile and then it was ok. I think the build system dependencies are screwed up somehow... Joe On Jul 25, 2010, at 10:01 PM, Jim Henderson wrote: On Sun, 25 Jul 2010 21:44:52 -0600, Joseph Roback wrote: Also interesting, if invoked to build miniupnpd manually, the iptables dependency seems to be honored. $ make package/feeds/packages/miniupnpd-compile Collecting package info: done make[1] package/feeds/packages/miniupnpd-compile make[2] -C package/libtool host-compile make[2] -C package/libtool compile make[2] -C package/iptables compile make[2] -C feeds/packages/net/miniupnpd compile The problem, repeatable every build, only seems to occur after `make clean make' of the entire trunk I've noticed this in my testing - r22344 seems to build OK, r22348 doesn't. I'll see if I can narrow it down a bit more (I'm building r22344 now). Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Builds since yesterday afternoon not succeeding
On Sun, 25 Jul 2010 22:05:12 -0600, Joseph Roback wrote: I using r22388. After building miniupnpd manually and continuing the build, uhttpd failed because its dependency openssl was there. I manually build uhttpd make package/uhttpd-compile and then it was ok. I think the build system dependencies are screwed up somehow... It looks like that's the case. I'm trying building the releases between r22380 and r22388 to see if I can pinpoint where it stopped building. I don't know now why I went all the way back to r22344, I think I must've mistyped (meaning to go to 84), but I noticed the build date when going in to update the feeds. Something I do wish the feeds script would do (maybe it does?) is update to the same date/time as the main build. I end up manually going in and using svn update to update feeds/packages, feeds/xwrt, and feeds/luci (by date) to make sure I'm on the sources that would've been downloaded at the same time as the main openwrt code repository. It's not difficult to do, but if the feeds script could figure that out, that would be awesome for tracking things like this down. :-) I'll probably identify which is the last release to build tomorrow morning, it looks like r22380 is going to be successful, so I'll jump ahead to r22384 and try that next - that'll probably run while I'm sleeping. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
