On Thu, Sep 17, 2009 at 07:58:17AM -0400, Philip Balister wrote:
> Philip Balister wrote:
>
> OK, I found the root problem. Basically, in the usrp2 firmware build
> process, there is a wrapper configure.gnu that unsets environment vars
> and removes extra arguments to the configure used to buil
Philip Balister wrote:
Eric Blossom wrote:
On Tue, Sep 15, 2009 at 04:57:32PM -0400, Philip Balister wrote:
I'm trying to disable the configure stuff for the USRP2 by passing
--disable-usrp2 to the configure script. Unfortunately, the
usrp2/firmware script is still trying to run. This dies w
Eric Blossom wrote:
On Tue, Sep 15, 2009 at 04:57:32PM -0400, Philip Balister wrote:
I'm trying to disable the configure stuff for the USRP2 by passing
--disable-usrp2 to the configure script. Unfortunately, the
usrp2/firmware script is still trying to run. This dies when I am trying
to cro
On Tue, Sep 15, 2009 at 04:57:32PM -0400, Philip Balister wrote:
> I'm trying to disable the configure stuff for the USRP2 by passing
> --disable-usrp2 to the configure script. Unfortunately, the
> usrp2/firmware script is still trying to run. This dies when I am trying
> to cross compile the
On Tue, Sep 15, 2009 at 13:57, Philip Balister wrote:
> I'm trying to disable the configure stuff for the USRP2 by passing
> --disable-usrp2 to the configure script. Unfortunately, the usrp2/firmware
> script is still trying to run. This dies when I am trying to cross compile
> the code. For the
I'm trying to disable the configure stuff for the USRP2 by passing
--disable-usrp2 to the configure script. Unfortunately, the
usrp2/firmware script is still trying to run. This dies when I am trying
to cross compile the code. For the OMAP3, I have no gig-E so I just want
the usrp2 stuff out of
