| 1 |
On Mon, 2004-07-26 at 14:53, Alex wrote: |
| 2 |
> I'm very proficient in C/C++. I'm also fairly skilled at doing shell |
| 3 |
> scripts and makefiles. I know a little perl and have a good handle on |
| 4 |
> regular expressions. |
| 5 |
> |
| 6 |
> I'm familiar with how to configure and compile applications from scratch. |
| 7 |
> |
| 8 |
> I joined this list because I was trying to use Gentoo to make chroot |
| 9 |
> jails. I was trying to do something like |
| 10 |
> |
| 11 |
> ROOT="/jail" emerge apache. |
| 12 |
|
| 13 |
I'm rather fond of building packages and then installing those packages |
| 14 |
into the $ROOT vs |
| 15 |
|
| 16 |
> |
| 17 |
> And get something that worked and was also fairly minimal. What really |
| 18 |
> annoys me about portage is that the configure/compile/install cmds are |
| 19 |
> tied directly to the version of the ebuild. If you make your own custom |
| 20 |
> builds, you have to make a new one for each incremental version of an app, |
| 21 |
> or else suffer the consequences. |
| 22 |
|
| 23 |
I'm not sure I understand your frustration here. |
| 24 |
|
| 25 |
|
| 26 |
> I also felt that perhaps there should be a distinction between |
| 27 |
> dependencies for building an app versus dependencies for using it. (e.g. |
| 28 |
> linux-headers are never needed at runtime!). |
| 29 |
|
| 30 |
If you have identified any ebuilds which think they need headers at |
| 31 |
runtime please compile a list and fire it off to qa@g.o |
| 32 |
|
| 33 |
Patches welcome as well of course. |
| 34 |
|
| 35 |
Another QA area that we are going to and currently do encounter are |
| 36 |
ebuilds which incorrectly assume at compile time that /usr/src/linux is |
| 37 |
the headers we should be using. This can mess a drivers all up if your |
| 38 |
cross compiling leading to deadlocks kernel freezes and so on. |
| 39 |
|
| 40 |
Here is a raw list of packages which may or may not be a problem for us. |
| 41 |
http://dev.gentoo.org/~solar/maybe-QA-problems.txt |
| 42 |
|
| 43 |
Feel free to narrow that down to a list of ebuilds for sure that are |
| 44 |
going to be a problem for us. |
| 45 |
|
| 46 |
> It sorta makes sense to not |
| 47 |
> distinguish these for a normal desktop, but not for cross-compiling on |
| 48 |
> embedded systems. |
| 49 |
> |
| 50 |
|
| 51 |
> I was considering developing some automated scripts in a |
| 52 |
> Linux-From-Scratch style. |
| 53 |
|
| 54 |
Not sure what your thinking of developing here but hopefully your |
| 55 |
thinking of using portage directly with these scripts. |
| 56 |
|
| 57 |
All of cross compiling needs to be revisited piece by piece. |
| 58 |
|
| 59 |
> Then, I realized that for cross-compiling, the |
| 60 |
> same problem applies and perhaps I could work with (or learn from) this |
| 61 |
> forum. |
| 62 |
> |
| 63 |
> -Alex |
| 64 |
> |
| 65 |
> |
| 66 |
> On Mon, 26 Jul 2004, Ned Ludd wrote: |
| 67 |
> |
| 68 |
> > help is always welcome in a community driven project. |
| 69 |
> > |
| 70 |
> > What do you do really good? |
| 71 |
> > What are your goals for portage? |
| 72 |
> > What build scenario's are you trying to accomplish? |
| 73 |
> > |
| 74 |
> >> |
| 75 |
> >> Thanks |
| 76 |
> >> |
| 77 |
> >> -Alex |
| 78 |
> >> |
| 79 |
> >> -- |
| 80 |
> >> gentoo-embedded@g.o mailing list |
| 81 |
> > -- |
| 82 |
> > Ned Ludd <solar@g.o> |
| 83 |
> > Gentoo (hardened,security,infrastructure,embedded,toolchain) Developer |
| 84 |
> > |
| 85 |
> |
| 86 |
> -- |
| 87 |
> gentoo-embedded@g.o mailing list |
| 88 |
-- |
| 89 |
Ned Ludd <solar@g.o> |
| 90 |
Gentoo (hardened,security,infrastructure,embedded,toolchain) Developer |
Archives