Anytime color highlighted mode for CMAKE

2013-07-06 Thread RyōTa SimaMoto
# Anytime color highlighted mode for CMAKE

Hi,

On usual terminal including ttyvN, if you add USE_GMAKE=yes on Mk/Uses/cmake.mk,
'cmake' gave colored output.  Since USES+=gmake is recommended, what way is
provided for custom setting to enable 'gmake' on USES macro when other certain
function is invoked?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


portaudit: Wrong vulnerability information for devel/dbus

2013-06-13 Thread RyōTa SimaMoto
Hi,

portaudit rejects the latest version (1.6.12) of devel/dbus
because acceptable version is set too higher (1.16.12) than it.

http://portaudit.FreeBSD.org/4e9e410b-d462-11e2-8d57-080027019be0.html
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: TEX_DEFAULT problem

2013-05-11 Thread RyōTa SimaMoto
Hi,

Please resolve %%TEXMFDIR%% of devel/tex-kpathsea/pkg-plist
that could be once unfolded with definition at Mk/bsd.tex.mk
which you unloaded.  I have no idea where TEXMFDIR?=share/texmf
should be suggested and processed in the PLIST_SUB variable list
when USE_TEX macro is unavailable.


2013/5/10, Hiroki Sato h...@freebsd.org:

...snip...
  I already fixed this in r317773.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


multimedia/gtk-youtube-viewer requires perl-5.16.x

2013-03-18 Thread RyōTa SimaMoto
# multimedia/gtk-youtube-viewer requires perl-5.16.x

Hi,

Since updating to 3.0.7, youtube-viewer (CLI) cannot run with
perl-5.14.x.  Meanwhile
gtk-youtube-viewer (GUI) works well for viewing videos by specifing ID
or from result
of searching with some terms yet on
GTK+-2.24.17/perl-threaded-5.14.2_1. (I do not know
about other functions).

Here is a snippet of error messagge from the command-line tool:
| $ youtube-viewer
| Perl v5.16.0 required--this is only v5.14.2, stopped at
/usr/local/bin/youtube-viewer line 106.
| BEGIN failed--compilation aborted at /usr/local/bin/youtube-viewer line 106.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


extconf.rb always fails at databases/rrdtool with CC=clang in /etc/make.conf

2012-11-09 Thread RyōTa SimaMoto
Hi,

Selecting RUBY_MODULE option for databases/rrdtool, and if you use
'clang' as the default compiler
by setting CC=clang at /etc/make.conf, this port would stop with the
following error message,
and any environmental setting like as USE_GCC=any could not affect.

