NSPR + NSS now in mozilla-central

[Benjamin Smedberg]

I have imported static tags of NSPR and NSS code into mozilla-central. This
means that developers no longer need to run client.py after pulling
mozilla-central: all the source code is self-contained in the repository.

However, if you have an existing working tree, you will need to delete the
old, untracked NSPR and NSS files:

rm -rf nsprpub dbm security/nss security/coreconf security/dbm

Happy hacking!

--BDS
_______________________________________________
dev-builds mailing list
dev-builds@...
https://lists.mozilla.org/listinfo/dev-builds

[Justin Wood (Callek)-2]

Benjamin Smedberg wrote:
> I have imported static tags of NSPR and NSS code into mozilla-central.
> This means that developers no longer need to run client.py after pulling
> mozilla-central: all the source code is self-contained in the repository.
>
> However, if you have an existing working tree, you will need to delete
> the old, untracked NSPR and NSS files:
>
> rm -rf nsprpub dbm security/nss security/coreconf security/dbm
>

Would it be worth making client.py work also to do a test for
nsprpub/CVS || dbm/CVS ... etc. and removing the dirs if they exist,
just so that an easy run of client.py can't hurt anyone, or think that
is just wasted effort?

--
~Justin Wood (Callek)
_______________________________________________
dev-builds mailing list
dev-builds@...
https://lists.mozilla.org/listinfo/dev-builds

[Benjamin Smedberg]

Justin Wood (Callek) wrote:

> Benjamin Smedberg wrote:
>> I have imported static tags of NSPR and NSS code into mozilla-central.
>> This means that developers no longer need to run client.py after
>> pulling mozilla-central: all the source code is self-contained in the
>> repository.
>>
>> However, if you have an existing working tree, you will need to delete
>> the old, untracked NSPR and NSS files:
>>
>> rm -rf nsprpub dbm security/nss security/coreconf security/dbm
>>
>
> Would it be worth making client.py work also to do a test for
> nsprpub/CVS || dbm/CVS ... etc. and removing the dirs if they exist,
> just so that an easy run of client.py can't hurt anyone, or think that
> is just wasted effort?

IMO the one-time hit isn't worth the additional coding and testing required.

--BDS
_______________________________________________
dev-builds mailing list
dev-builds@...
https://lists.mozilla.org/listinfo/dev-builds

[Nelson Bolyard]

Benjamin Smedberg wrote, On 2008-06-06 08:24:

> I have imported static tags of NSPR and NSS code into mozilla-central. This
> means that developers no longer need to run client.py after pulling
> mozilla-central: all the source code is self-contained in the repository.
>
> However, if you have an existing working tree, you will need to delete the
> old, untracked NSPR and NSS files:
>
> rm -rf nsprpub dbm security/nss security/coreconf security/dbm
>
> Happy hacking!

Hereafter,
Mozilla will have greater appreciation for the term "down stream".
_______________________________________________
dev-builds mailing list
dev-builds@...
https://lists.mozilla.org/listinfo/dev-builds

[John J Barton]

Benjamin Smedberg wrote:
> I have imported static tags of NSPR and NSS code into mozilla-central.
> This means that developers no longer need to run client.py after pulling
> mozilla-central: all the source code is self-contained in the repository.
>
> However, if you have an existing working tree, you will need to delete
> the old, untracked NSPR and NSS files:
>
> rm -rf nsprpub dbm security/nss security/coreconf security/dbm

I just did a clone of mozilla-central and when I build I hit

https://bugzilla.mozilla.org/show_bug.cgi?id=338224

which occurs in the nsprpub directory removed above. I don't understand
any of the first paragraph above.

Is nsprpub needed? should it be deleted after cloning the source or not?

jjb
_______________________________________________
dev-builds mailing list
dev-builds@...
https://lists.mozilla.org/listinfo/dev-builds

[Ted Mielczarek-3]

On Oct 9, 2:57 pm, John J Barton <johnjbar...@...> wrote:
> I just did a clone of mozilla-central and when I build I hit
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=338224
>
> which occurs in the nsprpub directory removed above. I don't understand
> any of the first paragraph above.
>
> Is nsprpub needed? should it be deleted after cloning the source or not?

Yes, you need NSPR to build Firefox. The "rm" was only if you had
cloned a tree a while ago and checked out NSPR/NSS from CVS.

-Ted
_______________________________________________
dev-builds mailing list
dev-builds@...
https://lists.mozilla.org/listinfo/dev-builds

[John J Barton]

Ted Mielczarek wrote:

> On Oct 9, 2:57 pm, John J Barton <johnjbar...@...> wrote:
>> I just did a clone of mozilla-central and when I build I hit
>>
>> https://bugzilla.mozilla.org/show_bug.cgi?id=338224
>>
>> which occurs in the nsprpub directory removed above. I don't understand
>> any of the first paragraph above.
>>
>> Is nsprpub needed? should it be deleted after cloning the source or not?
>
> Yes, you need NSPR to build Firefox. The "rm" was only if you had
> cloned a tree a while ago and checked out NSPR/NSS from CVS.
>
> -Ted

Ok, any suggestions on how to build nspr.pdb? Any idea what it is?
_______________________________________________
dev-builds mailing list
dev-builds@...
https://lists.mozilla.org/listinfo/dev-builds

[John J Barton]

John J Barton wrote:
> Ok, any suggestions on how to build nspr.pdb? Any idea what it is?

pdb is created by VC++ to hold debugging symbols. It is created when the
compile includes /Zi option. To name the target .pdb file, you use /Fd.
There is no makefile in my tree that contains /Fd so nspr4.pdb is not
going to be created. I believe the configuration sets up to require .pdb
but does not emit the rule to create the .pdb

 From reading the makefiles, it seems that MOZ_DEBUG_SYMBOLS may be
required for this kind of configuration. I'll try that when I get back
to that machine.

jjb


_______________________________________________
dev-builds mailing list
dev-builds@...
https://lists.mozilla.org/listinfo/dev-builds