Re: [Discuss-gnuradio] Re: Ticket #12 - libossaudio link issue on NetBSD

2006-08-05 Thread Johnathan Corgan
Eric Blossom wrote:

> Berndt, did gr-audio-oss work OK on NetBSD before this change?
> 
> If so, then we dropped something in the migration.

This looks like the same mistake I made with the audio-portaudio, being
too aggressive at removing stuff when extracting the component specific
stuff from the individual configure.ac's.

With the stuff in my ticket-12 branch I think we'll get to the bottom of
it pretty soon.

-Johnathan



signature.asc
Description: OpenPGP digital signature
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] Re: Ticket #12 - libossaudio link issue on NetBSD

2006-08-05 Thread Eric Blossom
On Sat, Aug 05, 2006 at 05:49:01PM -0700, Johnathan Corgan wrote:
> Berndt Josef Wulf wrote:
> 
> >> A trial fix for this issue is at:
> >>
> >> http://gnuradio.utah.edu/svn/gnuradio/branches/developers/jcorgan/ticket-12
> 
> > Thanks, but bad news: it still doesn't work.
> 
> Thanks, I'll look into this.  It's tough when I don't have a system to
> check it with but as long as you can try these out for me we'll get to
> the bottom of it.
> 
> -Johnathan

Berndt, did gr-audio-oss work OK on NetBSD before this change?

If so, then we dropped something in the migration.

Eric


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] Re: Ticket #12 - libossaudio link issue on NetBSD

2006-08-05 Thread Johnathan Corgan
Johnathan Corgan wrote:

> Thanks, I'll look into this.  It's tough when I don't have a system to
> check it with but as long as you can try these out for me we'll get to
> the bottom of it.

Berndt--okay, please svn update that branch and try again.  Can you pay
attention to the ./configure script output?  I added a line that should
report the value of OSS_LIBS if it detects it.  I need to know if the
configure script is getting this right or whether somehow it doesn't get
included correctly in the list of libraries when linking in the Makefile.am.

Thanks,

-Johnathan



signature.asc
Description: OpenPGP digital signature
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


[Discuss-gnuradio] Re: Ticket #12 - libossaudio link issue on NetBSD

2006-08-05 Thread Johnathan Corgan
Berndt Josef Wulf wrote:

>> A trial fix for this issue is at:
>>
>> http://gnuradio.utah.edu/svn/gnuradio/branches/developers/jcorgan/ticket-12

> Thanks, but bad news: it still doesn't work.

Thanks, I'll look into this.  It's tough when I don't have a system to
check it with but as long as you can try these out for me we'll get to
the bottom of it.

-Johnathan



signature.asc
Description: OpenPGP digital signature
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] svn merging etc

2006-08-05 Thread Eric Blossom
On Sat, Aug 05, 2006 at 08:28:45PM -0400, Achilleas Anastasopoulos wrote:
> Eric,
> 
> I have to admit that I am a bit overwhelmed with
> all these. I am still reading ch2 of the svn manual
> and it doesn't go that fast...
> 
> At this point the gr-trellis compiles fine, so in
> my opinion it can be incorporated in the trunk.
> Then, we can work on the automated expansion, etc.
> 
> Best,
> Achilleas

No problem.

Do you want to merge and commit, or would you like me to do it?

Eric


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


[Discuss-gnuradio] Re: Ticket #12 - libossaudio link issue on NetBSD

2006-08-05 Thread Berndt Josef Wulf
On Sunday 06 August 2006 03:52, Johnathan Corgan wrote:
> Berndt:
>
> A trial fix for this issue is at:
>
> http://gnuradio.utah.edu/svn/gnuradio/branches/developers/jcorgan/ticket-12
>
> Could you please check this out into a fresh directory and test?  I've
> disabled all the components except gnuradio-core and gr-audio-oss.
>
> I created an autoconf macro to test for the ossaudio library when the
> target machine is NetBSD, otherwise is tests for sys/soundcard.h like
> the current method.  The Makefile.am will link in the ossaudio library
> where needed if found.
>
> -Johnathan

Thanks, but bad news: it still doesn't work.

barossa: {4} ldd /usr/pkg/lib/python2.4/site-packages/gnuradio/_audio_oss.so
/usr/pkg/lib/python2.4/site-packages/gnuradio/_audio_oss.so:
-lm.0 => /usr/lib/libm387.so.0
-lm.0 => /usr/lib/libm.so.0
-lfftw3f.3 => /usr/pkg/lib/libfftw3f.so.3
-lstdc++.5 => /usr/lib/libstdc++.so.5
-lgcc_s.1 => /usr/lib/libgcc_s.so.1
-lgnuradio-core.0 => /usr/pkg/lib/libgnuradio-core.so.0

