Re: [ptxdist] CAN utils

2008-11-11 Thread Gary Thomas
Juergen Beisert wrote: > Gary, > > On Dienstag, 11. November 2008, Gary Thomas wrote: >> Index: rules/canutils.in >> === >> --- rules/canutils.in (revision 9080) >> +++ rules/canutils.in (working copy) >> @@ -2,7 +2,6 @@ >> menuc

Re: [ptxdist] Local kernel trees (was Re: CAN utils)

2008-11-11 Thread Gary Thomas
Gary Thomas wrote: > Wolfram Sang wrote: >> Hello Gary, >> >>> Assume that I have a totally local kernel tree - how can I use >>> this? Also assume that I don't [necessarily] need/want ptxdist >>> to bother building my kernel. >>> >>> How can I configure things to work in this way? >> The current

Re: [ptxdist] Local kernel trees (was Re: CAN utils)

2008-11-11 Thread Wolfram Sang
On Tue, Nov 11, 2008 at 07:40:58AM -0700, Gary Thomas wrote: > Close, but I'm still fuzzy on a couple of details. > > * Why not just specify the whole kernel source path, rather than > the [obscure in my mind] prefix + version. I have kernel source > trees all over the place and having to rerun

Re: [ptxdist] CAN utils

2008-11-11 Thread Juergen Beisert
Gary, On Dienstag, 11. November 2008, Gary Thomas wrote: > Juergen Beisert wrote: > > On Dienstag, 11. November 2008, Gary Thomas wrote: > >> Index: rules/canutils.in > >> === > >> --- rules/canutils.in (revision 9080) > >> +++ rule

Re: [ptxdist] CAN utils

2008-11-11 Thread Gary Thomas
Juergen Beisert wrote: > Gary, > > On Dienstag, 11. November 2008, Gary Thomas wrote: >> Juergen Beisert wrote: >>> On Dienstag, 11. November 2008, Gary Thomas wrote: Index: rules/canutils.in === --- rules/canutils.in

[ptxdist] CAN utils

2008-11-11 Thread Gary Thomas
I'm trying to build the CAN utilities package and having trouble. Firstly, it seems to expect the [berlios.de] SocketCAN include tree, but nothing in the configuration points at that. Also, programs which are not selected by the configuration are still built, just not installed. Most particularl

Re: [ptxdist] CAN utils

2008-11-11 Thread Juergen Beisert
Gary, On Dienstag, 11. November 2008, Gary Thomas wrote: > Index: rules/canutils.in > === > --- rules/canutils.in (revision 9080) > +++ rules/canutils.in (working copy) > @@ -2,7 +2,6 @@ > menuconfig CANUTILS > tristate >

Re: [ptxdist] CAN utils

2008-11-11 Thread Marc Kleine-Budde
Gary Thomas wrote: > I'm trying to build the CAN utilities package and having trouble. > > Firstly, it seems to expect the [berlios.de] SocketCAN include > tree, but nothing in the configuration points at that. > > Also, programs which are not selected by the configuration are > still built, just

Re: [ptxdist] Local kernel trees (was Re: CAN utils)

2008-11-11 Thread Gary Thomas
Wolfram Sang wrote: > On Tue, Nov 11, 2008 at 07:40:58AM -0700, Gary Thomas wrote: > >> Close, but I'm still fuzzy on a couple of details. >> >> * Why not just specify the whole kernel source path, rather than >> the [obscure in my mind] prefix + version. I have kernel source >> trees all over th

Re: [ptxdist] Local kernel trees (was Re: CAN utils)

2008-11-11 Thread Gary Thomas
Wolfram Sang wrote: > Hello Gary, > >> Assume that I have a totally local kernel tree - how can I use >> this? Also assume that I don't [necessarily] need/want ptxdist >> to bother building my kernel. >> >> How can I configure things to work in this way? > > The current state of local kernel tre

Re: [ptxdist] CAN utils

2008-11-11 Thread Gary Thomas
Marc Kleine-Budde wrote: > Gary Thomas wrote: >> I'm trying to build the CAN utilities package and having trouble. >> >> Firstly, it seems to expect the [berlios.de] SocketCAN include >> tree, but nothing in the configuration points at that. >> >> Also, programs which are not selected by the config

[ptxdist] Local kernel trees (was Re: CAN utils)

2008-11-11 Thread Wolfram Sang
Hello Gary, > Assume that I have a totally local kernel tree - how can I use > this? Also assume that I don't [necessarily] need/want ptxdist > to bother building my kernel. > > How can I configure things to work in this way? The current state of local kernel trees looks like this: Assuming we