IRC log for #nslu2-linux on 20091006

01:12.11*** join/#nslu2-linux eno (n=eno@nslu2-linux/eno)
01:20.20CIA-1403bzhou * r10721 10optware/trunk/make/fetchmail.mk: fetchmail: 6.3.11 -> 6.3.12
01:23.03CIA-1403bzhou * r10722 10optware/trunk/make/mlocate.mk: mlocate: 0.22.1 -> 0.22.2
01:27.15*** join/#nslu2-linux caplink811-log (n=caplink8@dslb-094-222-104-252.pools.arcor-ip.net)
03:08.45CIA-1403bzhou * r10723 10optware/trunk/make/9base.mk: 9base: fixed fsg3 build
06:05.16*** join/#nslu2-linux jomaster (n=jomaster@f053085116.adsl.alicedsl.de)
07:26.27*** join/#nslu2-linux pleemans (n=toi@d51A49C45.access.telenet.be)
08:19.35*** join/#nslu2-linux oli_ (n=chatzill@g227209008.adsl.alicedsl.de)
08:20.48oli_Hi everybody
08:20.50oli_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
08:20.51oli_How can I bring the package to ipkg-server?
08:20.53oli_I already compiled an ipkg-package
08:20.55oli_Its called sane-backends-wl500
08:22.08rwhitbyoli_: 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.
08:22.33rwhitbyonce you do that, we can put in those modifications for the wl500g builds
08:23.49oli_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
08:24.09rwhitbythe AddAPackageToOptware wiki page
08:24.25oli_I'll have a look
08:24.27oli_thx
08:24.56rwhitbycheck out the optware repository, modify it to build the package correctly, then send a patch to the nslu2-linux mailing list
08:25.16oli_whats ment by "patch"
08:27.38rwhitbyoutput of the diff program with -u option
08:28.00oli_ok, I think I have to read rhe instructions
08:28.02oli_thx
08:31.29oli_Is this the write place to ask if I have further questions?
08:39.32*** join/#nslu2-linux osas (n=nnnosas@nslu2-linux/osas)
08:54.38*** join/#nslu2-linux kolla (i=kolla@158.38.62.30)
08:56.55*** join/#nslu2-linux oli_ (n=chatzill@g227209008.adsl.alicedsl.de)
09:14.26*** join/#nslu2-linux oli_ (n=chatzill@g227209008.adsl.alicedsl.de) [NETSPLIT VICTIM]
09:14.26*** join/#nslu2-linux pleemans (n=toi@d51A49C45.access.telenet.be) [NETSPLIT VICTIM]
09:14.26*** join/#nslu2-linux eno (n=eno@nslu2-linux/eno)
09:14.26*** join/#nslu2-linux kizoku (n=albus@cm-84.215.21.116.getinternet.no) [NETSPLIT VICTIM]
09:14.26*** join/#nslu2-linux joshin (n=joshin@unaffiliated/joshin) [NETSPLIT VICTIM]
09:14.26*** join/#nslu2-linux cdbot2 (n=cdbot2@hentges.net) [NETSPLIT VICTIM]
09:14.26*** join/#nslu2-linux CIA-14 (n=CIA@208.69.182.149) [NETSPLIT VICTIM]
09:14.26*** join/#nslu2-linux ByronT (n=byrontod@nslu2-linux/ByronT) [NETSPLIT VICTIM]
09:14.26*** join/#nslu2-linux rwhitby (n=rwhitby@nslu2-linux/rwhitby)
09:24.17*** join/#nslu2-linux mithro (n=tim@unaffiliated/mithro)
09:52.31oli_Hi,
09:52.32oli_I'm trying to install optware-packages an get the following error on my Kubuntu-mashine:
09:52.34oli_In Funktion »open«,
09:52.35oli_<PROTECTED>
09:52.37oli_/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
09:52.38oli_make[2]: *** [collect2.o] Fehler 1
09:52.40oli_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'
09:52.42oli_make[1]: *** [all-gcc] Fehler 2
09:52.43oli_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'
09:52.45oli_make: *** [/home/oli/slug/optware/toolchain/crosstool/.built] Fehler 2
09:52.46oli_any idea
10:20.39*** join/#nslu2-linux Reedy (n=Reedy@wikimedia/pdpc.active.reedy)
10:26.39CIA-1403reedy * r10724 10optware/trunk/make/sabnzbdplus.mk: sabnzbdplus: 0.4.11 -> 0.4.12
10:55.37oli_@<CIA-14: was this info for me? I do not understand anything
10:56.35oli_no, I don't think so ;-)
10:57.13Reedyoli_, its a bot
11:20.20*** join/#nslu2-linux RedT0mt0m (n=tomtom@bro67-2-82-227-110-8.fbx.proxad.net)
12:15.52*** join/#nslu2-linux Reedy (n=Reedy@wikimedia/pdpc.active.reedy)
13:20.30*** join/#nslu2-linux GPSFan (n=kenm@64.92.145.112)
13:44.30*** join/#nslu2-linux Reedy (n=Reedy@wikimedia/pdpc.active.reedy)
14:45.45*** join/#nslu2-linux oli_ (n=chatzill@f048115184.adsl.alicedsl.de)
14:46.56oli_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?
14:58.17enooli_: send your patch or files to nslu2-developers@yahoogroups.com, and request SVN access
14:59.08oli_ok
14:59.10oli_I need some help building the files, could you help me?
14:59.55oli_I am doing this for the first time
15:00.33enooli_: according to the log, you were building toolchain for unslung (optware nslu2 target)
15:00.54enoyou can skip that, and try build for your platform
15:01.15oli_I'm building for Oleg firmware, some kind of nslu
15:01.33enounder optware, do "make oleg-target; cd oleg; make directories toolchain ipkg-utils"
15:01.43enooleg is not nslu
15:01.58oli_thats what I did, and further
15:04.54enooli_: after toolchain built, try "make sane-backends-ipk" to build the existing optware ipk first
15:05.04enoand figure out the diff
15:05.45oli_I compiled a new version of sane-backends and I also have the ipkg-file.
15:05.59enowe're not interested in binary
15:06.17enowe need to be able to reproduce the build
15:06.40oli_sane-backends does not work on oleg, I do not know why, so I compiled from source, could be difficult to get the diffs
15:06.41enoand optware has some special settings, such as RPATH set to /opt/lib
15:07.21enowhy is it difficult to get the diffs?
15:07.54oli_because I dot know where to look for them
15:08.10enoif version is different, we can even try special case oleg platform to use a different version
15:08.29oli_what does that mean?
15:08.38enoyou can compare two trees using diff
15:09.16oli_I compile sane-backends-ipk and give it a try
15:09.22enoby looking at make/sane-backends.mk, you should know what version optware is using
15:09.47enowhen you compile from source, you must use a specific version
15:09.59enolist the versions here
15:10.04oli_Isnt it possible to give the package a different name like sane-backends-wl500
15:10.27enowe don't want to do this kind of thing unless it's absolutely necessary
15:10.46eno(think about the maintenance effort)
15:11.01enooptware covers more than a dozen platforms
15:11.34oli_yeah I know ;-)
15:11.35enothe whole point of optware is try to leverage the build recipes
15:11.40oli_And I understand you
15:12.05oli_optwrae package version is 1.0.20
15:12.15oli_I also compiled 1.0.20
15:12.56enoactually optware sane-backends is 1.0.20+git20090927
15:13.08enoper request, using git snapshot
15:13.51enoideally you merge your changes into optware/make/sane-backends.mk
15:14.18*** join/#nslu2-linux RedT0mt01 (n=tomtom@bro67-2-82-227-110-8.fbx.proxad.net)
15:14.58*** join/#nslu2-linux nslu2-log (n=nslu2-lo@limax.nslu2-linux.org)
15:15.07*** join/#nslu2-linux nathan7 (i=frozenfi@97.107.131.74) [NETSPLIT VICTIM]
15:15.17oli_I build the latest stable version from here
15:15.17oli_http://alioth.debian.org/frs/?group_id=30186
15:15.40oli_its 1.0.20 no git
15:21.53oli_eno, still there
15:28.06enooli_: are you sure 1.0.20+git20090927 does not work for oleg?
15:30.10enoyou might want to try comment out SANE_BACKENDS_GIT_COMMIT and SANE_BACKENDS_GIT_DATE lines in sane-backends.mk
15:30.26enoand build just 1.0.20
15:30.43oli_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.
15:30.44oli_I wrote a HowTo on wl500g.info to share the package and now some people are in the project and it works.
15:30.59oli_who build this package
15:31.23oli_do you know
15:31.59enooptware developers check in build recipes, and our autobuilder builds packages automatically
15:32.54oli_so that means, somebody checked in a new version on 20090927 or some days later, is that right?
15:33.12enoyes, that's me (bzhou == eno)
15:33.37oli_you build it?
15:33.54enoi committed the change per request of someone else
15:34.05enoread "svn log make/sane-backends.mk"
15:34.36oli_Its interesting for me, seems that somebody is working on the project but it does not work
15:34.46oli_on oleg
15:35.21enoit's possible that people only tested it on available platforms, just not on oleg
15:36.33oli_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)
15:37.16enooptware/oleg binaries are specifically for oleg
15:37.35enobut it's not runtime tested
15:37.38enofor oleg
15:37.58oli_where was it runtime tested? maybe never?
15:38.06enoit can build != it can run
15:38.13enonever
15:38.30enowe rely on helps from users
15:39.01oli_But for me to understand. There is somebody who builts the package and updates it without knowing if it runs?
15:39.04enofrom users who care about it
15:39.30enothat somebody may tested it on one or two platforms
15:39.38oli_because it always gets fresh updated
15:39.39enojust not oleg
15:40.44oli_ok, know I understand
15:41.19oli_But if I change the package and its working, what about the other person who always make a fresh update that is not working
15:44.16enowe can pin the version to 1.0.20 specifically for oleg
15:44.51enoOTOH, part of the responsibility is in upstream
15:45.31enoif 1.0.20 is working and 1.0.21 is not, upstream did something wrong to break it
15:47.19oli_Sorry but I do not understand this
15:47.23*** join/#nslu2-linux Reedy (n=Reedy@wikimedia/pdpc.active.reedy)
15:49.23oli_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
15:49.25oli_Some day, the other person compiles a new version, somebode changes the optware-package and we have a not working version again, or?
15:49.59enosomebody needs to figure out why it's broken with the new version
15:50.15enoit could be upstream change
15:50.25enoit could be something missing in build recipe
15:50.36oli_what does that mean "upstream change"
15:50.56enoupstream in this particular case means sane-backends developers
15:51.47enoi do runtime test for packages with my name on it as MAINTAINER
15:52.02enoand packages i care enough about
15:53.24oli_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.
15:53.25oli_ok
15:53.29oli_what is the best way in your opinion to get my working package on the server
15:55.58enofiguring out the difference in build recipe
15:56.21oli_ok
15:56.52enoand send patch of make/sane-backends.mk to nslu2 mailing list
15:57.17enoafter review, if it's good, we'll grant you svn write access
15:57.53enoyou are welcome to take over the MAINTAINER role of that package
15:58.16oli_after I figuredd out the diffs, I replace the wrong/new files, write
15:58.52oli_sorrry, right? ;-)
16:05.17oli_What I do not understand is, what is ment by "patch of makefile" the makefile itself?
16:29.18enooli_: svn diff make/sane-backends.mk
16:29.44enoassuming you've changed your sane-backends.mk to work
16:31.01oli_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
16:31.37enoyou must build the package within optware framework
16:32.11enoyou can change make/sane-backends.mk to customize certain things
16:32.21enoapply your patches, etc
16:32.48enothen send your changes to nslu2 mailing list
16:33.07oli_is there a HowTo on how to built in optware framework, or could you tell me
16:34.01enothe instruction is on http://www.nslu2-linux.org/wiki/Optware/AddAPackageToOptware
16:34.18enobut basically "make sane-backends-ipk"
16:35.16enothere're other make targets, such as s..-source s.. s..-dirclean
16:35.22enos..-check
16:35.43enoread make/sane-backends.mk to understand
16:36.04enoit's not very long
16:36.17oli_ok
16:36.19oli_I did make sane-backends-ipk and now I have the ipkg file and the CONTROL and opt folder
16:36.39oli_And with the same command, I can built the ipk-file back??
16:37.00enoyeah, that's using the latest build recipe from svn
16:37.25enowhat do you mean ipk-file back?
16:38.29enotry modify make/sane-backends.mk to change version to 1.0.20 proper by commenting out SANE_BACKENDS_GIT_ lines
16:38.44enocan you build 1.0.20 ipk?
16:38.53oli_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
16:39.08oli_I'm back in some minutes
16:39.27enothat depends on what file you've modified
16:40.03enousually you put them in some .patch under sources/sane-backends/
17:07.04oli_Here I am
17:08.23oli_Hi, again how to built the ipk package
17:09.43enoi thought you already passed that, and can build ipk
17:09.47*** join/#nslu2-linux pleemans (n=toi@d54C2A96D.access.telenet.be)
17:10.11oli_I built an ipk package on my router with an ipkg script
17:10.32oli_I think I must understand the whole optware-thing
17:10.53enooptware is mostly cross build
17:11.30enojust read make/sane-backends.mk
17:11.49*** join/#nslu2-linux jomaster (n=jomaster@f053085116.adsl.alicedsl.de)
17:12.10oli_ok
17:12.11oli_with the command make sane-backends-ipk you gave me for some hours, what did I do
17:12.11enoand you can see it automates/modulizes the build of dependencies
17:12.59enoit will build all the dependencies, stage libs into staging/opt/lib
17:13.10enoand retrieve tarball of sane-backends
17:13.14enounpack the tarball
17:13.25enoapply patches if specified
17:13.35enoissue the make command
17:13.57enoand finally builds sane-backends .ipk
17:14.27oli_ok so it crosscompiles the package downloaded from sane-project-home, yes?
17:14.33enoyes
17:14.43eno(I missed the configure step)
17:14.57oli_yeah I know
17:15.36oli_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?
17:16.12enoyou don't want to manually change files, you automate that with .patch file(s)
17:16.36oli_ok, and where do I have to put the files at
17:17.00enobefore you change file, make a backup to file.c.orig
17:17.20enothen after you make the change, diff -u path/file.c{.orig,}
17:17.30enoto generate a patch
17:17.34oli_yes, i understand
17:17.47enoyou put the patch in sources/sane-backends/
17:17.55oli_ok
17:18.15enoand specify/append it to SANE-BACKENDS_PATCHES in make/sane-backends.mk
17:18.55enoif there're existing patches, make sure the strip level of your patch is the same
17:19.10oli_strip-level?
17:19.43enothe number of directories to strip away from the patch
17:19.49enoman strip
17:19.55oli_ok
17:19.58enothe -p param
17:20.38enoexisting sane-backends patches are using -p1
17:22.26oli_and in the end i only have to upload the changed files?
17:22.29enosince you've already done native build, include/sane/config.h is good to have
17:22.48enoto compare against cross build config.h
17:23.27enoyeah, eventually you only have to upload modified sane-backends.mk and additional .patch files
17:23.45enowhich itself can be a patch
17:33.45oli_the version I crosscompiled with "make sa...ipk" is 1.0.19, why
17:35.47enodid you change any part of make/sane-backends.mk ?
17:35.59oli_no
17:36.13enois your optware svn up-to-date?
17:36.41oli_hopefully
17:36.53enodo a "svn up" just in case
17:37.02enowhere did you see 1.0.19?
17:39.03oli_"sources/sane-backends/1.0.19"
17:39.53enothat does not mean you're generating 1.0.19 ipk
17:40.00oli_ok
17:40.31enoit's there for historical reasons
17:40.45enofor a while 1.0.20 does not build for certain platforms
17:41.12enoso we pin 1.0.19 for these platforms
17:42.42enoto see the value of any .mk variable, use "make query-VARIABLE_NAME"
17:42.54oli_ok
17:42.55enoe.g. "make query-SANE_BACKENDS_RELEASE"
17:44.56oli_what about that:
17:44.58oli_ifeq (1.0.19, $(SANE_BACKENDS_RELEASE))
17:45.00oli_SANE_BACKENDS_PATCHES=$(SANE_BACKENDS_SOURCE_DIR)/1.0.19/Makefile.in.patch \
17:45.01oli_$(SANE_BACKENDS_SOURCE_DIR)/1.0.19/tools-Makefile.in.patch
17:45.03oli_else
17:45.04oli_SANE_BACKENDS_PATCHES=$(SANE_BACKENDS_SOURCE_DIR)/Makefile.in.patch \
17:45.06oli_$(SANE_BACKENDS_SOURCE_DIR)/tools-Makefile.in.patch
17:45.07oli_where do I have to insert the patchfile
17:45.09oli_at else
17:45.48enoin the else section
17:46.14enosince you're patching for non-1.0.19 version
17:48.17oli_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
17:49.20enowhen a new .mk file is committed, yes, autobuilder will rebuild ipk's that need to be rebuilt
17:50.18enoit invokes a script to clean old versions
17:50.46enoand invokes "make all", which indirectly invokes "make sane-backends-ipk"
17:51.55enoanything specific to sane-backends, is done in make/sane-backends.mk
17:51.56oli_ok, thanks for great support. Are you online tomorrow?
17:52.19oli_I finish here for today
17:52.30enoi'm not sure about tomorrow's schedule
17:52.42enogood luck
17:52.49enoyou can leave your question here
17:52.56oli_ok
17:52.57oli_nice evening
17:53.14oli_if its evening at your country ;-)
17:53.54enoit's actually late morning, good night to you
17:54.21oli_oh, ok bye
17:54.47jomastergood night from me too :-D
18:26.23jomasterhi eno. are the patches at optware also under gpl?
18:27.15jomasterperhabs i like to use some for the fsg firmware, but i don't know what about licence and copyright holder.
18:32.32enojomaster: good question, i'd ask rwhitby on this
18:33.05enoit may be complicated, since some of patches we get from gentoo, oe, or openwrt
18:34.20enoand some depends on the licence of the upstream package
18:36.09enoif upstream is gpl, then our patch has to be gpl as well
20:13.07*** join/#nslu2-linux Reedy (n=Reedy@wikimedia/pdpc.active.reedy)
20:38.53*** join/#nslu2-linux hillct (n=hillct@cpe-069-134-049-165.nc.res.rr.com)
20:59.12CIA-1403bzhou * r10725 10optware/trunk/make/aria2.mk: aria2: 1.6.0 -> 1.6.1
21:00.24CIA-1403bzhou * r10726 10optware/trunk/ (Makefile make/libmpdclient.mk): libmpdclient: library for interfacing MPD. Add & promoted
21:00.26CIA-1403bzhou * r10727 10optware/trunk/make/mpc.mk: mpc: 0.17 -> 0.18, depends on libmpdclient
21:12.24*** join/#nslu2-linux Reedy (n=Reedy@wikimedia/pdpc.active.reedy)
22:19.12*** join/#nslu2-linux kolla (i=kolla@firda.kolla.no)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.