Re: 9.3 to 10.2 migration, determining if clang is used

2015-10-13 Thread Brooks Davis
On Tue, Oct 13, 2015 at 11:13:11AM -0700, Patrick Powell wrote:
> I just started doing a 9.3 to 10.2 migration of a bunch of applications 
> and discovered that some of the options used
> to generate the applications were slightly different.   I just know that 
> this has been covered before,  but I could not
> find a definitive method or set of methods to use to determine if the 
> old GCC compiler or the new CLANG compiler
> is being used.   Could the ports wizards (and/or autoconf experts) help 
> me a bit?
>
> (Aside:  the clang compiler diagnostics and warnings are very thorough 
> and quite clear.  Nicely done, especially
> the addition of the information about the flag to turn this warning 
> off.  I also like the pragmas to
> control warnings and the push/pop pragma facility.  This may have been 
> in the GCC compiler but I missed it.)
> 
> 1. If the application is to be generated via the PORT infrastructure,  
> what do you
>  put in the port Makefile to determine if CLANG (10.2) or GCC (9.3) 
> is being used?
> 
> 
> Something like below.  Note: the examples below are a bit contrived, 
> but the idea is to set
> some MAKE variable to different values depending on CLANG or GCC in use.
> 
> .if defined(CC_IS_CLANG)
> MYFLAGS+= -Wall -Werror -Wno-error=unused
> .else
> .if defined(CC_IS_GCC)
> MYFLAGS+= -Wall -Werror -Wno-unused
> .endif
> .endif

For ports, I think you are looking for USES=compiler:features (see
ports/Mk/Uses/compiler.mk).  I don't know the answer for autoconf.

-- Brooks


signature.asc
Description: PGP signature


9.3 to 10.2 migration, determining if clang is used

2015-10-13 Thread Patrick Powell
I just started doing a 9.3 to 10.2 migration of a bunch of applications 
and discovered that some of the options used
to generate the applications were slightly different.   I just know that 
this has been covered before,  but I could not
find a definitive method or set of methods to use to determine if the 
old GCC compiler or the new CLANG compiler
is being used.   Could the ports wizards (and/or autoconf experts) help 
me a bit?


(Aside:  the clang compiler diagnostics and warnings are very thorough 
and quite clear.  Nicely done, especially
the addition of the information about the flag to turn this warning 
off.  I also like the pragmas to
control warnings and the push/pop pragma facility.  This may have been 
in the GCC compiler but I missed it.)


1. If the application is to be generated via the PORT infrastructure,  
what do you
put in the port Makefile to determine if CLANG (10.2) or GCC (9.3) 
is being used?



   Something like below.  Note: the examples below are a bit contrived, 
but the idea is to set

   some MAKE variable to different values depending on CLANG or GCC in use.

   .if defined(CC_IS_CLANG)
   MYFLAGS+= -Wall -Werror -Wno-error=unused
   .else
   .if defined(CC_IS_GCC)
   MYFLAGS+= -Wall -Werror -Wno-unused
   .endif
   .endif



2.  A simple test for configure that checks the for the CLANG compiler:

# Check for programs
AC_PROG_CC
# we may need to add this to the configure macro set?
AC_PROG_CLANG
if test "$ac_cv_using_clang" = yes; then
  CFLAGS="$CFLAGS -Wall -Werror -Wno-error=unused"
   else
 if test "$ac_cv_c_compiler_gnu" = yes; then
   CFLAGS="$CFLAGS -Wall -Werror -Wno-unused"
fi;
   fi;

   It could even be something simpler if the AC_PROG_CC configure macro 
sets, for example,
   the $ac_gcc_version shell variable with a value that indicates CLANG 
in use then the following

   would be useful:


   if test "$ac_gcc_version" -gt 999  ; then
  ...
   fi;





--
Patrick Powell Astart Technologies
papow...@astart.com1530 Jamacha Rd, Suite X
Network and System San Diego, CA 92019
  Consulting   858-874-6543 FAX 858-751-2435
Web: www.astart.com

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Firefox + SeaMonkey (gecko browsers) instant crash on some web pages

2015-10-13 Thread Miroslav Lachman

Steve Wills wrote on 10/13/2015 17:16:

Hi,

On 10/13/2015 09:21, Miroslav Lachman wrote:


Hi Steve,

A "skia" fixed crashes on mapy.cz and seznam.cz but from this time I got
random crashes of Firefox and Seamonkey (both with "skia"). Until this
change Seamonkey was happily runnig for a few weeks (system uptime 20
days). I have more than 5 crashes today.
Is there a way to track this issue or some other way to fix mapy.cz and
seznam.cz crashes without bringing this instability?


I guess we need a debug version of firefox built and a copy of the core
dump from the crash. I was going to do that but haven't made time.

In the mean time, you might consider having two profiles, one where you
use skia for mapy.cz and seznam.cz and the other one default. Not ideal,
but as a temporary workaround that lets you use both sites until the
issue is solved.

Since SeaMonkey hasn't been updated, I'm wonder if the issue existed in
the older version of Firefox too.


Yes, this problem exists in old Firefox too. My desktop was not updated 
for more than 6 month, so I have


SeaMonkey 2.32:
Mozilla/5.0 (X11; FreeBSD amd64; rv:35.0) Gecko/20100101 Firefox/35.0 
SeaMonkey/2.32 Lightning/3.7


Firefox 35:
Mozilla/5.0 (X11; FreeBSD amd64; rv:35.0) Gecko/20100101 Firefox/35.0

Both crashed on mapy.cz and seznam.cz

I tried newer version in freshly installed VirtualBox VM with Firefox 40 
and 41. Results are the same.


I will try debug version in the next few days as time permits.

Thank you for your help.

Miroslav Lachman
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Firefox + SeaMonkey (gecko browsers) instant crash on some web pages

2015-10-13 Thread Steve Wills
Hi,

On 10/13/2015 09:21, Miroslav Lachman wrote:
> 
> Hi Steve,
> 
> A "skia" fixed crashes on mapy.cz and seznam.cz but from this time I got
> random crashes of Firefox and Seamonkey (both with "skia"). Until this
> change Seamonkey was happily runnig for a few weeks (system uptime 20
> days). I have more than 5 crashes today.
> Is there a way to track this issue or some other way to fix mapy.cz and
> seznam.cz crashes without bringing this instability?

I guess we need a debug version of firefox built and a copy of the core
dump from the crash. I was going to do that but haven't made time.

In the mean time, you might consider having two profiles, one where you
use skia for mapy.cz and seznam.cz and the other one default. Not ideal,
but as a temporary workaround that lets you use both sites until the
issue is solved.

Since SeaMonkey hasn't been updated, I'm wonder if the issue existed in
the older version of Firefox too.

Steve
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Firefox + SeaMonkey (gecko browsers) instant crash on some web pages

2015-10-13 Thread Miroslav Lachman

Steve Wills wrote on 10/09/2015 13:57:

Hi,

On 10/09/2015 03:38, Miroslav Lachman wrote:

Steve Wills wrote on 10/08/2015 21:55:

Just to test, try setting gfx.canvas.azure.backends and
gfx.content.azure.backends to skia in about:config and see if it still
crashes.


Hi Steve,

I changed both from cairo to skia. Firefox crashed again on www.mapy.cz
but on next start www.mapy.cz and www.seznam.cz works normally. So this
can be a workaround.

When I entered www.mapy.cz this messages were printed on console but FF
didn't crash



Yes, you have to restart for it to take effect. BTW, I think only
changing gfx.canvas.azure.backends is necessary,
gfx.content.azure.backends can remain at default setting.



firefox


(process:8936): GLib-CRITICAL **: g_slice_set_config: assertion
'sys_page_size == 0' failed
Fontconfig warning: "local.conf", line 1093: saw number, expected matrix
libGL error: Calling driver entry point failed
libGL error: reverting to software direct rendering
libGL error: failed to load driver: vboxvideo
ATTENTION: default value of option force_s3tc_enable overridden by
environment.


Yeah, GL stuff isn't going to get hardware acceleration in vbox, no
surprise there. Should be fine though, I think.


Can I use "skia" or does it have some negative impact? (I don't know
what these two settings mean)


