**** BEGIN LOGGING AT Wed Dec 12 02:59:58 2012
Dec 12 04:31:48 <Macer> hm
Dec 12 04:31:50 <Macer> i'm at a loss
Dec 12 04:31:56 <Macer> does any glibc source support armv5?
Dec 12 05:06:30 <ka6sox> ya, most do...
Dec 12 05:14:07 <Macer> the newer ones don't seem to
Dec 12 05:14:12 <Macer> so far i tried 2.17 and 2.15
Dec 12 05:14:26 <Macer> is there a specific version of src that i need in order to build it for armv5?
Dec 12 05:17:18 <ka6sox> are you building for Optware/Unslung or Slug OS?
Dec 12 07:09:05 <Macer> ka6sox: sorry. was a bit busy
Dec 12 07:09:21 <Macer> no.. i'm trying to build glibc on the synology itself
Dec 12 07:09:23 <ka6sox> Macer, no problem...I too am busy.
Dec 12 07:09:32 <ka6sox> ah, self hosting builds...got it
Dec 12 07:09:42 <Macer> and gcc as well
Dec 12 07:09:52 <ka6sox> building glibc and gcc on the target is always dicey
Dec 12 07:10:12 <ka6sox> most of them don't have enough RAM to do the linking step.
Dec 12 07:10:12 <Macer> you would think it would be easier ;) but i guess the idealogy is that x86 hardware is a lot faster to cross compile with
Dec 12 07:10:34 <Macer> but i have people that will be using the synology for small development with shells
Dec 12 07:10:41 <Macer> yeah.. the ds411j only has 128MB
Dec 12 07:10:53 <Macer> but i figure a typical swap might be able to handle the rest albeit slower
Dec 12 07:10:56 <ka6sox> yes, but gcc/glibc is too small unless you give it HUGE SWAP
Dec 12 07:11:15 <ka6sox> I've seen 2+GB links (which take a day or more on a 128MB machine)
Dec 12 07:11:35 <Macer> but i am running into a configure error where it says glibc doesn't support armv5
Dec 12 07:11:58 <Macer> and i don' tunderstand why :) i figured glibc had all the armv5 stuff
Dec 12 07:12:20 <Macer> maybe i should try with a slightly older gcc/glibc?
Dec 12 07:12:20 <ka6sox> does this build use autoconf?
Dec 12 07:12:36 <ka6sox> see what Optware has for glibc for the synology
Dec 12 07:12:44 <Macer> i did ;) 
Dec 12 07:12:49 <Macer> it doesn't
Dec 12 07:12:53 <ka6sox> hmmm
Dec 12 07:12:55 <ka6sox> okay
Dec 12 07:12:56 <Macer> it doesn't come with the kernel headers installed either
Dec 12 07:13:04 <ka6sox> ya, thats normal
Dec 12 07:13:05 <Macer> i ahd to get the synogpl stuff
Dec 12 07:13:13 <Macer> and copy it over and link it to /usr/include
Dec 12 07:13:40 <Macer> the error for glibc is straightforward though
Dec 12 07:13:55 <ka6sox> linking step for building gcc is a monster
Dec 12 07:14:00 <Macer> checking for assembler .type directive prefix... %checking sysdep dirs... configure: error: The armv5tel is not supported.
Dec 12 07:14:17 <Macer> the gcc part wasn't too bad... it got far up until stdio.h
Dec 12 07:14:29 <Macer> which i can only assume is built when you build glibc
Dec 12 07:14:37 <Macer> but i am stuck on glibc :)
Dec 12 07:14:49 <Macer> i can't get past the above
Dec 12 07:15:07 <Macer> when i got the toolchain for x86.. the arm cross compiler bins didn't seem to run
Dec 12 07:15:14 <Macer> but i didn't have much time to figure out why 
Dec 12 07:15:33 <Macer> maybe my kernel didn't support the bin type? can't really say because i had to leave
Dec 12 07:18:13 <Macer> In file included from ../.././libgcc/libgcc2.c:29:0:../.././libgcc/../gcc/tsystem.h:88:19: fatal error: stdio.h: No such file or directory
Dec 12 07:18:23 <Macer> that is where gcc building fails :-/
Dec 12 07:22:50 <ka6sox> bummers
Dec 12 07:23:25 <ka6sox> I really don't do native builds (as they are painful) and instead do cross stuff (either OpenEmbedded or the Optware style).
Dec 12 07:24:31 <Macer> oh
Dec 12 07:24:35 <Macer> well... 
Dec 12 07:24:46 <Macer> it appears that the .h files are in /opt/include
Dec 12 07:24:50 <Macer> how did i miss that? :)
Dec 12 07:25:24 <Macer> hm... i maybe i can just cp the /opt/include dir over to /usr/include since i just created the dir anyways
Dec 12 07:26:45 * Macer crosses fingers
Dec 12 07:26:45 <Macer> heh
Dec 12 07:26:55 <ka6sox> or just symlink the directory
Dec 12 07:27:43 <Macer> well.. i just copied it since i didn't want to symlink then move the kernel headers there as well
Dec 12 07:27:59 <Macer> that way i can just rm /usr/include if i have to without affecting /opt
Dec 12 07:28:04 <ka6sox> right
Dec 12 07:28:05 <ka6sox> okay
Dec 12 07:28:10 <Macer> oh wow.. that worked
Dec 12 07:28:11 <Macer> heh
Dec 12 07:28:13 <Macer> go figure 
Dec 12 07:28:21 <Macer> just wasted like 2 hours of my life figuring out glibc stuff 
Dec 12 07:28:38 <Macer> i didn't even think to search for stdio.h on the device
Dec 12 07:29:17 <ka6sox> life is like that...I am working on setting up an autobuilder cluster...its quite a slog
Dec 12 07:29:44 <Macer> well.. maybe after i build this i can figure out how to pkg it ;)
Dec 12 07:29:49 <Macer> would be nice to have a newer gcc
Dec 12 07:30:13 <Macer> i know someone was telling me that the one on the box was ancient (the optware repo is 4.2.3) or something like that
Dec 12 07:31:02 <Macer> but i guess that these embedded system developers think that cross compiling is a better option. i wonder if there is a way to set up distcc across different archs in order to speed things up :)
Dec 12 07:31:24 <Macer> ie: start building on the synology which caslls on distcc to build on an x86 if it is available 
Dec 12 07:31:57 <Macer> this methodology of using another system to build for arm devices seems a bit redundant 
Dec 12 07:32:12 <Macer> i used to build kernels on my 486SX/25 ;)
Dec 12 07:36:43 <ka6sox> icecreamsandwich is how cross distcc is done
Dec 12 07:36:51 <ka6sox> -sandwich
Dec 12 07:36:58 <ka6sox> icecream is the name of the package
Dec 12 07:37:24 <ka6sox> understands the cross-compliler issues for configuration.
Dec 12 07:42:32 <Macer> heh... well... it is building.. so i figure in about 3 weeks or so it should be done :)
Dec 12 07:42:49 <Macer> hopefully without error.. i honestly don't know how far along it is
Dec 12 07:42:52 <ka6sox> let me know if/when it gets done!
Dec 12 07:42:57 <Macer> what ever happened to qmake? 
Dec 12 07:43:04 <Macer> qmake had a % bar :)
Dec 12 07:43:13 <Macer> sure
Dec 12 07:43:17 <ka6sox> qmake is a nightmare...
Dec 12 07:43:27 <ka6sox> and one project I am working on uses it a lot
Dec 12 07:43:36 <Macer> ka6sox: yeah but someone could at least steal the % bar for gmake ;)
Dec 12 07:43:56 <ka6sox> true
Dec 12 07:44:25 <ka6sox> okay I must sleep...Jenkins is cooperating but still is taking a long time to configure for all these builds.
Dec 12 07:44:39 <Macer> heh. well.. thanks for the help. good night. 
Dec 12 07:44:50 <Macer> i'll let you knowif this actually works
Dec 12 07:44:58 <ka6sox> thanks!
Dec 12 07:44:59 <Macer> could be nice to simply rely on native building
Dec 12 07:45:05 <Macer> instead of all this 2nd system stuff :)
Dec 12 07:45:19 <ka6sox> be sure to give it LOTS of SWAP for the linking phase
Dec 12 07:46:55 <Macer> heh.. not really sure if i have a choice in this matter ;)
Dec 12 07:47:16 <Macer> when did linux start needing more than 8MB to do stuff ;) 640K should be enough!
Dec 12 07:47:38 <ka6sox-away> he he
Dec 12 07:47:50 <ka6sox-away> gone are the 486sx days
Dec 12 09:15:10 <Macer> grrrr
Dec 12 09:15:12 <Macer> ../../arm-none-linux-gnueabi/bin/ld: crti.o: No such file: No such file or dir  
Dec 12 09:15:17 <Macer> now what
Dec 12 11:06:29 <Macer> ok. i give up heh
Dec 12 11:06:36 <Macer> i almost broke my box moving libs around
Dec 12 15:56:05 <ka6sox-away> Macer, you need libgcc1 as well.
Dec 12 16:58:23 <Macer> zz_ka6sox-away: heh. uhm
Dec 12 17:00:46 <Macer> have it already installed :-/
Dec 12 17:00:55 <Macer> i give up on this. i can't get the cross compiling working either
Dec 12 17:07:21 <Macer> hm
Dec 12 17:07:32 <Macer> the cross compiler will not run on my kubuntu laptop :-/ wth is going on here?
Dec 12 17:07:45 <Macer> do i need some old linux distro to get things to work?
Dec 12 17:11:43 <Macer> blah. i think i've given this far too much time
Dec 12 17:12:00 <Macer> too bad... seemed like a good idea at the time but this methodology doesnt seem to agree with me
**** ENDING LOGGING AT Thu Dec 13 02:59:58 2012