**** BEGIN LOGGING AT Fri Nov 06 02:59:57 2009
Nov 06 04:01:56 <CIA-7> 03bzhou * r10856 10optware/trunk/make/sqlite.mk: sqlite: 3.6.19 -> 3.6.20
Nov 06 04:24:04 <CIA-7> 03bzhou * r10857 10optware/trunk/ (Makefile make/py-paramiko.mk): py-paramiko: ssh2 protocol for python. Added & promoted
Nov 06 09:47:13 <jomaster> hi eno, tell me when you are on and i can speak with you (hope i don't nerves you).
Nov 06 15:37:36 <eno> jomaster: i'm here
Nov 06 15:38:02 <jomaster> hi, most questions are gone :-D
Nov 06 15:38:39 <eno> so you got to the bottom of everything? congrats
Nov 06 15:39:07 <jomaster> i found my armeb-problem. a config-file use ".EXPORT_ALL_VARIABLES".
Nov 06 15:40:25 <eno> i c, have not used this option before
Nov 06 15:40:46 <eno> now I know to keep away from it
Nov 06 15:41:23 <jomaster> yes, really every variable will be exported. this makes many problems
Nov 06 15:42:26 <jomaster> i recognized that some applications don't save AR-value. is this normal?
Nov 06 15:43:17 <jomaster> so during build ar is used and not crosstool-ar
Nov 06 15:45:06 <eno> optware .mk file should set AR, it's possible some app does not take AR value from env or make variable
Nov 06 15:45:21 <eno> in that case, you better patch app Makefile
Nov 06 15:47:53 <jomaster> i see it at postgresql-build. i studied the buildlog to find my error. there AR is set to "". so when $(AR) is called "ar" is used.
Nov 06 15:50:47 <jomaster> used at "./src/port/Makefile" and set in "./src/Makefile.global" if you like to look at. i don't will work on this.
Nov 06 15:55:58 <jomaster> do you think that in libc-dev in line 143 "$(TARGET_USRLIBDIR)" should be "$(LIBC-DEV_USRLIBDIR)"?
Nov 06 16:06:15 <eno> jomaster: I'll look at it later
Nov 06 16:51:16 <savenger> Hi everyone... I have a question about SlugOS: I downloaded the tarball so that I have a working cross-development platform. I can easily compile some little programs. But I cannot link pcap to my program. It says: "error: pcap.h: No such file or directory" What can I do to use pcap?
Nov 06 16:53:02 <savenger> I already tried armeb-linux-gnueabi-g++ -I/usr/src/include myfile.c The pcap.h is inside the /usr/src/include, so I don't know why it isn't working.
Nov 06 16:58:56 <jomaster> perhaps you need to stage pcap before and then link to include- and lib-dir. you can try to create some optware-packages. this helps you compiling and staging.
Nov 06 17:21:48 <savenger> jomaster: Hi. How do I "stage" something?
Nov 06 17:24:28 <savenger> jomaster: btw. I made a mistake.... the pcap.h is inside /usr/include not /usr/src/include... compiling throw another error: CROSS COMPILE Badness: /usr/include in INCLUDEPATH: /usr/include
Nov 06 17:26:40 <eno> savenger: you should not place pcap.h in /usr/include
Nov 06 17:27:35 <eno> slugos toolchain built from OE errors out if you -I/usr/include
Nov 06 17:28:22 <eno> you can "stage" libpcap with "make install DESTDIR=$HOME/stage" for example
Nov 06 17:28:58 <eno> then -I$HOME/stage/usr/include -L$HOME/stage/usr/lib
Nov 06 17:29:06 <savenger> eno: inside which folder do I execute "make install..."
Nov 06 17:29:21 <eno> it's very dangerous installing to /usr
Nov 06 17:29:29 <eno> in libpcap
Nov 06 17:29:41 <savenger> eno: so I have to download the libpcap source?
Nov 06 17:29:44 <eno> (assuming libpcap supports make install DESTDIR="
Nov 06 17:30:04 <eno> yeah, where else do you expect to find libpcap?
Nov 06 17:30:36 <savenger> eno: perhaps there's a repository for slugos, where I can find it
Nov 06 17:31:07 <eno> overtime, if you want to build more than one app, you better use some cross compilation framework
Nov 06 17:31:37 <eno> OE has lots of .bb recipes
Nov 06 17:31:58 <eno> but I don't think they provide staged header or lib
Nov 06 17:32:22 <eno> native compilation is a different matter
Nov 06 17:32:44 <eno> you might be able to "opkg install libpcap-dev" (not sure about the package name)
Nov 06 17:33:23 <savenger> eon: yes, I already saw that, but I don't want to compile native :-)
Nov 06 17:33:36 <eno> what package are you trying to build?
Nov 06 17:33:52 <savenger> eon: no package, a self-written app
Nov 06 17:34:14 <eno> k
Nov 06 17:34:18 <savenger> eon: where on the nslu would be the stage-folder?
Nov 06 17:35:12 <eno> the location of the stage directory depends on framework
Nov 06 17:35:31 <eno> in your case, you pick an arbitrary directory on your cross build machine
Nov 06 17:35:49 <eno> it's mainly meant for cross compilation
Nov 06 17:36:14 <eno> on nslu2, if you use native build with -dev package, you don't need stage directory
Nov 06 17:37:40 <eno> since you're not using any framework, you're basically on your own
Nov 06 17:38:15 <savenger> eno: ok, I think the correct stage-folder will be my slugos-nslu2be.tmp/staging/armv5teb-linux/-folder, right?
Nov 06 17:38:28 <eno> you can look at CLFS (cross linux from scratch)
Nov 06 17:38:57 <savenger> eno: I think I have to stop for today... my wife's getting angry ;-)
Nov 06 17:39:06 <savenger> eno: But thank you very much for your help.
Nov 06 17:39:15 <eno> you're not using the framework, so the location of the staging directory does not matter that much
Nov 06 17:39:31 <eno> good luck, with your project and with your wife
Nov 06 17:39:48 <savenger> eno: ;-)
Nov 06 19:09:46 <jomaster> @eno: i think the order of PATH in libgd should be changed (line 116 and 147), because if there are tools in staging-dir/bin which are used during compiling, the build fails.
Nov 06 22:18:14 <CIA-7> 03bzhou * r10858 10optware/trunk/make/openssl.mk: openssl: 0.9.8k -> 0.9.8l
Nov 06 23:12:52 <CIA-7> 03bzhou * r10859 10optware/trunk/make/libgd.mk: libgd: libpng-config & libpng12-config PATH fix; updated template
**** ENDING LOGGING AT Sat Nov 07 02:59:57 2009