libossaudio isn't linked in compared to the version that works 

/usr/pkg/lib/python2.4/site-packages/gnuradio/_audio_oss.so:
-lossaudio.0 => /usr/lib/libossaudio.so.0
-lm.0 => /usr/lib/libm387.so.0
-lm.0 => /usr/lib/libm.so.0
-lfftw3f.3 => /usr/pkg/lib/libfftw3f.so.3
-lstdc++.5 => /usr/lib/libstdc++.so.5
-lgcc_s.1 => /usr/lib/libgcc_s.so.1
-lgnuradio-core.0 => /usr/pkg/lib/libgnuradio-core.so.0

configure detects the libossaudio library but OSS_LIBS doesn't substitute it 
into gr-audio-oss/src/Makefile


cheerio Berndt


pgpO9cw9HZ5NF.pgp
Description: PGP signature
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] svn merging etc

2006-08-05 Thread Achilleas Anastasopoulos

Eric,

I have to admit that I am a bit overwhelmed with
all these. I am still reading ch2 of the svn manual
and it doesn't go that fast...

At this point the gr-trellis compiles fine, so in
my opinion it can be incorporated in the trunk.
Then, we can work on the automated expansion, etc.


Best,
Achilleas

Eric Blossom wrote:


Johnanthan, FYI, I created the branch [probably bad form.]

Achilleas, I did create your account with the given password.

There's been a lot of work in trunk since the branch was checked out.
The branch only adds gr-trellis.  I think it would apply cleanly to
trunk, however it still doesn't automatically expand the templates, so
I don't think it's time for that merge.

My thought is to merge all the trunk changes into the branch (being
careful of course to record the range in the merge commit message), confirm
that everything is still working, and then finish the automation of
the template expansion.  Then finally merge it all back in to trunk.

Achilleas, I can finish the template expansion automation after we
merge trunk to branch.

How's this sound?  


The branch was created from revision 3155.  See below

[EMAIL PROTECTED] ~]$ cd gr/anastas
[EMAIL PROTECTED] anastas]$ svn log --verbose --stop-on-copy

r3156 | eb | 2006-08-04 12:07:21 -0700 (Fri, 04 Aug 2006) | 2 lines
Changed paths:
   A /gnuradio/branches/developers/anastas/wip (from /gnuradio/trunk:3155)

Created branch to use to merge in gr-trellis




The current revision of the trunk is 3174

[EMAIL PROTECTED] ~]$ cd gr/trunk/
[EMAIL PROTECTED] trunk]$ svn up
U  gr-usrp/src/Makefile.am
U  Makefile.common
U  config/grc_gr_audio_osx.m4
U  config/grc_gr_comedi.m4
U  config/grc_gr_audio_alsa.m4
U  config/grc_usrp.m4
U  config/grc_gr_video_sdl.m4
U  config/grc_gr_audio_oss.m4
U  config/grc_gr_audio_portaudio.m4
U  config/grc_gr_audio_jack.m4
U  config/grc_gr_usrp.m4
U  config/grc_gr_audio_windows.m4
Updated to revision 3174.

So sitting in the top of the wip directory

  $ cd gr/anastas  [your's may be named something different}
  $ svn merge -r 3156:3174 http://gnuradio.utah.edu/svn/gnuradio/trunk

should merge those changes in [Johnathan, do I have this right?]

Check that this all compiles, then commit the merge to the branch.

  $ svn commit -m 'ported r3156:3174 (lots of stuff) from trunk'

Let me know when this is complete, and I'll finish off the automation.

FYI, the example on page 51 of "Version Control with Subversion (1.2)"
"Copying Specific Changes" is what I'm looking at as I write this...

Eric





___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] ubuntu build report

2006-08-05 Thread Johnathan Corgan
Matt Ettus wrote:

>- if you do a make -j 2 then it fails when it gets to
> gnuradio_swig_python.  Calling make again after that completes the
> gnuradio-core build ok.

This is open ticket #13.

>- building usrp fails in prims.cc:
> 
> prims.cc:1561:24: error: usrp_prims.h: No such file or directory

Eric fixed this now in r3175 on the trunk.

-Johnathan



signature.asc
Description: OpenPGP digital signature
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] svn merging etc

2006-08-05 Thread Johnathan Corgan
Johnathan Corgan wrote:

> ..."grab everything since 3155 up until and including changeset 3174"

Well, technically a better way to say it is:

"get the difference between the repository state @ revision 3155 and the
repository state @ revision 3174"

-Johnathan



signature.asc
Description: OpenPGP digital signature
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] svn merging etc