The only negative impact could be slower performance in some cases. But
it does provide better performance in other cases, so it depends. And of
course, not crashing is a benefit. :)


Hi Steve,

A "skia" fixed crashes on mapy.cz and seznam.cz but from this time I got 
random crashes of Firefox and Seamonkey (both with "skia"). Until this 
change Seamonkey was happily runnig for a few weeks (system uptime 20 
days). I have more than 5 crashes today.
Is there a way to track this issue or some other way to fix mapy.cz and 
seznam.cz crashes without bringing this instability?


Miroslav Lachman

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


INDEX now builds successfully on 9.x

2015-10-13 Thread Ports Index build

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


FreeBSD ports you maintain which are out of date

2015-10-13 Thread portscout
Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
science/gramps  | 3.4.9   | 4.2.1
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Thanks.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


INDEX build failed for 9.x

2015-10-13 Thread Ports Index build
INDEX build failed with errors:
Generating INDEX-9 - please wait..--- describe.accessibility ---
--- describe.arabic ---
--- describe.archivers ---
--- describe.astro ---
--- describe.audio ---
--- describe.benchmarks ---
--- describe.biology ---
--- describe.cad ---
--- describe.chinese ---
--- describe.comms ---
--- describe.converters ---
--- describe.databases ---
--- describe.deskutils ---
--- describe.devel ---
--- describe.dns ---
--- describe.editors ---
--- describe.emulators ---
--- describe.finance ---
--- describe.french ---
--- describe.ftp ---
[...]
--- describe.print ---
--- describe.russian ---
--- describe.science ---
--- describe.security ---
--- describe.shells ---
--- describe.sysutils ---
--- describe.textproc ---
--- describe.ukrainian ---
--- describe.vietnamese ---
--- describe.www ---
--- describe.x11 ---
--- describe.x11-clocks ---
--- describe.x11-drivers ---
--- describe.x11-fm ---
--- describe.x11-fonts ---
--- describe.x11-servers ---
--- describe.x11-themes ---
--- describe.x11-toolkits ---
--- describe.x11-wm ---
 Done.
make_index: /home/indexbuild/tindex/ports/x11-servers/xephyr: no entry for 
graphics/libdrm

Committers on the hook:
 kwm marino mat 

