**** BEGIN LOGGING AT Tue Oct 06 02:59:58 2009 Oct 06 03:08:45 03bzhou * r10723 10optware/trunk/make/9base.mk: 9base: fixed fsg3 build Oct 06 08:20:48 Hi everybody Oct 06 08:20:50 I compiled a version of sane-backends on AsusWL500gP and its working. The ipkg-package from ipkg-server does not work for us (Asus-users). It is tested and we have a How-To on how to install end configure the server on wl500g.info Oct 06 08:20:51 How can I bring the package to ipkg-server? Oct 06 08:20:53 I already compiled an ipkg-package Oct 06 08:20:55 Its called sane-backends-wl500 Oct 06 08:22:08 oli_: you need to work out how to modify the makefiles in optware to rebuild that package. we don't accept binary packages, but require that they are rebuilt from source by the autobuilder. Oct 06 08:22:33 once you do that, we can put in those modifications for the wl500g builds Oct 06 08:23:49 I compiled the ipkg-package with an ipkg-script, so I now have an .ipkg-file.... Thats not enough? What do I have to do, where can I get the information Oct 06 08:24:09 the AddAPackageToOptware wiki page Oct 06 08:24:25 I'll have a look Oct 06 08:24:27 thx Oct 06 08:24:56 check out the optware repository, modify it to build the package correctly, then send a patch to the nslu2-linux mailing list Oct 06 08:25:16 whats ment by "patch" Oct 06 08:27:38 output of the diff program with -u option Oct 06 08:28:00 ok, I think I have to read rhe instructions Oct 06 08:28:02 thx Oct 06 08:31:29 Is this the write place to ask if I have further questions? Oct 06 09:52:31 Hi, Oct 06 09:52:32 I'm trying to install optware-packages an get the following error on my Kubuntu-mashine: Oct 06 09:52:34 In Funktion »open«, Oct 06 09:52:35 eingefügt von »collect_execute« bei /home/oli/slug/optware/toolchain/crosstool/build/armv5b-softfloat-linux/gcc-3.3.5-glibc-2.2.5/gcc-3.3.5/gcc/collect2.c:1575: Oct 06 09:52:37 /usr/include/bits/fcntl2.h:51: Fehler: Aufruf von »__open_missing_mode« mit Attributfehler deklariert: open with O_CREAT in second argument needs 3 arguments Oct 06 09:52:38 make[2]: *** [collect2.o] Fehler 1 Oct 06 09:52:40 make[2]: Verlasse Verzeichnis '/home/oli/slug/optware/toolchain/crosstool/build/armv5b-softfloat-linux/gcc-3.3.5-glibc-2.2.5/build-gcc-core/gcc' Oct 06 09:52:42 make[1]: *** [all-gcc] Fehler 2 Oct 06 09:52:43 make[1]: Verlasse Verzeichnis '/home/oli/slug/optware/toolchain/crosstool/build/armv5b-softfloat-linux/gcc-3.3.5-glibc-2.2.5/build-gcc-core' Oct 06 09:52:45 make: *** [/home/oli/slug/optware/toolchain/crosstool/.built] Fehler 2 Oct 06 09:52:46 any idea Oct 06 10:26:39 03reedy * r10724 10optware/trunk/make/sabnzbdplus.mk: sabnzbdplus: 0.4.11 -> 0.4.12 Oct 06 10:55:37 @ no, I don't think so ;-) Oct 06 10:57:13 oli_, its a bot Oct 06 14:46:56 Hi, I would like to get write access for SVN write. I am developing sane-backends for AsusWl500 with oleg Firmware. Can anybody please help me? Oct 06 14:58:17 oli_: send your patch or files to nslu2-developers@yahoogroups.com, and request SVN access Oct 06 14:59:08 ok Oct 06 14:59:10 I need some help building the files, could you help me? Oct 06 14:59:55 I am doing this for the first time Oct 06 15:00:33 oli_: according to the log, you were building toolchain for unslung (optware nslu2 target) Oct 06 15:00:54 you can skip that, and try build for your platform Oct 06 15:01:15 I'm building for Oleg firmware, some kind of nslu Oct 06 15:01:33 under optware, do "make oleg-target; cd oleg; make directories toolchain ipkg-utils" Oct 06 15:01:43 oleg is not nslu Oct 06 15:01:57 thats what I did, and further Oct 06 15:04:54 oli_: after toolchain built, try "make sane-backends-ipk" to build the existing optware ipk first Oct 06 15:05:04 and figure out the diff Oct 06 15:05:45 I compiled a new version of sane-backends and I also have the ipkg-file. Oct 06 15:05:59 we're not interested in binary Oct 06 15:06:16 we need to be able to reproduce the build Oct 06 15:06:40 sane-backends does not work on oleg, I do not know why, so I compiled from source, could be difficult to get the diffs Oct 06 15:06:41 and optware has some special settings, such as RPATH set to /opt/lib Oct 06 15:07:21 why is it difficult to get the diffs? Oct 06 15:07:54 because I dot know where to look for them Oct 06 15:08:10 if version is different, we can even try special case oleg platform to use a different version Oct 06 15:08:29 what does that mean? Oct 06 15:08:38 you can compare two trees using diff Oct 06 15:09:16 I compile sane-backends-ipk and give it a try Oct 06 15:09:22 by looking at make/sane-backends.mk, you should know what version optware is using Oct 06 15:09:47 when you compile from source, you must use a specific version Oct 06 15:09:59 list the versions here Oct 06 15:10:04 Isnt it possible to give the package a different name like sane-backends-wl500 Oct 06 15:10:27 we don't want to do this kind of thing unless it's absolutely necessary Oct 06 15:10:46 (think about the maintenance effort) Oct 06 15:11:01 optware covers more than a dozen platforms Oct 06 15:11:34 yeah I know ;-) Oct 06 15:11:35 the whole point of optware is try to leverage the build recipes Oct 06 15:11:40 And I understand you Oct 06 15:12:05 optwrae package version is 1.0.20 Oct 06 15:12:15 I also compiled 1.0.20 Oct 06 15:12:56 actually optware sane-backends is 1.0.20+git20090927 Oct 06 15:13:08 per request, using git snapshot Oct 06 15:13:50 ideally you merge your changes into optware/make/sane-backends.mk **** BEGIN LOGGING AT Tue Oct 06 15:14:15 2009 Oct 06 15:14:55 I build the latest stable version from here Oct 06 15:14:57 http://alioth.debian.org/frs/?group_id=30186 Oct 06 15:15:40 its 1.0.20 no git Oct 06 15:21:53 eno, still there Oct 06 15:28:06 oli_: are you sure 1.0.20+git20090927 does not work for oleg? Oct 06 15:30:11 you might want to try comment out SANE_BACKENDS_GIT_COMMIT and SANE_BACKENDS_GIT_DATE lines in sane-backends.mk Oct 06 15:30:26 and build just 1.0.20 Oct 06 15:30:43 sure, i installed it again and again. I'm from wl500g.info and some years ago, there was a thread for sane-backends, so I think it could have worked for some time. Oct 06 15:30:45 I wrote a HowTo on wl500g.info to share the package and now some people are in the project and it works. Oct 06 15:30:59 who build this package Oct 06 15:31:24 do you know Oct 06 15:31:59 optware developers check in build recipes, and our autobuilder builds packages automatically Oct 06 15:32:54 so that means, somebody checked in a new version on 20090927 or some days later, is that right? Oct 06 15:33:12 yes, that's me (bzhou == eno) Oct 06 15:33:37 you build it? Oct 06 15:33:55 i committed the change per request of someone else Oct 06 15:34:06 read "svn log make/sane-backends.mk" Oct 06 15:34:36 Its interesting for me, seems that somebody is working on the project but it does not work Oct 06 15:34:46 on oleg Oct 06 15:35:21 it's possible that people only tested it on available platforms, just not on oleg Oct 06 15:36:33 I do not understand, is it not built specially for oleg (sorry I have to ask some stupid stuff because I am not that involved in optware yet) Oct 06 15:37:17 optware/oleg binaries are specifically for oleg Oct 06 15:37:35 but it's not runtime tested Oct 06 15:37:38 for oleg Oct 06 15:37:59 where was it runtime tested? maybe never? Oct 06 15:38:07 it can build != it can run Oct 06 15:38:13 never Oct 06 15:38:30 we rely on helps from users Oct 06 15:39:01 But for me to understand. There is somebody who builts the package and updates it without knowing if it runs? Oct 06 15:39:04 from users who care about it Oct 06 15:39:30 that somebody may tested it on one or two platforms Oct 06 15:39:38 because it always gets fresh updated Oct 06 15:39:39 just not oleg Oct 06 15:40:44 ok, know I understand Oct 06 15:41:19 But if I change the package and its working, what about the other person who always make a fresh update that is not working Oct 06 15:44:17 we can pin the version to 1.0.20 specifically for oleg Oct 06 15:44:51 OTOH, part of the responsibility is in upstream Oct 06 15:45:31 if 1.0.20 is working and 1.0.21 is not, upstream did something wrong to break it Oct 06 15:47:20 Sorry but I do not understand this Oct 06 15:49:23 If I change the package and e.g. you make it available then we have a working version for some time on the optware-server Oct 06 15:49:25 Some day, the other person compiles a new version, somebode changes the optware-package and we have a not working version again, or? Oct 06 15:49:59 somebody needs to figure out why it's broken with the new version Oct 06 15:50:15 it could be upstream change Oct 06 15:50:25 it could be something missing in build recipe Oct 06 15:50:36 what does that mean "upstream change" Oct 06 15:50:56 upstream in this particular case means sane-backends developers Oct 06 15:51:47 i do runtime test for packages with my name on it as MAINTAINER Oct 06 15:52:02 and packages i care enough about Oct 06 15:53:24 I know I do some stupid asking, but I'd like to do some work for Asus-Wl500 and so I have to get involved a little bit. I have some more packages for oleg. Oct 06 15:53:25 ok Oct 06 15:53:30 what is the best way in your opinion to get my working package on the server Oct 06 15:55:58 figuring out the difference in build recipe Oct 06 15:56:22 ok Oct 06 15:56:53 and send patch of make/sane-backends.mk to nslu2 mailing list Oct 06 15:57:17 after review, if it's good, we'll grant you svn write access Oct 06 15:57:53 you are welcome to take over the MAINTAINER role of that package Oct 06 15:58:16 after I figuredd out the diffs, I replace the wrong/new files, write Oct 06 15:58:52 sorrry, right? ;-) Oct 06 16:05:17 What I do not understand is, what is ment by "patch of makefile" the makefile itself? Oct 06 16:29:19 oli_: svn diff make/sane-backends.mk Oct 06 16:29:44 assuming you've changed your sane-backends.mk to work Oct 06 16:31:08 When I replaced the files, what do I have to do next. How do I built the package, or what kind of package do I have to give to you Oct 06 16:32:35 you must build the package within optware framework Oct 06 16:32:36 you can change make/sane-backends.mk to customize certain things Oct 06 16:33:00 apply your patches, etc Oct 06 16:33:00 then send your changes to nslu2 mailing list Oct 06 16:33:08 is there a HowTo on how to built in optware framework, or could you tell me Oct 06 16:34:01 the instruction is on http://www.nslu2-linux.org/wiki/Optware/AddAPackageToOptware Oct 06 16:34:38 but basically "make sane-backends-ipk" Oct 06 16:35:16 there're other make targets, such as s..-source s.. s..-dirclean Oct 06 16:35:23 s..-check Oct 06 16:35:43 read make/sane-backends.mk to understand Oct 06 16:36:28 it's not very long Oct 06 16:36:28 ok Oct 06 16:36:28 I did make sane-backends-ipk and now I have the ipkg file and the CONTROL and opt folder Oct 06 16:36:39 And with the same command, I can built the ipk-file back?? Oct 06 16:37:00 yeah, that's using the latest build recipe from svn Oct 06 16:37:26 what do you mean ipk-file back? Oct 06 16:38:30 try modify make/sane-backends.mk to change version to 1.0.20 proper by commenting out SANE_BACKENDS_GIT_ lines Oct 06 16:38:44 can you build 1.0.20 ipk? Oct 06 16:38:54 you gave me that command, to built the package on my system. Therefor the package was downloaded from server. But now, if I wanna built my modified files, how do I do that Oct 06 16:39:08 I'm back in some minutes Oct 06 16:39:27 that depends on what file you've modified Oct 06 16:40:04 usually you put them in some .patch under sources/sane-backends/ Oct 06 17:07:04 Here I am Oct 06 17:08:23 Hi, again how to built the ipk package Oct 06 17:09:44 i thought you already passed that, and can build ipk Oct 06 17:10:11 I built an ipk package on my router with an ipkg script Oct 06 17:10:32 I think I must understand the whole optware-thing Oct 06 17:10:54 optware is mostly cross build Oct 06 17:11:30 just read make/sane-backends.mk Oct 06 17:12:10 ok Oct 06 17:12:11 with the command make sane-backends-ipk you gave me for some hours, what did I do Oct 06 17:12:11 and you can see it automates/modulizes the build of dependencies Oct 06 17:12:59 it will build all the dependencies, stage libs into staging/opt/lib Oct 06 17:13:10 and retrieve tarball of sane-backends Oct 06 17:13:17 unpack the tarball Oct 06 17:13:26 apply patches if specified Oct 06 17:13:35 issue the make command Oct 06 17:13:58 and finally builds sane-backends .ipk Oct 06 17:14:28 ok so it crosscompiles the package downloaded from sane-project-home, yes? Oct 06 17:14:33 yes Oct 06 17:14:43 (I missed the configure step) Oct 06 17:14:57 yeah I know Oct 06 17:15:36 but after I changed the files, I do not want it to cross compile the downloaded files, but the files on my mashine, or not? Oct 06 17:16:12 you don't want to manually change files, you automate that with .patch file(s) Oct 06 17:16:37 ok, and where do I have to put the files at Oct 06 17:17:00 before you change file, make a backup to file.c.orig Oct 06 17:17:21 then after you make the change, diff -u path/file.c{.orig,} Oct 06 17:17:30 to generate a patch Oct 06 17:17:34 yes, i understand Oct 06 17:17:47 you put the patch in sources/sane-backends/ Oct 06 17:17:55 ok Oct 06 17:18:15 and specify/append it to SANE-BACKENDS_PATCHES in make/sane-backends.mk Oct 06 17:18:55 if there're existing patches, make sure the strip level of your patch is the same Oct 06 17:19:10 strip-level? Oct 06 17:19:43 the number of directories to strip away from the patch Oct 06 17:19:49 man strip Oct 06 17:19:56 ok Oct 06 17:19:59 the -p param Oct 06 17:20:39 existing sane-backends patches are using -p1 Oct 06 17:22:26 and in the end i only have to upload the changed files? Oct 06 17:22:30 since you've already done native build, include/sane/config.h is good to have Oct 06 17:22:48 to compare against cross build config.h Oct 06 17:23:27 yeah, eventually you only have to upload modified sane-backends.mk and additional .patch files Oct 06 17:23:46 which itself can be a patch Oct 06 17:33:45 the version I crosscompiled with "make sa...ipk" is 1.0.19, why Oct 06 17:35:48 did you change any part of make/sane-backends.mk ? Oct 06 17:35:59 no Oct 06 17:36:13 is your optware svn up-to-date? Oct 06 17:37:22 hopefully Oct 06 17:37:22 do a "svn up" just in case Oct 06 17:37:22 where did you see 1.0.19? Oct 06 17:39:03 "sources/sane-backends/1.0.19" Oct 06 17:39:53 that does not mean you're generating 1.0.19 ipk Oct 06 17:40:00 ok Oct 06 17:40:31 it's there for historical reasons Oct 06 17:40:45 for a while 1.0.20 does not build for certain platforms Oct 06 17:41:12 so we pin 1.0.19 for these platforms Oct 06 17:42:42 to see the value of any .mk variable, use "make query-VARIABLE_NAME" Oct 06 17:42:55 ok Oct 06 17:42:55 e.g. "make query-SANE_BACKENDS_RELEASE" Oct 06 17:44:57 what about that: Oct 06 17:44:59 ifeq (1.0.19, $(SANE_BACKENDS_RELEASE)) Oct 06 17:45:00 SANE_BACKENDS_PATCHES=$(SANE_BACKENDS_SOURCE_DIR)/1.0.19/Makefile.in.patch \ Oct 06 17:45:01 $(SANE_BACKENDS_SOURCE_DIR)/1.0.19/tools-Makefile.in.patch Oct 06 17:45:03 else Oct 06 17:45:05 SANE_BACKENDS_PATCHES=$(SANE_BACKENDS_SOURCE_DIR)/Makefile.in.patch \ Oct 06 17:45:06 $(SANE_BACKENDS_SOURCE_DIR)/tools-Makefile.in.patch Oct 06 17:45:08 where do I have to insert the patchfile Oct 06 17:45:09 at else Oct 06 17:45:48 in the else section Oct 06 17:46:14 since you're patching for non-1.0.19 version Oct 06 17:48:17 when I send the makefile, does the autobuilder build the whole package new? What means does he download the source.tar, compile it, make it make install it, make the ipk-file and after that apply the pathces... Just to understand how this is working Oct 06 17:49:20 when a new .mk file is committed, yes, autobuilder will rebuild ipk's that need to be rebuilt Oct 06 17:50:18 it invokes a script to clean old versions Oct 06 17:50:46 and invokes "make all", which indirectly invokes "make sane-backends-ipk" Oct 06 17:51:55 anything specific to sane-backends, is done in make/sane-backends.mk Oct 06 17:51:56 ok, thanks for great support. Are you online tomorrow? Oct 06 17:52:19 I finish here for today Oct 06 17:52:30 i'm not sure about tomorrow's schedule Oct 06 17:52:42 good luck Oct 06 17:52:49 you can leave your question here Oct 06 17:52:56 ok Oct 06 17:52:57 nice evening Oct 06 17:53:14 if its evening at your country ;-) Oct 06 17:53:55 it's actually late morning, good night to you Oct 06 17:54:21 oh, ok bye Oct 06 17:54:47 good night from me too :-D Oct 06 18:26:22 hi eno. are the patches at optware also under gpl? Oct 06 18:27:15 perhabs i like to use some for the fsg firmware, but i don't know what about licence and copyright holder. Oct 06 18:32:32 jomaster: good question, i'd ask rwhitby on this Oct 06 18:33:05 it may be complicated, since some of patches we get from gentoo, oe, or openwrt Oct 06 18:34:20 and some depends on the licence of the upstream package Oct 06 18:36:09 if upstream is gpl, then our patch has to be gpl as well Oct 06 20:59:12 03bzhou * r10725 10optware/trunk/make/aria2.mk: aria2: 1.6.0 -> 1.6.1 Oct 06 21:00:24 03bzhou * r10726 10optware/trunk/ (Makefile make/libmpdclient.mk): libmpdclient: library for interfacing MPD. Add & promoted Oct 06 21:00:26 03bzhou * r10727 10optware/trunk/make/mpc.mk: mpc: 0.17 -> 0.18, depends on libmpdclient Oct 07 00:47:56 03bzhou * r10728 10optware/trunk/make/mcabber.mk: mcabber: 0.9.9 -> 0.9.10 **** ENDING LOGGING AT Wed Oct 07 02:59:57 2009