Geert Hendrickx | 1 Jun 2005 01:06
Picon

Re: CFLAGS in mk.conf

On Tue, May 31, 2005 at 05:02:17PM -0400, Todd Vierling wrote:
> On Mon, 30 May 2005, Geert Hendrickx wrote:
> 
> > Another question: (how) can /etc/mk.conf CFLAGS be overriden from the
> > commandline?
> 
> Use the following snippet, if you want to parameterize your own CFLAGS
> fragment.
> 
> =====
> MY_CFLAGS?=	-Os -someotheroption
> CFLAGS+=	${MY_CFLAGS}
> =====
> 
> Then you can set the value of MY_CFLAGS in your environment or on the make
> command line.

Thanks!!  

GH

--

-- 
:wq

Todd Vierling | 1 Jun 2005 01:35
Gravatar

Re: python versions

On Tue, 31 May 2005, Simon J. Gerraty wrote:

> 1/ do I still need to build the -pth version of python to get threads?

No.  It's now on by default.

> 2/ is there some new trick needed to make packages use the installed
>    2p3 version?

It will no longer be recognized, so you are required to build a non-"-pth"
version for new python pkg builds.  Unfortunately this may also mean that
you'll have to rebuild any py-* libraries you have installed.

--

-- 
-- Todd Vierling <tv <at> duh.org> <tv <at> pobox.com> <todd <at> vierling.name>

Simon J. Gerraty | 1 Jun 2005 01:42

Re: python versions


On Tue, 31 May 2005 19:35:07 -0400 (Eastern Daylight Time), Todd Vierling write
s:
>On Tue, 31 May 2005, Simon J. Gerraty wrote:
>
>> 1/ do I still need to build the -pth version of python to get threads?
>
>No.  It's now on by default.

Thanks, then I'll go ahead and rebuild everything for 2.4

--sjg

Rob Bennett | 1 Jun 2005 13:50
Picon
Favicon

Problems with DIALOG in ramdisk-small

Hi everyone,
I'm stuggling to figure out what is going on here. 
I've compiled NetBSD 2.0.2 and also done DIALOG-0.6z 
which works nicely in my fully laden NetBSD box. (i.e.
the one I compiled it on)
However, when I copy the dialog file to a lightweight
cdrom-boot ramdisk version of 2.0.2 (basically a
bootfloppy) 
dialog gives me this error when I run it:
$ /bin/dialog
/bin/dialog: 1: Syntax error: "(" unexpected

By way of a comparision, back on my "normal" box I
get:
# /usr/pkg/bin/dialog

dialog version 0.3, by Savio Lam (lan836 <at> cs.cuhk.hk).
  patched to version 0.6c by Stuart Herber
(S.Herbert <at> shef.ac.uk)
  patched to version 0.6z by John Gatewood Ham
(zappaman <at> alphabox.buu.ac.th)
********

Am I missing something blindingly obvious about
compiling binaries and moving them between systems, or
is my environment in the cdrom boot not got enough of
"something" to allow dialog to run?  My guess is the 
latter, but none of the documentation about dialog
seems to mention what it might need.  

(Continue reading)

Hubert Feyrer | 1 Jun 2005 14:01
Picon
Favicon

Re: Problems with DIALOG in ramdisk-small

On Wed, 1 Jun 2005, Rob Bennett wrote:
> $ /bin/dialog
> /bin/dialog: 1: Syntax error: "(" unexpected

Missing /libexec/ld_elf.so?

  - Hubert

--

-- 
Genervt von Viren und von Viren versandten Spam-Mails?  -> www.NetBSD.de
Fed up from viruses & virus-originated spam mail?       -> www.NetBSD.org

Thomas Klausner | 1 Jun 2005 14:07
Picon

Re: Conversion of mplayer to options framework

On Tue, May 31, 2005 at 08:49:17PM +0000, Julio M. Merino Vidal wrote:
> the attached patch converts mplayer to the package options framework.
> More specifically, it gets rid of the MPLAYER_DISABLE_DRIVERS,
> MPLAYER_ENABLE_RUNTIME_CPU_DETECTION and MPLAYER_USE_MEDIALIB variables.
> (How do I mark them as deprecated?  mk/defaults/obsolete.mk does not
> seem the right place, as it is says "global vars".)

From mk/bsd.options.mk:
#       PKG_OPTIONS_LEGACY_VARS
#               This is a list of USE_VARIABLE:option pairs that
#               map legacy /etc/mk.conf variables to their option
#               counterparts.

Just add a PKG_OPTIONS_LEGACY_VARS line to the options.mk file.
It's also possible to add negated options this way, i.e.
PKG_OPTIONS_LEGACY_VARS+=	NO_FOO:-foo