Most recent SVN update was:
Updating '.':
Usysutils/tmux/pkg-descr
Dx11/nvidia-driver-173
Ux11/Makefile
Uemulators/virtualbox-ose-additions/Makefile
U
emulators/virtualbox-ose/files/patch-src-VBox-Additions-x11-vboxmouse-Makefile.kmk
Dx11-drivers/xf86-video-ati-ums
Dx11-drivers/xf86-video-trident/files
Ux11-drivers/xf86-video-trident/Makefile
Ux11-drivers/xf86-video-trident/distinfo
Ux11-drivers/xf86-video-intel/Makefile
Ux11-drivers/xf86-video-scfb/Makefile
Ux11-drivers/xf86-video-apm/Makefile
Ux11-drivers/xf86-video-ark/Makefile
Ux11-drivers/xf86-video-ati/Makefile
Ux11-drivers/xf86-video-tseng/Makefile
Ux11-drivers/xf86-video-mach64/distinfo
Ux11-drivers/xf86-video-mach64/Makefile
Ux11-drivers/xf86-video-s3/Makefile
Ux11-drivers/xf86-input-joystick/Makefile
Ux11-drivers/xf86-input-acecad/Makefile
Ux11-drivers/xf86-input-keyboard/Makefile
Ux11-drivers/xf86-input-keyboard/distinfo
Ux11-drivers/xf86-video-rendition/files/patch-src_rendition.c
Ux11-drivers/xf86-video-rendition/files/patch-src_rendition.h
Ux11-drivers/xf86-video-rendition/Makefile
Ux11-drivers/xf86-video-r128/Makefile
Ux11-drivers/xf86-video-r128/distinfo
Ux11-drivers/xf86-video-vesa/Makefile
Ux11-drivers/xf86-video-vesa/distinfo
Ux11-drivers/xf86-input-wacom/Makefile
Ux11-drivers/xf86-video-mga/Makefile
Ax11-drivers/xf86-video-voodoo/files
Ax11-drivers/xf86-video-voodoo/files/patch-src_voodoo.h
Ux11-drivers/xf86-video-voodoo/Makefile
Dx11-drivers/xf86-video-chips/files
Ux11-drivers/xf86-video-chips/Makefile
Ux11-drivers/xf86-video-chips/distinfo
Ux11-drivers/xf86-video-cirrus/Makefile
Ux11-drivers/xf86-video-cirrus/distinfo
Ux11-drivers/xf86-video-glint/Makefile
Ux11-drivers/xf86-input-mutouch/Makefile
Ux11-drivers/Makefile
Ux11-drivers/xf86-input-mouse/Makefile
Ux11-drivers/xf86-video-neomagic/Makefile
Ux11-drivers/xf86-video-neomagic/distinfo
Ux11-drivers/xf86-video-s3virge/distinfo
Ux11-drivers/xf86-video-s3virge/Makefile
Ux11-drivers/xf86-video-nv/Makefile
Ux11-drivers/xf86-video-i740/Makefile
Ux11-drivers/xf86-video-i128/Makefile
Ux11-drivers/xf86-input-hyperpen/Makefile
Ax11-drivers/xf86-video-sunffb/files/patch-src_ffb__driver.c
Ux11-drivers/xf86-video-sunffb/Makefile
Ux11-drivers/xf86-input-vmmouse/pkg-plist
Ux11-drivers/xf86-input-vmmouse/Makefile
Ux11-drivers/xf86-input-vmmouse/distinfo
Ux11-drivers/xf86-video-fbdev/Makefile
Dx11-drivers/xf86-video-siliconmotion/files
Ux11-drivers/xf86-video-siliconmotion/Makefile
Ux11-drivers/xf86-video-siliconmotion/distinfo
Ux11-drivers/xf86-input-elographics/Makefile
Ux11-drivers/xf86-input-egalax/Makefile
Ux11-drivers/xf86-input-void/Makefile
Ux11-drivers/xf86-input-void/distinfo
Ux11-drivers/xf86-input-fpit/Makefile
Ux11-drivers/xf86-video-dummy/Makefile
Ux11-drivers/xf86-video-sis/distinfo
Ux11-drivers/xf86-video-sis/files/patch-src_sis__driver.c
Ux11-drivers/xf86-video-sis/Makefile
Ux11-drivers/xf86-input-penmount/Makefile
Ux11-drivers/xf86-video-openchrome/Makefile
Ux11-drivers/xf86-input-evdev/Makefile
Ux11-drivers/xf86-video-tdfx/Makefile
Ux11-drivers/xf86-video-savage/Makefile
Ux11-drivers/xf86-video-savage/distinfo
Ux11-drivers/xf86-input-synaptics/Makefile
Dmath/plplot/files/patch-cmake_modules_pkg-config.cmake
Dmath/plplot/files/patch-cmake_modules_linuxvga.cmake
Umath/plplot/pkg-plist
Umath/plplot/Makefile
Umath/plplot/distinfo
Umath/plplot-ada/Makefile
Ux11-fonts/libXfont/distinfo
Ux11-fonts/libXfont/Makefile
Ux11-fonts/fontsproto/Makefile
Ux11-fonts/fontsproto/di

Re: math/ess, deprecate or change maintainership

2015-10-13 Thread Kubilay Kocak
On 13/10/2015 5:37 PM, Christopher J. Ruwe wrote:
> Hi,
> 
> Emacs Speacks Statistics 15.09, which I maintain as math/ess, has been
> released in the end of September. 
> 
> However, as I outlined in
> http://lists.freebsd.org/pipermail/freebsd-ports/2014-November/096678.html,
> I have severe doubts that packages for emacs modes generate any value.
> 
> I do not plan to update math/ess and advocate for deprecating that
> port. Should anybody need math/ess in ports, I would like to hand over
> maintainership to said anybody willing to step in.
> 
> Cheers,
> 

Hi Christopher,

Please feel free to submit a bugzilla issue with title:

math/ess: Reset maintainership

Also include a patch updating the MAINTAINER line to po...@freebsd.org

And finally, THANK YOU for contributing to FreeBSD, we hope to see you
back here soon :)

./koobs
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"