Changing to "next" fails?

GNU Radio
1

Hi,

Maybe a stupid question…am I doing smth. wrong, or has there been some
change? When doing a “git checkout next” and trying to build next, it
still
build master. Even completely deleting the gnuradio folder does not
help.
Also I get some error message when doing git checkout next, git branch
next
gives no error, but again it build master.

Ralph.

–

Ralph A. Schmid
Mondstr. 10
90762 Frth
+49-171-3631223
[email protected]
http://www.bclog.de/

2

On Mon, Apr 1, 2013 at 10:11 AM, Ralph A. Schmid, dk5ras
[email protected] wrote:

Hi,

Maybe a stupid question…am I doing smth. wrong, or has there been some
change? When doing a “git checkout next” and trying to build next, it still
build master. Even completely deleting the gnuradio folder does not help.
Also I get some error message when doing git checkout next, git branch next
gives no error, but again it build master.

The code hasn’t changed for days and it builds fine so yes, you are
probably doing something wrong. Without knowing what you do after the
checkout it’s hard to guess what it could be.

ALex

3

On Mon, Apr 1, 2013 at 3:43 PM, Ralph A. Schmid [email protected]
wrote:

The code hasn’t changed for days and it builds fine so yes, you are
probably doing something wrong. Without knowing what you do after the
checkout it’s hard to guess what it could be.

I have done what I have described :slight_smile: But the other tip seems to help, git pull
origin…

I meant that “trying to build next” after a checkout was bit vague
given that there are 5 steps to be executed after a checkout.

Alex

4

The code hasn’t changed for days and it builds fine so yes, you are
probably doing something wrong. Without knowing what you do after the
checkout it’s hard to guess what it could be.

I have done what I have described :slight_smile: But the other tip seems to help,
git pull
origin…

ALex

Ralph.

5

I meant that “trying to build next” after a checkout was bit vague given
that
there are 5 steps to be executed after a checkout.

Well, what are those steps to the book? sudo make uninstall, git
checkout
xxx, cd xxx, cmake …, make. Did I miss something? AS I have mentioned,
until now it did work this way, so I assumed that either something had
changed or I simply missed something, and before it worked by
coincidence.

Alex

Ralph.

6

Ralph,

“git branch next” just moves you over to the next branch but doesn’t
pull anything down. If there was an error doing “git pull next”, then
just moving to that branch wouldn’t have any effect.

This seems to be the problem, as usually git checkout xxx did the job.

Also, you mentioned an error. When asking for help and you have an
error, it makes it much easier for us to help you if you tell us what
the error is.

Of course, but in this case I assumed some basic problem, and I was
right :slight_smile:
The problem is that I usually do email from Windows, not from Linux, so
it
takes a second attempt to exactly copy the error and paste it.

Finally, while next hasn’t changed for a couple of days, we did a
pretty big change last week in our move to full 3.7 form. We removed
gnuradio-core and now have a gnuradio-runtime. This is probably the
cause of your issues.

I know this change, and that exactly is the reason that I wanted to give
it a
try. Now “next” is building while I ride a train from Munich to
Nuremburg with
300 km/h and sipping a beer.

Tom

Ralph.

7

Oh, by the way, at 72 % building fails. Some unspecified error 2 or smth
like that, no further information. Again I am in Windows now, can give
the
exact message when I boot Linux again, but I am afraid it said nothing
more.

Ralph.