> However, note that I've not added neither arts, nor esound, nor nas to
> the default options.  I'm not sure this is the way to go, but reduces
> the amount of dependencies by default.  A reason in favor is that we
> already have several packages that support options to enable these
> backends, and they are disabled by default.  The "bad" side is that
> binary packages won't have any of these audio output plugins compiled in
> (but we don't have binary packages in FTP yet, do we?  See below,
> anyway.)

I don't think you should change the default options. People
who don't want them have already adjusted...

> Any objections to this?  Any detail I should improve?
(Continue reading)

Julio M. Merino Vidal | 1 Jun 2005 17:00
Picon

Re: Conversion of mplayer to options framework

On Wed, 2005-06-01 at 14:07 +0200, Thomas Klausner wrote:
> On Tue, May 31, 2005 at 08:49:17PM +0000, Julio M. Merino Vidal wrote:
> > the attached patch converts mplayer to the package options framework.
> > More specifically, it gets rid of the MPLAYER_DISABLE_DRIVERS,
> > MPLAYER_ENABLE_RUNTIME_CPU_DETECTION and MPLAYER_USE_MEDIALIB variables.
> > (How do I mark them as deprecated?  mk/defaults/obsolete.mk does not
> > seem the right place, as it is says "global vars".)
> 
> From mk/bsd.options.mk:
> #       PKG_OPTIONS_LEGACY_VARS
> #               This is a list of USE_VARIABLE:option pairs that
> #               map legacy /etc/mk.conf variables to their option
> #               counterparts.
> 
> Just add a PKG_OPTIONS_LEGACY_VARS line to the options.mk file.
> It's also possible to add negated options this way, i.e.
> PKG_OPTIONS_LEGACY_VARS+=	NO_FOO:-foo

I've added:

.if ${MACHINE_ARCH} == "i386"
PKG_OPTIONS_LEGACY_VARS+= \
    MPLAYER_ENABLE_RUNTIME_CPU_DETECTION:mplayer-runtime-cpudetection
.endif

But it seems to do nothing.  At least, the corresponding option is not
added by default, although the variable is explicitly set to YES by
mk/defaults/mk.conf.

> > However, note that I've not added neither arts, nor esound, nor nas to
(Continue reading)

Thomas Klausner | 1 Jun 2005 15:05
Picon

Re: Conversion of mplayer to options framework

On Wed, Jun 01, 2005 at 03:00:46PM +0000, Julio M. Merino Vidal wrote:
> I've added:
> 
> .if ${MACHINE_ARCH} == "i386"
> PKG_OPTIONS_LEGACY_VARS+= \
>     MPLAYER_ENABLE_RUNTIME_CPU_DETECTION:mplayer-runtime-cpudetection
> .endif
> 
> But it seems to do nothing.  At least, the corresponding option is not
> added by default, although the variable is explicitly set to YES by
> mk/defaults/mk.conf.

Do you have bsd.prefs.mk included before the MACHINE_ARCH test?
Is your pkgsrc up-to-date?
I can't think of anything else. Look at e.g. audio/lame/options.mk
for a case where it works.

> > Option descriptions for all options (including the package-specific
> > ones) should be added to mk/defaults/option.descriptions.
> 
> Nice!  I wasn't aware of that file; it makes 'make show-options' output
> quite user-friendly :)

Yes :)
Now we only need all options described there....

Cheers,
 Thomas

(Continue reading)

Julio M. Merino Vidal | 1 Jun 2005 17:11
Picon

Reformatting faq.xml

Hi!

I'd like to do some changes in the FAQ section in the guide.  Basically,
group all existing questions in a "General questions" section and then
add another block with GNOME-related questions of interest (more
sections could follow).

But when going to do so, I found the xml file very hard to read,
specially due to the inconsistent indentation.  So I removed it from the
main tags (chapter and sections) and only left it for structures that
are worth noticing (lists).  (Indentation in Docbook files gets in the
way as a little change in the structure will require you to reindent the
whole document...)

Furthermore, it was incorrectly formatted in some cases.  For example,
there must be no space between an element and CDATA, as in '<para>some
text</para>', not '<para> some text </para>'.  Check this out:

http://mail-index.netbsd.org/www-changes/2005/05/06/0000.html

So before doing big changes to the content, I've reformatted the file.
There is a copy here (there is no sense in making a diff because almost
all lines change):

ftp://ftp.NetBSD.org/pub/NetBSD/misc/jmmv/faq.xml

Any objections in doing this?

Thanks,

(Continue reading)

Thomas Klausner | 1 Jun 2005 15:21
Picon

Handling options in bl3 files

Hi!

While trying to convert devel/allegro to the options
framework, I stumbled over the following problem:
Its bl3.mk file has contains
.if !empty(USE_ESOUND:M[Yy][Ee][Ss])
.  include "../../audio/esound/buildlink3.mk"
.endif
which should be convert to match against the PKG_OPTIONS
of the (to-be-) installed package.

How should this be done?

 Thomas


Gmane