Ok,
can anyone identify a certain "GOOD" build to use for the git bisect?
(Say where 2.1.7 was released?)
I looked through the logs and have arbitrarily selected,
134f314c57d67b56bab93db4089c25e956ad6cf2] Lots of notes prior to 2.1.7
I do not know how to force git to build that revision so I could actually
verify it is good.
Thanks,
-craig
----- Original Message -----
From: "Craig Campbell" <craig at ccraft.ca>
To: "FreeRadius users mailing list" <freeradius-users at lists.freeradius.org>
Sent: Tuesday, November 24, 2009 7:28 AM
Subject: Re: Unexpected "Exiting normally" 2.1.8?
> Thanks for the correction.
>
> I have rebuilt and am re-running my test. I just hope I didn't somehow
> taint the bisect work and provide misleading information to Alan.
>
> I should know some time today if I need to redo the bisection.
> For my previous work I had done,
>
> $git bisect start
> $git bisect bad
> $git bisect good 321c0ae58641f709d115526bb564cbd8c4dab71d <- I do
> not have full confidence in this
>
> Followed by loops of ,
> $./conf
> $CFLAGS='-O0 -g' ./configure
> $make clean
> $find . -name "*.o" <- sometimes I found lingering .o
> files - not certain why. I would delete any I discovered at this point
> $make
> $git bisect skip|bad|good <- depending on if build failed, binary
> crashed or other error (skip), had error (bad), or succeeded(good)
> $git pull <- I THINK this may be
> unnecessary.. but not certain. Docs I found on git were not entirely
> clear
>
> If I need to re-bisect, could you perhaps spoon feed me the commands to
> ensure I'm doing it correctly? Specifically, how can I acquire and verify
> I have my first "good" build? And then the incantation to perform
> iterative bisections until I run out.
>
> I truly hope I haven't provided misleading info.
>
> Thanks,
> -craig
> ----- Original Message -----
> From: "Alexander Clouter" <alex at digriz.org.uk>
> To: <freeradius-users at lists.freeradius.org>
> Sent: Monday, November 23, 2009 8:13 AM
> Subject: Re: Unexpected "Exiting normally" 2.1.8?
>
>
>> Hi,
>>
>> Craig Campbell <craig at ccraft.ca> wrote:
>>>
>>> I re -acquired the source, but there seems to be a (minor I think)
>>> error.
>>>
>>> $git clone git://git.freeradius.org/freeradius-server.git
>>> $cd freeradius-server
>>> $git fetch origin stable:stable
>>> $git pull <----- should be 'git checkout stable'
>>> $make clean
>>> $CFLAGS='-O0 -g' ./configure
>>> $make
>>>
>> Otherwise if I am reading that right you are trying to compile off the
>> unstable branch.
>>
>> Cheers
>>
>> --
>> Alexander Clouter
>> .sigmonster says: BOFH excuse #169:
>> broadcast packets on wrong frequency
>>
>> -
>> List info/subscribe/unsubscribe? See
>> http://www.freeradius.org/list/users.html
>>
>> __________ Information from ESET Smart Security, version of virus
>> signature database 4630 (20091123) __________
>>
>> The message was checked by ESET Smart Security.
>>
>> http://www.eset.com
>>
>>
>>
>
>
> __________ Information from ESET Smart Security, version of virus
> signature database 4632 (20091124) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>
>
>
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html
>
> __________ Information from ESET Smart Security, version of virus
> signature database 4632 (20091124) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>
>
>
__________ Information from ESET Smart Security, version of virus signature database 4635 (20091125) __________
The message was checked by ESET Smart Security.
http://www.eset.com