version:Please provide at least FreeBSD version and output log from build. Have you tried to debug that .core file?
make
), although I'm not that good with gdb
:[New LWP 100340]
warning: Unexpected size of section `.reg-xstate/100340' in core file.
Core was generated by `/usr/local/bin/gdk-pixbuf-query-loaders --update-cache'.
Program terminated with signal SIGSEGV, Segmentation fault.
Invalid permissions for mapped object.
warning: Unexpected size of section `.reg-xstate/100340' in core file.
#0 0x00000008016a1c88 in ?? ()
Making all in demos
gmake[4]: Entering directory '/usr/ports/x11-toolkits/gtk20/work/gtk+-2.24.33/demos'
/usr/local/bin/gdk-pixbuf-csource --raw --build-list \
apple_red ./apple-red.png \
gnome_foot ./gnome-foot.png \
> test-inline-pixbufs.h \
|| (rm -f test-inline-pixbufs.h && false)
failed to load "./apple-red.png": Couldn’t recognize the image file format for file “./apple-red.pngâ€
gmake[4]: *** [Makefile:1044: test-inline-pixbufs.h] Error 1
gmake[4]: Leaving directory '/usr/ports/x11-toolkits/gtk20/work/gtk+-2.24.33/demos'
gmake[3]: *** [Makefile:730: all-recursive] Error 1
gmake[3]: Leaving directory '/usr/ports/x11-toolkits/gtk20/work/gtk+-2.24.33'
gmake[2]: *** [Makefile:622: all] Error 2
gmake[2]: Leaving directory '/usr/ports/x11-toolkits/gtk20/work/gtk+-2.24.33'
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1
Stop.
make[1]: stopped in /usr/ports/x11-toolkits/gtk20
*** Error code 1
Stop.
make: stopped in /usr/ports/x11-toolkits/gtk20
So looks like glib2 have to be "fixed" (patched), and only then rebuilt. But later in this thread they state that the patch was removed in revision r91990 . I would consider patching glib2 source, rebuild it and then try to rebuild gdk-pixbuf2. Or maybe hack some solution around - "fixing" apple-red.png or disable part of compilation causing the error if possible (they were mentioning demos).
Because error message is the same, and I believe a lot of open-source libraries bring same problems to different oses.3301 why are you referring to MacPorts? That ports tree has nothing to do with FreeBSD.
That's usually set in the BIOS.How to make NUM LOCK default ON on all new ttys?
I'm not so sure, as far as I remember, NUM is ON in BIOS, and it was ON in old sc terminal driver.That's usually set in the BIOS.
Just checked. NUM is ON after BIOS work, it is still ON during FreeBSD loader menu and becomes OFF only when vt driver starts (or somewgere near that point). It is annoying for me. Can't imaging situation when I turn it OFF having a working 102-keys keyboard. May be there should be (already is) some tunable to change it?That's usually set in the BIOS.