2006-08-05 Thread Johnathan Corgan
Eric Blossom wrote:

> The branch was created from revision 3155.  See below

> The current revision of the trunk is 3174

> So sitting in the top of the wip directory
> 
>   $ cd gr/anastas  [your's may be named something different}
>   $ svn merge -r 3156:3174 http://gnuradio.utah.edu/svn/gnuradio/trunk
> 
> should merge those changes in [Johnathan, do I have this right?]

It should be -r 3155:3174

..."grab everything since 3155 up until and including changeset 3174"

-Johnathan



signature.asc
Description: OpenPGP digital signature
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] make fails on new svn

2006-08-05 Thread Johnathan Corgan
Eric Blossom wrote:

> FYI, the .libs should have never been in the path.
> The .la file, which libtool looks for, is contained in foo, not foo/.libs

Correct.  For some reason the extra .libs I put in there was being
"overlooked" when compiling with the combination of libtool & gcc on our
machines, but on Achilleas'.

-Johnathan



signature.asc
Description: OpenPGP digital signature
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] make fails on new svn

2006-08-05 Thread Eric Blossom
On Fri, Aug 04, 2006 at 09:33:00PM -0700, Johnathan Corgan wrote:
> Achilleas Anastasopoulos wrote:
> 
> > Any thoughts?
> 
> For some reason there is an extra '.libs' added to the path to where
> it's looking for libgnuradio-core.so and for libusrp.so; I don't know
> why.  But it's very likely a bug and not anything you are doing.
> 
> Can you log in to Trac as guest (password 'gnuradio') and file a bug in
> component 'build'?  Assign it to me.
> 
> Thanks.
> -Johnathan

FYI, the .libs should have never been in the path.
The .la file, which libtool looks for, is contained in foo, not foo/.libs

Eric


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] svn merging etc

2006-08-05 Thread Eric Blossom
On Sat, Aug 05, 2006 at 12:13:58AM -0700, Johnathan Corgan wrote:
> Achilleas Anastasopoulos wrote:
> 
> > I was wondering if you can commit this change that
> > fixed the error also to my wip directory:
> > http://gnuradio.utah.edu/svn/gnuradio/branches/developers/anastas/wip/
> > since it does not yet compile with gcc3.4,
> > or is this something that I am supposed to do?
> 
> I hope you don't mind my copying the list as this is important
> information for other developers as well.
> 
> Ideally you'd be periodically merging changes on the trunk into your
> working copy, so you can see if there is any problem with what you're
> working on what's going on elsewhere.
> 
> If revision M is the version of the trunk that was originally copied
> into your developer branch, and N is the latest revision in the trunk,
> then the following command would accomplish this (you must be at the top
> of your working copy):
> 
> svn merge -rN:M http://gnuradio.utah.edu/svn/gnuradio/trunk
> 
> Your working copy will have all the stuff merged in; you'll need to
> verify there were no conflicts.  If there were, you'll need to fix them
> up.  Now you can check in your local copy with a log message indicating
> that you merged from trunk from revision M to revision N.
> 
> This latter is important to get in the log.  The next time you do a
> merge from the trunk, you'll want to start at the highest revision you
> last merged.  In the above case, this is revision M.  So having it in
> the log makes it easy for you to go check this.
> 
> If you just want to get the fix for ticket #11, use -r3171:3172 in the
> above command.  This may complicate your merging from the trunk at a
> later time as you'll have a -rN:M range that overlaps the above, and
> you'll get a reject for the affected files when it tries to apply the
> diff to something that it has already been applied to.
> 
> When you're ready to merge your wip stuff into the trunk, I'll walk you
> through that as it involves a different set of commands based on whether
> you've been periodically merging from the trunk into your wip or not.
> 
> -Johnathan

Johnanthan, FYI, I created the branch [probably bad form.]

Achilleas, I did create your account with the given password.

There's been a lot of work in trunk since the branch was checked out.
The branch only adds gr-trellis.  I think it would apply cleanly to
trunk, however it still doesn't automatically expand the templates, so
I don't think it's time for that merge.

My thought is to merge all the trunk changes into the branch (being
careful of course to record the range in the merge commit message), confirm
that everything is still working, and then finish the automation of
the template expansion.  Then finally merge it all back in to trunk.

Achilleas, I can finish the template expansion automation after we
merge trunk to branch.

How's this sound?  

The branch was created from revision 3155.  See below

[EMAIL PROTECTED] ~]$ cd gr/anastas
[EMAIL PROTECTED] anastas]$ svn log --verbose --stop-on-copy

r3156 | eb | 2006-08-04 12:07:21 -0700 (Fri, 04 Aug 2006) | 2 lines
Changed paths:
   A /gnuradio/branches/developers/anastas/wip (from /gnuradio/trunk:3155)