gmake[4]: Leaving directory
`/usr/ports/databases/rrdtool/work/rrdtool-1.4.7/bindings/perl-shared'
cd ruby  /usr/local/bin/ruby extconf.rb  gmake EPREFIX=/usr/local
sitedir=/usr/local/lib/ruby RUBYARCHDIR=
checking for rrd_create() in -lrrd... yes
creating Makefile
gmake[4]: Entering directory
`/usr/ports/databases/rrdtool/work/rrdtool-1.4.7/bindings/ruby'
linking shared-object RRD.so
clang: warning: argument unused during compilation:
'-rpath=/usr/lib:/usr/local/lib'
clang: warning: argument unused during compilation:
'-rpath=/usr/lib:/usr/local/lib'
/usr/local/lib: file not recognized: File format not recognized
clang: error: linker command failed with exit code 1 (use -v to see invocation)
gmake[4]: *** [RRD.so] Error 1
gmake[4]: Leaving directory
`/usr/ports/databases/rrdtool/work/rrdtool-1.4.7/bindings/ruby'
gmake[3]: *** [ruby] Error 2
..snipped..

Here is excerpt from my /etc/make.conf:
  CC=clang
  CXX=clang++
  CPP=clang-cpp
  RUBY_DEFAULT_VER=1.9
  PERL_VERSION=5.14.2

Port's switches for running make (WITH_GCC=4.6 and WITH_GCC=any) are
ignored when the ruby
binding module creates Makefile from extconf.rb, then it always
invokes clang, and note
that CC=clang happens at perl module Makefile from Makefile.PL too.

Is there a way to get a good relationship between clang and ruby
extconf.rb?  Or can I
have exact option for completely masking CC= and CXX= settings in
/etc/make.conf?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: extconf.rb always fails at databases/rrdtool with CC=clang in /etc/make.conf

2012-11-09 Thread RyōTa SimaMoto
I am sorry I made misunderstanding to this issue.

Once CC= is set when ruby is built, it seems that ruby
remembers this in lib/ruby/1.9/i386-freebsd9/rbconfig.rb
file.  That is why generated Makefile from extconf.rb
always invokes the same compiler even if environmental
parameter is changed to other settings in /etc/make.conf
later.


2012/11/10, RyōTa SimaMoto liangtai...@gmail.com:
 Hi,

 Selecting RUBY_MODULE option for databases/rrdtool, and if you use
 'clang' as the default compiler
 by setting CC=clang at /etc/make.conf, this port would stop with the
 following error message,
 and any environmental setting like as USE_GCC=any could not affect.

 gmake[4]: Leaving directory
 `/usr/ports/databases/rrdtool/work/rrdtool-1.4.7/bindings/perl-shared'
 cd ruby  /usr/local/bin/ruby extconf.rb  gmake EPREFIX=/usr/local
 sitedir=/usr/local/lib/ruby RUBYARCHDIR=
 checking for rrd_create() in -lrrd... yes
 creating Makefile
 gmake[4]: Entering directory
 `/usr/ports/databases/rrdtool/work/rrdtool-1.4.7/bindings/ruby'
 linking shared-object RRD.so
 clang: warning: argument unused during compilation:
 '-rpath=/usr/lib:/usr/local/lib'
 clang: warning: argument unused during compilation:
 '-rpath=/usr/lib:/usr/local/lib'
 /usr/local/lib: file not recognized: File format not recognized
 clang: error: linker command failed with exit code 1 (use -v to see
 invocation)
 gmake[4]: *** [RRD.so] Error 1
 gmake[4]: Leaving directory
 `/usr/ports/databases/rrdtool/work/rrdtool-1.4.7/bindings/ruby'
 gmake[3]: *** [ruby] Error 2
 ..snipped..

 Here is excerpt from my /etc/make.conf:
   CC=clang
   CXX=clang++
   CPP=clang-cpp
   RUBY_DEFAULT_VER=1.9
   PERL_VERSION=5.14.2

 Port's switches for running make (WITH_GCC=4.6 and WITH_GCC=any) are
 ignored when the ruby
 binding module creates Makefile from extconf.rb, then it always
 invokes clang, and note
 that CC=clang happens at perl module Makefile from Makefile.PL too.

 Is there a way to get a good relationship between clang and ruby
 extconf.rb?  Or can I
 have exact option for completely masking CC= and CXX= settings in
 /etc/make.conf?

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

Re: ffmpeg1

2012-10-20 Thread RyōTa SimaMoto
Hi,

I have the same problem.  In short, Setting
CONFIGURE_ARGS+= LIBS=-lm at the audio/fdk-aac/Makefile
may resolve it.

