On Sun, Feb 27, 2011 at 6:51 AM, Arya Santini <arya.santi...@gmail.com>wrote:

> Hi Jared, thanks for that suggestion.
>
> Anyway, I realized that I was using GNU compiler gcc-4.6
> (experimental) which apparently imposes stricter rules and allows
> package builds to fail where previous versions used to succeed. So the
> suggested fix for one typical "ptrdiff_t does not name a type" is
> #include <cstddef.h>, which I did in the
> /usrp/host/swig/python/usrp_prims.cc file, and the build completed to
> success.
>
> Arya
>

Thanks for bringing this up (and for the solution). The usrp_prims.cc file
is actually generated by SWIG, so I've explicitly included stddef.h into the
.i file, which is done for most of the other SWIG files already for other
reasons. This really seems like a SWIG problem, so hopefully this will be
fixed in future releases before the new GCC takes over. Hopefully, this
fixes our last hole, anyways.

I'll be pushing changes to next and master soon.

Tom




> On Sun, Feb 27, 2011 at 3:15 AM, Jared Harvey <m...@jaredharvey.com>
> wrote:
> > Hello Arya,
> >
> > AS> I  was  trying  to  build  the gnuradio on yet
> > AS> another  machine  running  Ubuntu  10.10. from
> > AS> source  today  after  checking  out the latest
> > AS> code from the dev trunk:
> >
> > I see Ubuntu 10.10 has native packages. Is there a
> > reason why you need to compile it? Perhaps you are
> > looking for the latest and greatest.
> >
> > You    may   have   dependency   problems.   These
> > dependencies  may  be  resolved  by installing the
> > native packages. Perhaps you can open Synaptic and
> > install  the  native  gnuradio that way and see if
> > that helps your compile process.
> >
> > Best regards.
> >
> > .. ..-. / -.-- --- ..- / .-. . .- -.. /  - .... .. ...
> > .-.. . - ... / .... .- ...- . / .- / -... . . .-.
> >
> >  Jared Harvey                           Operator KB1GTT
> >
> > e-mail m...@jaredharvey.com
> > Web page http://jaredharvey.com
> >
> >
> > _______________________________________________
> > Discuss-gnuradio mailing list
> > Discuss-gnuradio@gnu.org
> > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> >
>
> _______________________________________________
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Reply via email to