Created branch to use to merge in gr-trellis




The current revision of the trunk is 3174

[EMAIL PROTECTED] ~]$ cd gr/trunk/
[EMAIL PROTECTED] trunk]$ svn up
U  gr-usrp/src/Makefile.am
U  Makefile.common
U  config/grc_gr_audio_osx.m4
U  config/grc_gr_comedi.m4
U  config/grc_gr_audio_alsa.m4
U  config/grc_usrp.m4
U  config/grc_gr_video_sdl.m4
U  config/grc_gr_audio_oss.m4
U  config/grc_gr_audio_portaudio.m4
U  config/grc_gr_audio_jack.m4
U  config/grc_gr_usrp.m4
U  config/grc_gr_audio_windows.m4
Updated to revision 3174.

So sitting in the top of the wip directory

  $ cd gr/anastas  [your's may be named something different}
  $ svn merge -r 3156:3174 http://gnuradio.utah.edu/svn/gnuradio/trunk

should merge those changes in [Johnathan, do I have this right?]

Check that this all compiles, then commit the merge to the branch.

  $ svn commit -m 'ported r3156:3174 (lots of stuff) from trunk'

Let me know when this is complete, and I'll finish off the automation.

FYI, the example on page 51 of "Version Control with Subversion (1.2)"
"Copying Specific Changes" is what I'm looking at as I write this...

Eric


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


[Discuss-gnuradio] ubuntu build report

2006-08-05 Thread Matt Ettus


Two problems building on a completely fresh ubuntu system:

   - if you do a make -j 2 then it fails when it gets to 
gnuradio_swig_python.  Calling make again after that completes the 
gnuradio-core build ok.

   - building usrp fails in prims.cc:

prims.cc:1561:24: error: usrp_prims.h: No such file or directory

Matt



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] New source code repository!

2006-08-05 Thread Johnathan Corgan
Robert McGwier wrote:

> bootstrap
> configure
> make
> make check
> sudo make install
> 
> now all complete and all my tests with code in examples work.
> 
> Bob

Thanks for testing. I'll wait for the bug report on the already fixed
portaudio issue so I can get that particular update into the trunk.

-Johnathan



signature.asc
Description: OpenPGP digital signature
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


[Discuss-gnuradio] Re: Ticket #12 - libossaudio link issue on NetBSD

2006-08-05 Thread Johnathan Corgan
Berndt:

A trial fix for this issue is at:

http://gnuradio.utah.edu/svn/gnuradio/branches/developers/jcorgan/ticket-12

Could you please check this out into a fresh directory and test?  I've
disabled all the components except gnuradio-core and gr-audio-oss.

I created an autoconf macro to test for the ossaudio library when the
target machine is NetBSD, otherwise is tests for sys/soundcard.h like
the current method.  The Makefile.am will link in the ossaudio library
where needed if found.

-Johnathan



signature.asc
Description: OpenPGP digital signature
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] make fails on new svn

2006-08-05 Thread Johnathan Corgan
Achilleas Anastasopoulos wrote:

> I was wondering if you can commit this change that
> fixed the error also to my wip directory:
> http://gnuradio.utah.edu/svn/gnuradio/branches/developers/anastas/wip/
> since it does not yet compile with gcc3.4,
> or is this something that I am supposed to do?

I hope you don't mind my copying the list as this is important
information for other developers as well.

Ideally you'd be periodically merging changes on the trunk into your
working copy, so you can see if there is any problem with what you're
working on what's going on elsewhere.

If revision M is the version of the trunk that was originally copied
into your developer branch, and N is the latest revision in the trunk,
then the following command would accomplish this (you must be at the top
of your working copy):

svn merge -rN:M http://gnuradio.utah.edu/svn/gnuradio/trunk

Your working copy will have all the stuff merged in; you'll need to
verify there were no conflicts.  If there were, you'll need to fix them
up.  Now you can check in your local copy with a log message indicating
that you merged from trunk from revision M to revision N.

This latter is important to get in the log.  The next time you do a
merge from the trunk, you'll want to start at the highest revision you
last merged.  In the above case, this is revision M.  So having it in
the log makes it easy for you to go check this.

If you just want to get the fix for ticket #11, use -r3171:3172 in the
above command.  This may complicate your merging from the trunk at a
later time as you'll have a -rN:M range that overlaps the above, and
you'll get a reject for the affected files when it tries to apply the
diff to something that it has already been applied to.

When you're ready to merge your wip stuff into the trunk, I'll walk you
through that as it involves a different set of commands based on whether
you've been periodically merging from the trunk into your wip or not.

-Johnathan


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio