[00:22] <ESphynx> Yay :) it built!
[01:19] <UndiFineD> :)
[02:14] <ESphynx> Ok so my Oneiric build failed :|
[02:15] <ESphynx> most likely because of the messed up symlink :|
[02:15] <ESphynx> for ffi.h
[02:16] <ESphynx> when I build manually, I have to do a: sudo ln -s /usr/include/i686-linux-gnu/ffi.h /usr/include/ ; sudo ln -s /usr/include/i686-linux-gnu/ffitarget.h /usr/include/
[02:17] <ESphynx> or /usr/include/i386-linux-gnu/ I guess ?
[02:17] <ESphynx> How should I go about addressing that issue? (That's when cross-building for 32 bit on 64 bit oneiric)
[02:18] <ESphynx> I have lib32ffi-dev [amd64] in the debian/control file, but I'm guessing that the ffi package messed up and put under i686-linux-gnu instead of i386 ...
[02:18] <jtaylor> why do you need to cross build on oneiric?
[02:19] <ESphynx> well, on precise I just do the i386 build
[02:19] <ESphynx> and I guess 64 bit systems can still pull it
[02:19] <jtaylor> yes
[02:19] <ESphynx> but on oneiric, it worked until I added this libffi...
[02:19] <ESphynx> So since I could do it, I did it.
[02:19] <ESphynx> it's nice to know it can successfully be built on a 64 bit system.
[02:20] <ESphynx> as users on oneiric 64 bit might want to build it from source.
[02:20] <jtaylor> they can in a 32 bit chroot
[02:20] <ESphynx> they can also in a 64 bit system
[02:20] <ESphynx> not chroot.
[02:20] <ESphynx> chroot is overrated.
[02:20] <ESphynx> is there a way for me to add this missing include symlink?
[02:21] <ESphynx> setting up a chroot is an unnecessary burden for my users... and something that might carry them away from my software :P
[02:21] <jtaylor> why does it not compile on 64  bit?
[02:22] <ESphynx> jtaylor: no 64 bit support yet :)
[02:22] <ESphynx> Support is planned but will take a lot of dev time :P
[02:22] <ESphynx> all I need is to create that proper ffi.h symlink :P
[02:23] <ESphynx> heck, I could just add an -isystem to my makefiles.
[02:23] <ESphynx> to  /usr/include/i686-linux-gnu/
[02:23] <jtaylor> the symlink is there in oneiric
[02:24] <jtaylor> wrong include path is easily worked around with CPPFLAGS
[02:34] <ESphynx> jtaylor: the symlink from where to where have you got?
[02:34] <jtaylor> .so to .so.X
[02:34] <ESphynx> jtaylor: no i'm talking about the ffi.h
[02:34] <jtaylor> its in lib32
[02:35] <jtaylor> the headers are in i686
[02:35] <ESphynx> right... and that's not in the path
[02:35] <jtaylor> then add it
[02:35] <ESphynx> they should be in i386-linux-gnu, should they not?
[02:35] <jtaylor> yes and they are in precise
[02:35] <jtaylor> pre precise it is not multiarched
[02:36] <jtaylor> only the old biarch
[02:36] <ESphynx> they are in precise eh? It's strange cuz yesterday someone had that same problem on Mint 13... and before someone on Precise...
[02:36] <ESphynx> ok
[02:36] <jtaylor> (which is probably defined as i686)
[02:36] <ESphynx> so I'll just go ahead and tweak the makefiles
[02:36] <ESphynx> (my makefiles don't use CFLAGS from outside :P)
[02:36] <jtaylor> thats a bug
[02:37] <ESphynx> is it? ;)
[02:37] <ESphynx> I hate outside factors messing up a build :P
[02:37] <ESphynx> besides I can defend it on the fact of not being C ;)
[02:38] <jtaylor> CFLAGS is compiler flags
[02:38] <jtaylor> CPPFLAGS is preprocessor flags
[02:38] <ESphynx> ;)
[02:38] <ESphynx> i'm not familiar with CPPFLAGS tbh ;) first time I hear it
[02:38] <ESphynx> is that a standard configure thing? where does it come from?
[02:39] <jtaylor> its a autotools thing
[02:39] <ESphynx> k... well I'm not using autotools...
[02:39] <ESphynx> am I bound to accept CPPFLAGS? ;)
[02:39] <jtaylor> no
[02:39] <ESphynx> ah :)
[02:39] <ESphynx> hehe thanks for all the help jtaylor! appreciate it :)
[02:40] <ESphynx> i'll get dinner ready and then fix my preprocessor flags :P
[02:40] <ESphynx> is there still hope to make it into Quantal? :)
[02:40] <jtaylor> feature freeze is aug 23
[02:40] <ESphynx> ugg that is soon.
[02:40] <jtaylor> but you still need to find reviewers which is hard
[02:40] <jtaylor> so its tight
[02:40] <ESphynx> are you a reviewer? ;)
[02:41] <jtaylor> if I find the time
[02:41] <jtaylor> whats the package about?
[02:41] <ESphynx> It's the Ecere SDK... a cross platform SDK with GUI toolkit, network library, 2D/3D graphics engine, compiler for the eC language
[02:41] <ESphynx> we've been hoping to get into Ubuntu for quite a while...
[02:42] <ESphynx> (note GCC 4.7 fails on the build... trying to fix that tonight :P)
[02:43] <ESphynx> I would really appreciate help to get this in :)
[02:43] <ESphynx> whatever I can do!
[03:01] <micahg> well, there's always backports if you miss feature freeze
[04:32] <ESphynx> micahg: Do Backports till make it into the official release?
[04:33] <micahg> ESphynx: backports is enabled by default, so people can see it, it's not officially part of the release though (and can't be on any of the main images)
[04:34] <ESphynx> oh :( i'd really like to be part of the release though :(
[04:34] <ESphynx> we've been trying hard @ it since Karmic Koala :(
[04:34] <micahg> ESphynx: I don't think it makes a difference unless you're trying to get it on an image
[04:34] <ESphynx> yes I'd like to be on the CD :P
[04:34] <micahg> ESphynx: which CD?
[04:34] <ESphynx> hmm... the 1 CD ideally :P
[04:34] <ESphynx> or DVD :P
[04:35] <micahg> Ubuntu doesn't have that like Debian
[04:35] <ESphynx> where do dev apps go?
[04:35] <ESphynx> hmm, I have an Ubuntu CD here
[04:35] <ESphynx> 9.04 I think ?
[04:35] <micahg> no, I mean Ubuntu doesn't have the whole archive on media
[04:35] <ESphynx> right, but it's got some stuff, right? :)
[04:36] <micahg> to get something on an image, there has to be a request for it, the primary images (flavors included) are all tight on space except maybe Ubuntu Studio
[04:36] <ESphynx> I'll settle for Ubuntu Studio I guess ;)
[04:37] <ESphynx> but anyway, I'd really like to make it to feature freeze :P
[04:37] <ESphynx> but jtaylor ran away :P
[04:37] <ESphynx> micahg are you a potential reviewer as well? :)
[04:38] <micahg> ESphynx: yeah, but just FWIW, I don't see this being included on any media, it's fine for the archive though (in theory, I've done no review)
[04:39] <ESphynx> micahg: hey, I can dream ;)
[04:39] <ESphynx> I'll start with being on the archive ;)
[04:39] <ESphynx> Seriously, eC is an amazing programming language.
[04:40] <ESphynx> with less popularity than it deserves :P
[04:40] <ESphynx> And so is the Ecere GUI/toolkit ;)
[04:40] <micahg> I'm not sure any of the flavors ship an IDE at all
[04:40] <ESphynx> hmm, I'm sure they do?
[04:40] <ESphynx> KDevelop etc.
[04:40] <ESphynx> Python support?
[04:40] <ESphynx> I'm sure the distros come with Python support?
[04:40] <micahg> I don't think that's on any media though
[04:41] <ESphynx> in terms of space, the SDK is tiny...
[04:41] <ESphynx> we're talking < 10mb
[04:41] <micahg> we have many in the archive, just none on shipped media
[04:41] <ESphynx> K.... I sure would have thought some IDEs shipped with it!
[04:42] <ESphynx> Would you potentially have time to do a review? :)
[10:19] <smartboyhw> green7: You here?
[10:19] <green7> yup
[10:20] <smartboyhw> Did you ask them?
[10:20] <green7> I'm asking
[10:20] <green7> need some help in beginning development.
[10:49] <green7> can anyone help me in starting development?
[10:52] <micahg> this happens to be one of the few times during the week when very few people are around
[10:53] <green7> well, can you help me?
[10:54] <micahg> I'm very close to going to sleep, but what do you mean by development (Ubuntu, Ubuntu App, general)?
[10:54] <green7> Ubuntu
[10:54] <iulian> To start with, have a look at the links from the topic.
[10:54] <iulian> Specifically, the contributing one.
[10:55] <green7> Well, the Ubuntu wiki has so much links!
[10:55] <iulian> That's a good thing, isn't it?
[10:55] <green7> Nope! It's very confusing!
[10:56] <green7> When I'm close to reading half the page, it directs me to take a look a t some other page.
[10:57] <iulian> green7: Well, then read that page and come back.
[10:58] <green7> OK. I want to fix the bugs and probably write some patches. What should I read? The MOTU wiki?
[10:58] <iulian> There's way too much stuff going on to just have one single page. And thus, we've structured it as much as we could.
[10:58] <iulian> green7: Yes. That'd be a good place to start.
[10:58] <green7> All right.
[11:00] <iulian> If you have any questions, feel free to ask them here and we shall try to point you in the right direction.
[11:00] <green7> okay, thanks
[12:15] <green7> hello again
[12:15] <green7> got a question
[12:19] <green7> join #ubuntu-devel
[13:46] <green7> got a question
[13:47] <smartboyhw> green7: Clearly it is still me here
[13:47] <green7> so I've read the MOTU wiki
[13:47] <green7> and I'm ready for packaging
[13:47] <smartboyhw> OK
[13:47] <smartboyhw> OK
[13:48] <green7> The question is that there are many requests for packaging, and some of them already have their ppa, so what's the point of packaging?
[13:48] <smartboyhw> Don't ask me, ask the others
[13:48] <green7> I'm asking everyone
[13:48] <smartboyhw> They are not awake:)
[13:49] <smartboyhw> green7: Also it's Sunday
[13:49] <green7> yep
[13:51] <green7> do you know what's the difference between the packager and the maintainer?
[13:51] <smartboyhw> green7: I am only good at testing
[13:51] <green7> okay
[14:47] <green7> I cannot debuild a code
[15:29] <green7> I need some help in debuilding a package
[15:30] <smartboyhw> green7: This is Sunday!!!!
[15:31] <green7> not a single person works on sunday?
[15:32] <smartboyhw> NO!
[15:40] <ESphynx> I do :)
[15:40] <smartboyhw> Good!
[15:41] <ESphynx> I have to rewrite my code generator to work with GCC 4.7 though :P
[15:48] <codemaniac> smartboyhw: a lot of people work on Sundays for the community . :)
[15:48] <smartboyhw> Oh, do they
[15:48] <codemaniac> as weekdays are full of work on work .
[15:49] <green7> right