This is 007b401cf14fcfc067d11f5e4d2ca1730407803b, which according to my git-foo is the latest commit to (aka HEAD of) this branch. Fixing it "right now" is not a big deal IMHO: I just keep the gnuradio-next branch up to date and if it works that's great and if it does not then (as the description states) use the current gnuradio-next install and check back in a few days and hopefully the build will have been fixed. I'm going to leave this port where it is, and I'll just continue to update it as commits are merged.
Please do feel free to ping me about OSX stuff if/when you need/want to. - MLD On Apr 1, 2013, at 12:53 PM, Tom Rondeau <[email protected]> wrote: > On Mon, Apr 1, 2013 at 12:44 PM, Michael Dickens <[email protected]> wrote: >> Carles points out that the next branch is failing on OSX (via the >> "gnuradio-next" port). Here's the error log. Ideas? - MLD > > Is this the current HEAD on the next branch? As we've said, we're > going through a lot of major changes on next right now as the last > steps to 3.7. One huge change I've just recently finished was removing > gruel and putting all of it's functionality into gnuradio-runtime. > That could either fix this problem or make it worse... > > Regardless, I'm not inclined to spend too much time right now > debugging it until we're more fully settled on the structure in > 'next.' For now, I'd go back before the major gnuradio-runtime > changes. I think this commit should work: > 40ab0030dbe821c9ed475a0b73898040f4af581c > > I might bug you for some help on OSX issues in a few days when we > think that we're ready. _______________________________________________ Discuss-gnuradio mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
