This is the heart of the problem

Posted Feb 14, 2014 23:00 UTC (Fri) by madscientist (subscriber, #16861)
In reply to: This is the heart of the problem by hummassa
Parent article: The Debian technical committee vote concludes

I'm not sure what "that" you are referring to?

I build GCC et.al. by running configure and make, as per the README. I have a fancy makefile I wrote that does this. I create the sysroots as described in my previous posts: I get the RPMs and use rpm2cpio to unpack them into a directory, then when I compile and link my code I add the --sysroot=<dir> flag pointing to that directory. You might have to go through the sysroot and replace absolute symlinks with relative symlinks; I have a little Perl script that does this but it's easy enough to do by hand. You only need to do it once (or anyway, once every time you change your base operating system).

This is the heart of the problem

Posted Feb 15, 2014 13:22 UTC (Sat) by hummassa (subscriber, #307) [Link] (3 responses)

I think the "that" I referred to was "a complete build environment with my own GCC/binutils/make/flex/bison/m4/gdb, all the latest versions, and various different sysroots" etc.

IOW, do you already, and if not, would you/ could you PLEASE (pretty please with chantilly and a cherry on top) publish your specialized makefile and perl script that enables you to do all those things authomagically? :D

I can throw in the promise of a beer (or other appeasing beverage/ edible with one hour of my arguably agreeable companionship and conversation) whether and whenever we are geographically close...

This is the heart of the problem

Posted Feb 15, 2014 14:44 UTC (Sat) by madscientist (subscriber, #16861) [Link]

Since I did this as part of my work I'm not free to just publish it all without asking. But I'll check and see what can be done.

This is the heart of the problem

Posted Feb 15, 2014 19:03 UTC (Sat) by nix (subscriber, #2304) [Link]

You might want to look at the buildroot project.

This is the heart of the problem

Posted Feb 16, 2014 18:36 UTC (Sun) by liw (subscriber, #6379) [Link]

I have something vaguely similar as my personal CI system.
http://git.liw.fi/cgi-bin/cgit/cgit.cgi/jenkinstool/ if you want to
have look.

Beware: I wrote this for myself. It's not designed to be clean or
easy to setup, and I don't particularly want to support it, but you
can have a look.

Basically: a) a VM that runs Jenkins b) a VM for each environment (stable vs unstable, i386 vs amd64) where builds happen c) an apt repository (using reprepro) to hold packages built by CI d) successfully built packages get uploaded to the repo automatically e) builds use the repo in addition the Debian once and so groups of dependent packages can be built within the CI system.

Some day I may have time (or someone to pay me to hvae time) to make
that easier for others to do.