Empty volk directory when I git gnuradio

Looks like some kind of link or something is broken when you try to GIT
gnuradio. The build fails as volk will not build, and the volk sub-
directory is empty. I did successfully GIT volk directly and clone it
to it’s sub-directory in gnuradio, and the build then went fine.

Just throwing that out there so someone can try to fix it or get it

Chris “Gump” Graves

git clone --recursive

On 04/01/2015 10:20 AM, Sylvain M. wrote:

git clone --recursive

Discuss-gnuradio mailing list
[email protected]
Discuss-gnuradio Info Page
When did the change actually occur? I knew it was coming, but was
waiting to update build-gnuradio to take this into account.

This happened on Sunday. The --recursive flag could have been added at
point in anticipation of it.

On 04/01/2015 11:26 AM, Johnathan C. wrote:

This happened on Sunday. The --recursive flag could have been added
at any point in anticipation of it.

Well, spank me. I’d had it in my fuzzy little brain that I’d have to
wait. Ah well, just testing an update to build-gnuradio now.

Actually now I see it would probably be:

git pull --recurse-submodules=on
git submodule update

View this message in context:
Sent from the GnuRadio mailing list archive at Nabble.com.

When I clone from the gnuradio repository:

git clone --recursive http://git.gnuradio.org/git/gnuradio.git

The clone succeeds. It is on the master branch. I can checkout next,
switch back and forth
between next and master. However when I attempt to checkout maint, git
the checkout is aborted
because the untracked working tree (everything in volk) would be
overwritten by the maint checkout.

$ git checkout maint
error: The following untracked working tree files would be overwritten
… many line of volk/ contents …


Any advice on how to get to the maint version?

– Tom, N5EG

On Sun, Apr 5, 2015 at 11:51 AM, Tom McDermott [email protected]

– Tom, N5EG

You’ll need to deinitialize the volk submodule first to make it a clean

git submodule deinit volk
git checkout maint

Probably best not to worry too much about this. For feature branches,
you’ll do this and then rebase off master to prevent this happening
For maint, if you need it, best to keep a separate directory just for

This is temporary. The planned release of 3.7.7 is next Monday. When
happens, master becomes maint, so the current maint issue will go away.


Can you you add the --recursive in the README?

I assume a standard “git pull” will be sufficient in the future or do we
also need to do a “git submodule update”?


View this message in context:
Sent from the GnuRadio mailing list archive at Nabble.com.

Thanks, Tom.

It works.

After checking out maint, I can checkout master then,
git submodule init volk
and now all 3 branches (next, master, maint) checkout correctly.

My issue was being unfamiliar with git submodules.

I’ll wait for 3.7.7 before further testing - so many new cool features
play with!

– Tom, N5EG