Joegen,  I the compiler is very picky, can you check in fixes for
these? I've fixed them in the past, but probably should have told you
about this requirement.

Levend, I hope you figured out how to add LFs to those files to get
thru the errors

On Tue, May 10, 2011 at 2:51 AM, Levend Sayar <[email protected]> wrote:
> At least I build all rpms, but for sipXproxy rpm it gave 2 "no newline
> at the end" errors.
>
> ../sipXproxy/lib/authplugins/CallerAlias.cpp
> ../sipXproxy/lib/authplugins/SubscriptionAuth.cpp
>
> _lvnd_
> (^_^)
>
>
>
> On Mon, May 9, 2011 at 11:26 PM, Levend Sayar <[email protected]> wrote:
>> Thank you very much Douglas.
>>
>> I put it there,since I am a little bit lazy. Not to write same thing
>> on each configure :)
>>
>> rpm --dbpath does want I wanted.
>>
>> I am not building rpms normally. This is just an exception, but I will
>> check your squid solution.
>> Maybe we can use it on our continuous integration machine.
>>
>> _lvnd_
>> (^_^)
>>
>>
>>
>> On Mon, May 9, 2011 at 11:10 PM, Douglas Hubler <[email protected]> wrote:
>>> On Mon, May 9, 2011 at 3:43 PM, Levend Sayar <[email protected]> wrote:
>>>> I put RPM_DIST_DIR to my .bashrc setting as environment variable.
>>>
>>> don't do that ;)  Do
>>>
>>>  ./configure RPM_DIST_DIR=/some/other/place
>>>
>>>
>>>> I wanted to see the exact sipxportlib rpm installed on mock
>>>> filesystem. I thought that
>>>> if I rpm -e that rpm, I can continue build without making
>>>> repo-chroot-init from scratch.
>>>> I mean I wanted to erase 4.4.0 version of sipxportlib from mock.
>>>
>>>
>>> I think that the rpm database is actually managed by the non-chrooted
>>> operating system.  So this command lists all rpms for a given system
>>>
>>>  rpm --dbpath /var/lib/mock/centos-5-x86_64/root/var/lib/rpm -qa
>>>
>>> You should call make repo-chroot-init before each build.  If it's too
>>> slow, there are instructions on wiki for setting up a squid caching
>>> server I highly recommend.
>>> _______________________________________________
>>> sipx-dev mailing list
>>> [email protected]
>>> List Archive: http://list.sipfoundry.org/archive/sipx-dev/
>>>
>>
> _______________________________________________
> sipx-dev mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-dev/
>
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/

Reply via email to