Firefox 2.0 out


Firefox 2.0 has been released. If you’re looking to install it from pkgsrc, Geert Hendrickx is planning to create a separate package in pkgsrc, so that Firefox 1.5 can remain supported. Check www/firefox2 (may not exist yet; used to be wip/firefox2) for the new version.

Posted by     Categories: Goings-on     3 Comments
3 Comments on Firefox 2.0 out

Respond | Trackback

  1. Geert Hendrickx says:

    FYI, it’s in pkgsrc now:
    http://mail-index.netbsd.org/pkgsrc-changes/2006/10/24/0047.html
    (and similar for -gtk1 and -bin).

  2. timofonic says:

    Hello,

    thanks a lot to ghen, but sadly www/firefox and www/firefox2 not builds under DragonFly:

    c++ -o mozStorageModule.o -c -DMOZILLA_INTERNAL_API -DOSTYPE=\”DragonFly1.6\” -DOSARCH=\”DragonFly\” -DBUILD_ID=0000000000 -I./../src -I../../dist/include/storage -I../../dist/include/sqlite3 -I../../dist/include/xpcom -I../../dist/include/string -I../../dist/include/js -I../../dist/include/xpconnect -I../../dist/include/storage -I../../dist/include -I../../dist/include/nspr -I/usr/pkg/include -I/usr/pkg/include -I../../dist/sdk/include -I/usr/pkg/xorg/include -fPIC -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -I/usr/pkg/xorg/include -fno-rtti -fno-exceptions -Wall -Wconversion -Wpointer-arith -Wcast-align -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy -Wno-non-virtual-dtor -Wno-long-long -O2 -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -fshort-wchar -pthread -pipe -DNDEBUG -DTRIMMED -O2 -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -I/usr/pkg/xorg/include -DMOZILLA_CLIENT -include ../../mozilla-config.h -Wp,-MD,.deps/mozStorageModule.pp mozStorageModule.cpp
    rm -f libstoragecomps.so
    c++ -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -I/usr/pkg/xorg/include -fno-rtti -fno-exceptions -Wall -Wconversion -Wpointer-arith -Wcast-align -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy -Wno-non-virtual-dtor -Wno-long-long -O2 -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -fshort-wchar -pthread -pipe -DNDEBUG -DTRIMMED -O2 -fPIC -Wl,-R/usr/pkg/lib/firefox2 -shared -Wl,-z,defs -Wl,-h,libstoragecomps.so -o libstoragecomps.so mozStorageModule.o -Wl,-R/usr/pkg/lib/firefox2 -L/usr/pkg/xorg/lib -Wl,-R/usr/pkg/xorg/lib -L/usr/pkg/lib -Wl,-R/usr/pkg/lib -L/usr/lib -Wl,-R/usr/lib -Wl,–whole-archive ../../dist/lib/libstorage_s.a ../../dist/lib/libsqlite3_s.a -Wl,–no-whole-archive -L../../dist/bin -L../../dist/lib -L../../dist/bin -lxpcom -lxpcom_core -L../../dist/bin -L../../dist/lib -lplds4 -lplc4 -lnspr4 -L/usr/pkg/xorg/lib -L/usr/pkg/lib -L/usr/lib -pthread -L../../dist/bin -lmozjs -Wl,-Bsymbolic -lm
    ../../dist/lib/libsqlite3_s.a(os_unix.o)(.text+0x124): In function `testThreadLockingBehavior':
    : undefined reference to `pthread_create’
    ../../dist/lib/libsqlite3_s.a(os_unix.o)(.text+0x134): In function `testThreadLockingBehavior':
    : undefined reference to `pthread_create’
    make[3]: *** [libstoragecomps.so] Error 1
    make[3]: Leaving directory `/usr/obj/pkgsrc/www/firefox2/work/mozilla/storage/build’
    make[2]: *** [libs] Error 2
    make[2]: Leaving directory `/usr/obj/pkgsrc/www/firefox2/work/mozilla/storage’
    make[1]: *** [tier_9] Error 2
    make[1]: Leaving directory `/usr/obj/pkgsrc/www/firefox2/work/mozilla’
    gmake: *** [default] Error 2
    *** Error code 2

    Stop.
    bmake: stopped in /usr/pkgsrc/www/firefox2
    *** Error code 1

    Stop.
    bmake: stopped in /usr/pkgsrc/www/firefox2
    Real: 3918.39s User: 674.68s System: 236.13s Percent: 23% Cmd: ALLOW_VULNERABLE_PACKAGES=YES bmake install

    This problem occour since weeks on www/firefox too, it seems our dfly/pkgsrc hero (Joerg) need to fix this kind of stuff. It’s said this problem of pthread is common because nbsd use a totally different threading than dfly.

    Have a nice day and thanks for the pkgsrc work,
    timofonic

  3. ja'far says:

    This is still broken; I’m getting the same build error with a pkgsrc updated yesterday, building on HEAD from about a week ago. Should I submit a bug report?

Respond

Comments

Comments