It is strange that libfdk-aac did not link against libm.so
though it uses some arithmetic functions from math.h.  The
config.log of multimedia/ffmpeg1 shows that:
/usr/local/lib/libfdk-aac.so: undefined reference to `floor'
/usr/local/lib/libfdk-aac.so: undefined reference to `ceil'
/usr/local/lib/libfdk-aac.so: undefined reference to `tan'
/usr/local/lib/libfdk-aac.so: undefined reference to `log'
/usr/local/lib/libfdk-aac.so: undefined reference to `atan'
/usr/local/lib/libfdk-aac.so: undefined reference to `acos'
/usr/local/lib/libfdk-aac.so: undefined reference to `exp'
/usr/local/lib/libfdk-aac.so: undefined reference to `sin'
/usr/local/lib/libfdk-aac.so: undefined reference to `pow'
/usr/local/lib/libfdk-aac.so: undefined reference to `atan2'
/usr/local/lib/libfdk-aac.so: undefined reference to `cos'
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Then the linkage list of this library was:
$ ldd /usr/local/lib/libfdk-aac.so.0
/usr/local/lib/libfdk-aac.so.0:
libc.so.7 = /lib/libc.so.7 (0x2806e000)

It succeeds to test of compilation a new libfdk-aac.so that links
against both of libc and libm, with a short program from the
configure script of ffmpeg1 and its way:
ffconf.c:
   extern int aacEncOpen();
   int main(void){ aacEncOpen(); }
clang -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -O2 \
  -pipe -fno-strict-aliasing -I/usr/local/include/vorbis -I/usr/local/include \
  -std=c99 -fomit-frame-pointer -I/usr/local/include -I/usr/local/include \
  -I/usr/local/include/p11-kit-1 -I/usr/local/include/fribidi \
  -I/usr/local/include/freetype2 -I/usr/local/include -c -o ffconf.o ffconf.c
clang -L/usr/local/lib -Wl,--as-needed -o ffconf ffconf.o -lfdk-aac -lfaac \
  -lcelt0 -lcelt0 -lbluray -L/usr/local/lib -lass -laacplus -L/usr/local/lib \
  -lgnutls -L/usr/local/lib -L/usr/lib -lfontconfig -lva -lm -lbz2 -lz -pthread


2012/10/16, ajtiM lum...@gmail.com:
 Hi!

 I tried to update VLC on FreeBSD 9.1 RC2 and it need ffmpeg1 which I have a

 problem to build:

 Cleaning for ffmpeg1-1.0
 ===  License GPLv3 LGPL3 accepted by the user
 ===  Found saved configuration for ffmpeg1-1.0
 ===   ffmpeg1-1.0 depends on file: /usr/local/sbin/pkg - found
 ===  Extracting for ffmpeg1-1.0
 = SHA256 Checksum OK for ffmpeg-1.0.tar.bz2.
 ===   ffmpeg1-1.0 depends on file: /usr/local/bin/perl5.16.0 - found
 ===  Patching for ffmpeg1-1.0
 ===   ffmpeg1-1.0 depends on file: /usr/local/bin/perl5.16.0 - found
 ===  Applying FreeBSD patches for ffmpeg1-1.0
 ===   ffmpeg1-1.0 depends on executable: yasm - found
 ===   ffmpeg1-1.0 depends on file: /usr/local/bin/as - found
 ===   ffmpeg1-1.0 depends on executable: texi2html - found
 ===   ffmpeg1-1.0 depends on file: /usr/local/include/frei0r.h - found
 ===   ffmpeg1-1.0 depends on file: /usr/local/include/vdpau/vdpau.h -
 found
 ===   ffmpeg1-1.0 depends on executable: gmake - found
 ===   ffmpeg1-1.0 depends on executable: pkgconf - found
 ===   ffmpeg1-1.0 depends on file: /usr/local/libdata/pkgconfig/x11.pc -
 found
 ===   ffmpeg1-1.0 depends on file: /usr/local/libdata/pkgconfig/xext.pc -
 found
 ===   ffmpeg1-1.0 depends on file: /usr/local/libdata/pkgconfig/xfixes.pc -
 found
 ===   ffmpeg1-1.0 depends on file: /usr/local/bin/sdl-config - found
 ===   ffmpeg1-1.0 depends on file: /usr/local/bin/perl5.16.0 - found
 ===   ffmpeg1-1.0 depends on shared library: aacplus - found
 ===   ffmpeg1-1.0 depends on shared library: opencore-amrnb - found
 ===   ffmpeg1-1.0 depends on shared library: opencore-amrwb - found
 ===   ffmpeg1-1.0 depends on shared library: faac - found
 ===   ffmpeg1-1.0 depends on shared library: fdk-aac - found
 ===   ffmpeg1-1.0 depends on shared library: fontconfig - found
 ===   ffmpeg1-1.0 depends on shared library: freetype - found
 ===   ffmpeg1-1.0 depends on shared library: gnutls - found
 ===   ffmpeg1-1.0 depends on shared library: gsm - found
 ===   ffmpeg1-1.0 depends on shared library: mp3lame - found
 ===   ffmpeg1-1.0 depends on shared library: openal - found
 ===   ffmpeg1-1.0 depends on shared library: opencv_imgproc - found
 ===   ffmpeg1-1.0 depends on shared library: openjpeg - found
 ===   ffmpeg1-1.0 depends on shared library: rtmp - found
 ===   ffmpeg1-1.0 depends on shared library: schroedinger-1.0.11 - found
 ===   ffmpeg1-1.0 depends on shared library: speex - found
 ===   ffmpeg1-1.0 depends on shared library: theora - found
 ===   ffmpeg1-1.0 depends on shared library: va - found
 ===   ffmpeg1-1.0 depends on shared library: vo-aacenc - found
 ===   ffmpeg1-1.0 depends on shared library: vo-amrwbenc - found
 ===   ffmpeg1-1.0 depends on shared library: vorbisenc - found
 ===   ffmpeg1-1.0 depends on shared library: vpx - found
 ===   ffmpeg1-1.0 depends on shared library: x264 - found
 ===   ffmpeg1-1.0 depends on shared library: xvidcore - found
 ===   

Re: Any common policy against conflicting choice in Makefile OPTIONS?

2012-02-06 Thread RyōTa SimaMoto
Thank you for all!

I sent a PR of upgrading qmmp as
http://www.freebsd.org/cgi/query-pr.cgi?pr=164832

Perhaps the ports system may be not very strong to let
users select options easily without any complicated
interface.  I desided to maintain the current options,
and give up the plan to display twin options.  For
ffmpeg-devel users, a short message about how to use
the installed version is added by an IGNORE procedure.

-=-=-=-=-=
SimaMoto,RyoTa liangtai...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Any common policy against conflicting choice in Makefile OPTIONS?

2012-02-05 Thread RyōTa SimaMoto
Hi, I'm a port maintainer for multimedia/qmmp, and some ports.
Before upgrading QMMP port, may I ask what is the common policy how to
offer Makefile OPTIONS containing a certain contradictory pair?

Actually the latest version of QMMP supports several versions of ffmpeg,
including 0.7.11, 0.9, 0.9.1, and 2012.01.22 that I tested to verify, so it
allows user to choose one of multimedia/ffmpeg or multimedia/ffmpeg-devel.
As you know you should not select both of them, otherwise they may conflict
with each other.  I plan to provide an entry for each of them.
  | 
  | [*] FFMPEGSupport to playback by FFMPEG
  | [ ] FFMPEG_DEVEL  Support to playback by FFMPEG-devel
  | 
Then how should the Makefile proceed after the user's choice?

When the user did not install any of them yet, it's easy: The installation
would obey the user's order except when occationally both of them are
enabled that results to fail with an alert message.  On the other hand, if
one of them are already installed, Makefile would know which one is
installed using 'exists(${LOCALBASE}/include/libavcodec/vda.h)' command.
So, in fact, there is no question that which version the user want to use.

The smartest way would be that provides a single entry which corresponds
to the existing version and hides the other entry that should not be
choosen.  Unfortunately, the value LOCALBASE is not defined until
bsd.port.options.mk macro is loaded, that means we don't have any proper
steps to determine what version is already installed when the Makefile
construct the OPTIONS set.  So we have no other way than to let the option
dialog always show both entries including quite wrong option.

Then if the user selects the other one that might conflict with the
installed version, there are six possible courses I assume.
 0x000.  Quit the session with alert message instructing user to retry
 'make config' to choose the already installed one that Makefile
 knows.
 0x001.  Dare to go through and expect that the depending port deals with
 the conflicting issue.
 0x002.  Use the installed version and omit the choice implicitly.
 0x004.  Warn with short pause, then use the installed version and omit
 the choice.
 0x010.  Store options into /var/db/ports/* as are that the user selects.
 0x020.  Store options into /var/db/ports/* with correction as actually
 working.  (If option variables are allowed to be changed at
 testing stage.)

Is there any recommended policy?  If so, what way or a set of ways should I
choose?


-=-=-=-=-=
SimaMoto,RyoTa liangtai...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Help needed to test before upgrading (was: Please help for joining my port for QMMP)

2011-04-04 Thread RyōTa SimaMoto
Dear ports developers,

Thank you and Martin for letting the port of QMMP stage at the
mainstream.  But I still need your help to maintain this port,
especially to test each function.

2011/4/4 Raphael Kubo da Costa kub...@gmail.com:
 Is there any reason why 0.5.0 is not there yet?

I'm sorry that I didn't send a report to upgrade the port yet.
Installation finished successfully, but I can't tell why some
new features don't work.  Perhaps my low spec PC and brain
might refuse proper testing:(  My port for v0.5.0 is here:
http://gist.github.com/472287

With v0.5.0 release, these new options in plugins are added:
  # wildmidi: SMF docoding
  # oss4: output through ${PORTSDIR}/audio/oss
  # udisks: automatic removable-media detector using Qt-DBus
  # crossfade: effect using pure Qt libraries
  # extra stereo: effect using pure Qt libraries
  # gme: decode several game music files through
${PORTSDIR}/audio/libgme

Only the pulseaudio plugin works to get output on v0.5.0.
  % % % % 0.4.5 : 0.5.0
  # pulse: good : good
  # oss:   fine : failed
  # oss4:  n/a  : failed
  # jack:  ?: ?
// I don't know how to activate jack audio backend.

* I can't hear SMF with WildMIDI decoder plugin as well as its
  bundled genuine executable 'wildmidi', though timidity++
  works well with guspat or eawpat.  Let my port usable please!
  http://gist.github.com/700309
* To hear CD-DA disk, always it needs to add cdda:///dev/acd0
  on the URI opener dialog, even though udisks plugin is
  activated.  Are another settings required for Qt-DBus? Or
  my old CD-drive might disturb again regular usage. (The
  /bin/dd command already had been unusable for ripping.)


-=-=-=-=-=
SimaMoto,RyōTa liangtai...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Update graphics/gimp-help issue

2010-04-09 Thread RyōTa SimaMoto
Hi,

I'm new to this list.

I'm a member of the GIMP Help Documentation Team.
On early October of last year, we released the new version
product gimp-help-2.6.0-html, so I edited its port(s).

Since this version, we had been providing packages in
ready-to-install packages separated in translated languages.
Source tarball doesn't exist.  On the contrary,
Older version was a source tree of XML files.

I wrote new ports in two approach for construction:
1. Update only on the graphics/gimp-help.  User can select
languages by the option function.  It is simple, but this way
causes its package file to become very bigger than the older
version if all languages are included because shared image
files are also copied in different paths of each language.
about 347MB.
2. Separate the port by languages.  In this way, 13 new ports
will be added.  graphics/gimp-help will be changed to the
meta-port, misc/gimp-help-en as the main port, and other
ports as its slaves.

Which style is more preferable?  Or you have another ways?

In the second approach, I don't know how to create 'diff'
file for updating these port.  The first one is ready to send-pr.

-=-=-=-=-=
SimaMoto,RyōTa liangtai...@gmail.com
http://code.google.com/p/gimp-doc-ja/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org