# \[VOLK\] Summary of call

**URL:** <https://www.ruby-forum.com/t/volk-summary-of-call/238034>\
**Category:** GNU Radio\
**Created:** [December 12, 2013, 9:13pm UTC](https://www.ruby-forum.com/t/volk-summary-of-call/238034 "2013-12-12T21:13:05Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![musicdenotation](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/ea666f/32.png) [@musicdenotation](https://www.ruby-forum.com/u/musicdenotation)\
**Post date:** [December 12, 2013, 9:13pm UTC](https://www.ruby-forum.com/t/volk-summary-of-call/238034/1 "2013-12-12T21:13:05Z")

</div>

The VOLK working group had a call earlier today. Agenda and summary  
are here:  
[http://gnuradio.org/redmine/projects/gnuradio/wiki/Call20131212](http://gnuradio.org/redmine/projects/gnuradio/wiki/Call20131212)

We’ll likely have our next call late January or February time-frame.

There’s a semi-open question about what kind of stats we should  
collect. Tim added support for taking CFLAGS at build time and  
/proc/version and /proc/cpuinfo at runtime. While we’re at it are  
there any other machine features that would be useful to collect?

-Nathan

---

<div class="post-metadata">

**Author:** ![WestS\_Nathan](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/8baadc/32.png) [@WestS\_Nathan](https://www.ruby-forum.com/u/WestS_Nathan)\
**Post date:** [December 12, 2013, 10:02pm UTC](https://www.ruby-forum.com/t/volk-summary-of-call/238034/2 "2013-12-12T22:02:10Z")

</div>

On Thu, Dec 12, 2013 at 3:11 PM, West, Nathan  
[removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)wrote:

> 

Toolchain name/version info please!  
([http://gnuradio.org/redmine/issues/620](http://gnuradio.org/redmine/issues/620))

Unless, of course, Tim’s support for CFLAGS already includes that info  
and/or patch…

---

<div class="post-metadata">

**Author:** ![WestS\_Nathan](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/8baadc/32.png) [@WestS\_Nathan](https://www.ruby-forum.com/u/WestS_Nathan)\
**Post date:** [December 12, 2013, 10:08pm UTC](https://www.ruby-forum.com/t/volk-summary-of-call/238034/3 "2013-12-12T22:08:01Z")

</div>

On 12/12/2013 04:01 PM, Douglas G. wrote:

> ```
> collect. Tim added support for taking CFLAGS at build time and
> /proc/version and /proc/cpuinfo at runtime. While we're at it are
> there any other machine features that would be useful to collect?
> 
> ```
> 
> Toolchain name/version info please!  
> ([http://gnuradio.org/redmine/issues/620](http://gnuradio.org/redmine/issues/620))
> 
> Unless, of course, Tim’s support for CFLAGS already includes that info  
> and/or patch…

Yep, already working on including compiler name / version as well

---

<div class="post-metadata">

**Author:** ![WestS\_Nathan](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/8baadc/32.png) [@WestS\_Nathan](https://www.ruby-forum.com/u/WestS_Nathan)\
**Post date:** [December 12, 2013, 10:11pm UTC](https://www.ruby-forum.com/t/volk-summary-of-call/238034/4 "2013-12-12T22:11:32Z")

</div>

On Thu, Dec 12, 2013 at 4:07 PM, Tim [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> > There’s a semi-open question about what kind of stats we should
> 
> Yep, already working on including compiler name / version as well

Yeah. Tim and I have been working on this. Should be able to merge it  
soon. Adds ‘–cc’, ‘–cxx’, and ‘–cflags’ to gnuradio-config-info to  
get the information we used to compile with. Also created a new  
volk-config-info program that gives similar information about the VOLK  
build.

I updated the dev call wiki page with some info on this.

Tom