mail/alpine: make: /usr/ports/mail/alpine/Makefile line 108: Malformed conditional
I get this while running portmaster on a most recently updated ports
tree:
make: Unknown modifier ')'
make: /usr/ports/mail/alpine/Makefile line 108: Malformed conditional
(${PORT_OPTIONS:MQUOTA) || defined(WITH_MAILDIR})
make: Fatal errors encountered -- cannot continue=== Launching child
to update fricas-1.1.8_5 to fricas-1.1.8_6
___
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: mail/alpine: make: /usr/ports/mail/alpine/Makefile line 108: Malformed conditional
On 6/7/2013 08:53, O. Hartmann wrote:
I get this while running portmaster on a most recently updated ports
tree:
make: Unknown modifier ')'
make: /usr/ports/mail/alpine/Makefile line 108: Malformed conditional
(${PORT_OPTIONS:MQUOTA) || defined(WITH_MAILDIR})
make: Fatal errors encountered -- cannot continue=== Launching child
to update fricas-1.1.8_5 to fricas-1.1.8_6
In inside brackets are inverted, that indicates it was edited with sed
during the optionng conversion.
Somebody should probably scan for this particular problem repo wide.
When it happens once, there could be others.
John
___
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: devel/flatzebra broken, maintainer timeout, please reverse commit
On Thu, 6 Jun 2013 18:43:08 +0100, Chris Rees wrote Hi, That's the proper fix- sorry I was unclear there; I meant if it can't be fixed easily. I have just updated the PR with a fix, see : http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/177949 Anton, can you test it and tell me how it goes ? Thanks, Best regards, -- Ganael LAPLANCHE ganael.laplan...@martymac.org http://www.martymac.org | http://contribs.martymac.org FreeBSD: martymac marty...@freebsd.org, http://www.FreeBSD.org ___ 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: mail/alpine: make: /usr/ports/mail/alpine/Makefile line 108: Malformed conditional
On Fri, Jun 07, 2013 at 08:57:01AM +0200, John Marino wrote:
On 6/7/2013 08:53, O. Hartmann wrote:
I get this while running portmaster on a most recently updated ports
tree:
make: Unknown modifier ')'
make: /usr/ports/mail/alpine/Makefile line 108: Malformed conditional
(${PORT_OPTIONS:MQUOTA) || defined(WITH_MAILDIR})
make: Fatal errors encountered -- cannot continue=== Launching child
to update fricas-1.1.8_5 to fricas-1.1.8_6
In inside brackets are inverted, that indicates it was edited with sed
during the optionng conversion.
Somebody should probably scan for this particular problem repo wide.
When it happens once, there could be others.
John
___
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
Fixed sorry about that.
regards,
Bapt
pgpwjsWIWjk_y.pgp
Description: PGP signature
[HEADSUP] dialog4ports does not popup anymore only for global options
Hi, I have committed the code preventing config-conditional to popup the dialog only if some global options are defined (NLS, DOCS, EXAMPLES and IPV6 for now). This was a popular demand, hope that it fits the requirement. So from now please always define via OPTIONS_DEFINE those options if your ports are going to use them. regards, Bapt pgpYne1nED4Qc.pgp Description: PGP signature
FreeBSD unmaintained ports which are currently marked broken
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as broken in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 7.x/8.x/9.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: audio/mp3towav-bundle broken because: fails to build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.8.20130510040555.pointyhat/mp3towav-bundle-0.4.1_2.log (May 14 20:15:43 UTC 2013) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=mp3towav-bundle portname: audio/mpg123.el broken because: fails to fetch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=mpg123.el portname: biology/dotter broken because: checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=biologyportname=dotter portname: chinese/big5con broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=big5con portname: chinese/bitchx broken because: patch reject build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=bitchx portname: chinese/hztty broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=hztty portname: databases/msql broken because: Broken on FreeBSD 9+ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=msql portname: databases/sqlrelay broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=sqlrelay portname: deskutils/libopensync-plugin-python-devel broken because: fails to build with recent libopensync build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutilsportname=libopensync-plugin-python-devel portname: deskutils/libopensync-plugin-vformat-devel broken because: fails to build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutilsportname=libopensync-plugin-vformat-devel portname: deskutils/simpleagenda broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutilsportname=simpleagenda portname: devel/dsss broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=dsss portname: devel/libYGP broken because: Does not build with recent boost build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=libYGP portname: devel/linuxthreads broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linuxthreads portname: devel/mico broken because: fails to build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.8.20130510040555.pointyhat/mico-2.3.12_4.log (May 14 19:56:54 UTC 2013) overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=mico
FreeBSD ports which are currently marked broken
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as broken in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 7.x/8.x/9.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: accessibility/yasr broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=accessibilityportname=yasr portname: audio/gdam broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=gdam portname: audio/mp3towav-bundle broken because: fails to build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.8.20130510040555.pointyhat/mp3towav-bundle-0.4.1_2.log (May 14 20:15:43 UTC 2013) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=mp3towav-bundle portname: audio/mpg123.el broken because: fails to fetch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=mpg123.el portname: benchmarks/polygraph31 broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=benchmarksportname=polygraph31 portname: biology/dotter broken because: checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=biologyportname=dotter portname: cad/salome-geom broken because: fails to build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.8.20130510040555.pointyhat/salome-geom-5.1.4_6.log (May 14 20:16:25 UTC 2013) overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=salome-geom portname: cad/salome-med broken because: Fails to fetch build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.8.20130510040555.pointyhat/salome-med-5.1.4_6.log (May 14 19:43:40 UTC 2013) overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=salome-med portname: cad/salome-yacs broken because: fails to build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.8.20130510040555.pointyhat/salome-yacs-5.1.4_4.log (May 14 21:11:46 UTC 2013) overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=salome-yacs portname: chinese/big5con broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=big5con portname: chinese/bitchx broken because: patch reject build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=bitchx portname: chinese/cxterm broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=cxterm portname: chinese/hztty broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=hztty portname: comms/hso-kmod broken because: does not build with USB2, please try comms/uhso-kmod instead build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=commsportname=hso-kmod
Re: devel/flatzebra broken, maintainer timeout, please reverse commit
I have just updated the PR with a fix, see : http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/177949 Anton, can you test it and tell me how it goes ? works fine on ia64 Thanks Anton ___ 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: ports 10-CURRENT
El día Sunday, May 26, 2013 a las 05:50:22PM +0200, Matthias Apitz escribió:
Hello,
Today morning, after SVN checkout /usr/ports r319094 and wiping out
all old stuff:
# rm -rf /usr/local/*
# rm -rf /var/db/pkg/*
# rm -rf /compat/linux/*
I've made the following ports:
x11/xorg
devel/imake
now the 'imake' works fine to configure, for example graphics/xv;
Good News!!!
It seems that net/vnc tries to compile its own version of the imake
tool, which is now not working anymore; see attached nohup.out;
matthias
=== Building for vnc-4.1.3_5
cd /usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc make CC=cc CXX=c++ World
./config/util/printver.c:15:1: warning: type specifier missing, defaults to
'int' [-Wimplicit-int]
main()
^~~~
1 warning generated.
Building XFree86 version 4.3.0 (27 February 2003).
I hope you checked the configuration parameters in ./config/cf
to see if you need to pass BOOTSTRAPCFLAGS.
viernes, 7 de junio de 2013, 07:15:59 CEST
cd ./config/imake make -f Makefile.ini BOOTSTRAPCFLAGS= CC=cc clean
rm -f ccimake imake.o imake
rm -f *.CKP *.ln *.BAK *.bak *.o core errs ,* *~ *.a tags TAGS make.log \#*
rm -f -r Makefile.proto Makefile Makefile.dep bootstrap
rm -f imakemdep_cpp.h
make Makefile.boot
cd ./config/imake make -f Makefile.ini BOOTSTRAPCFLAGS= CC=cc
making imake with BOOTSTRAPCFLAGS= and CROSSCOMPILEFLAGS=-DCROSSCOMPILEDIR=
in config/imake
cc -o ccimake -DCROSSCOMPILEDIR=\\ -O -I../../include
-I../../imports/x11/include/X11 ccimake.c
ccimake.c:53:6: warning: implicit declaration of function 'write' is invalid in
C99 [-Wimplicit-function-declaration]
write(1, crosscompiledir_str, sizeof(crosscompiledir_str) - 1);
^
1 warning generated.
if [ -n ] ; then /cc -E `./ccimake` -DCROSSCOMPILE_CPP imakemdep.h
imakemdep_cpp.h; else touch imakemdep_cpp.h; fi
cc -c -O -I../../include -I../../imports/x11/include/X11 `./ccimake` imake.c
cc -o imake -O -I../../include -I../../imports/x11/include/X11 imake.o
rm -f ./config/makedepend/Makefile.proto
./config/imake/imake -I./config/cf -s ./config/makedepend/Makefile.proto -f
./config/makedepend/Imakefile -DTOPDIR=../.. -DCURDIR=./config/makedepend
objformat: not found
In file included from Imakefile.c:16:
In file included from ./config/cf/Imake.tmpl:104:
./config/cf/FreeBSD.cf:477:35: error: '#' is not followed by a macro parameter
#define IncludeMakefile(file) @@# dependencies are in .depend
^
In file included from Imakefile.c:16:
In file included from ./config/cf/Imake.tmpl:300:
./config/cf/Imake.rules:1627:27: warning: empty character constant
[-Winvalid-pp-token]
for flag in ${MAKEFLAGS} ''; do \ @@\
^
./config/cf/Imake.rules:1850:35: error: '#' is not followed by a macro parameter
#define IncludeMakefile(file) @@# dependencies are in .depend
^
In file included from Imakefile.c:16:
./config/cf/Imake.tmpl:1982:10: fatal error: ' X11 .rules' file not found
#include ProjectRulesFile
^
./config/cf/Imake.tmpl:1980:35: note: expanded from macro 'ProjectRulesFile'
# define ProjectRulesFile Concat3(,TopLevelProject,.rules)
^
./config/cf/Imake.rules:252:23: note: expanded from macro 'Concat3'
#define Concat3(a,b,c)a/**/b/**/c
^
1 warning and 3 errors generated.
./config/imake/imake: Exit code 1.
Stop.
*** [./config/makedepend/Makefile.proto] Error code 1
Stop in /usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc.
*** [World] Error code 1
Stop in /usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc.
*** [post-build] Error code 1
Stop in /usr/ports/net/vnc.
*** [build] Error code 1
Stop in /usr/ports/net/vnc.
--
Matthias Apitz | /\ ASCII Ribbon Campaign: www.asciiribbon.org
E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail
WWW: http://www.unixarea.de/ | X - No proprietary attachments
phone: +49-170-4527211 | / \ - Respect for open standards
___
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: devel/flatzebra broken, maintainer timeout, please reverse commit
On Fri, 7 Jun 2013 09:52:44 +0100 (BST), Anton Shterenlikht wrote Anton, can you test it and tell me how it goes ? works fine on ia64 Thanks. I'll wait for Edwin approval and commit the update. Best regards, -- Ganael LAPLANCHE ganael.laplan...@martymac.org http://www.martymac.org | http://contribs.martymac.org FreeBSD: martymac marty...@freebsd.org, http://www.FreeBSD.org ___ 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: [HEADSUP] dialog4ports does not popup anymore only for global options
Baptiste Daroussin wrote: I have committed the code preventing config-conditional to popup the dialog only if some global options are defined (NLS, DOCS, EXAMPLES and IPV6 for now). This was a popular demand, hope that it fits the requirement. So from now please always define via OPTIONS_DEFINE those options if your ports are going to use them. Is it possible to still show the dialog if one of those options implies additional dependencies? If not, what should those of us who do not want them installed do? ___ 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: [HEADSUP] dialog4ports does not popup anymore only for global options
On Fri, Jun 07, 2013 at 12:20:24PM +0300, Vitaly Magerya wrote: Baptiste Daroussin wrote: I have committed the code preventing config-conditional to popup the dialog only if some global options are defined (NLS, DOCS, EXAMPLES and IPV6 for now). This was a popular demand, hope that it fits the requirement. So from now please always define via OPTIONS_DEFINE those options if your ports are going to use them. Is it possible to still show the dialog if one of those options implies additional dependencies? If not, what should those of us who do not want them installed do? make config will always show those options so you can always tune them. just make config-conditional will not fireup a new dialog automatically if the defined options are only those from the global options. regards, Bapt pgpvH3KoZ7K2F.pgp Description: PGP signature
Re: devel/flatzebra broken, maintainer timeout, please reverse commit
On 7 Jun 2013 10:16, Ganael LAPLANCHE ganael.laplan...@martymac.org wrote: On Fri, 7 Jun 2013 09:52:44 +0100 (BST), Anton Shterenlikht wrote Anton, can you test it and tell me how it goes ? works fine on ia64 Thanks. I'll wait for Edwin approval and commit the update. I think maintainer timeout applies here; unless there was an acknowledgement from the maintainer before we shouldn't make people wait any longer. Chris ___ 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: devel/flatzebra broken, maintainer timeout, please reverse commit
On Fri, 7 Jun 2013 10:48:32 +0100, Chris Rees wrote I think maintainer timeout applies here; unless there was an acknowledgement from the maintainer before we shouldn't make people wait any longer. You're right, this PR is quite old now (6 weeks). I've committed the change. Thanks ! -- Ganael LAPLANCHE ganael.laplan...@martymac.org http://www.martymac.org | http://contribs.martymac.org FreeBSD: martymac marty...@freebsd.org, http://www.FreeBSD.org ___ 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: [HEADSUP] dialog4ports does not popup anymore only for global options
Baptiste Daroussin wrote: Is it possible to still show the dialog if one of those options implies additional dependencies? If not, what should those of us who do not want them installed do? make config will always show those options so you can always tune them. just make config-conditional will not fireup a new dialog automatically if the defined options are only those from the global options. I see. As far as I can tell though, and correct me if I'm wrong, but 'make install' doesn't show those options. It also does not show those options for dependent ports. Neither does 'make config-recursive'. Tools like portmaster will now ignore those as well during install and reinstall. So, again, what are my options if I don't want dependencies to be pulled in silently? ___ 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: [HEADSUP] dialog4ports does not popup anymore only for global options
On Fri, Jun 07, 2013 at 01:15:49PM +0300, Vitaly Magerya wrote: Baptiste Daroussin wrote: Is it possible to still show the dialog if one of those options implies additional dependencies? If not, what should those of us who do not want them installed do? make config will always show those options so you can always tune them. just make config-conditional will not fireup a new dialog automatically if the defined options are only those from the global options. I see. As far as I can tell though, and correct me if I'm wrong, but 'make install' doesn't show those options. It also does not show those options for dependent ports. Neither does 'make config-recursive'. Tools like portmaster will now ignore those as well during install and reinstall. So, again, what are my options if I don't want dependencies to be pulled in silently? You have no options and you never had one in the ports tree sorry. If you have a way to implement that cleanly, I'll be happy to push such features in the ports but really I see a way to do what you ask for. regards, Bapt pgprabnyKNIcR.pgp Description: PGP signature
Re: [HEADSUP] dialog4ports does not popup anymore only for global options
Baptiste Daroussin wrote: So, again, what are my options if I don't want dependencies to be pulled in silently? You have no options and you never had one in the ports tree sorry. Previously maintainers could decide to show dialog with only DOCS or not to show it. They didn't do it consistently, of course. Probably because no guidelines where established. If you have a way to implement that cleanly, I'll be happy to push such features in the ports but really I see a way to do what you ask for. We could provide 'OPTIONS_DEFINE_SILENT' for ports that don't want to spam the users with dialogs, but still want to provide the options. Or a separate flag, like 'OPTIONS_ARE_SILENT'. ___ 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: [HEADSUP] dialog4ports does not popup anymore only for global options
On 2013-06-07 12:17, Baptiste Daroussin wrote: On Fri, Jun 07, 2013 at 01:15:49PM +0300, Vitaly Magerya wrote: Baptiste Daroussin wrote: Is it possible to still show the dialog if one of those options implies additional dependencies? If not, what should those of us who do not want them installed do? make config will always show those options so you can always tune them. just make config-conditional will not fireup a new dialog automatically if the defined options are only those from the global options. I see. As far as I can tell though, and correct me if I'm wrong, but 'make install' doesn't show those options. It also does not show those options for dependent ports. Neither does 'make config-recursive'. Tools like portmaster will now ignore those as well during install and reinstall. So, again, what are my options if I don't want dependencies to be pulled in silently? You have no options and you never had one in the ports tree sorry. If you have a way to implement that cleanly, I'll be happy to push such features in the ports but really I see a way to do what you ask for. How about only suppressing the dialog if the options have been explicitly set or unset in make.conf? signature.asc Description: OpenPGP digital signature
Re: [HEADSUP] dialog4ports does not popup anymore only for global options
On Fri, Jun 07, 2013 at 12:46:08PM +0200, Tijl Coosemans wrote: On 2013-06-07 12:17, Baptiste Daroussin wrote: On Fri, Jun 07, 2013 at 01:15:49PM +0300, Vitaly Magerya wrote: Baptiste Daroussin wrote: Is it possible to still show the dialog if one of those options implies additional dependencies? If not, what should those of us who do not want them installed do? make config will always show those options so you can always tune them. just make config-conditional will not fireup a new dialog automatically if the defined options are only those from the global options. I see. As far as I can tell though, and correct me if I'm wrong, but 'make install' doesn't show those options. It also does not show those options for dependent ports. Neither does 'make config-recursive'. Tools like portmaster will now ignore those as well during install and reinstall. So, again, what are my options if I don't want dependencies to be pulled in silently? You have no options and you never had one in the ports tree sorry. If you have a way to implement that cleanly, I'll be happy to push such features in the ports but really I see a way to do what you ask for. How about only suppressing the dialog if the options have been explicitly set or unset in make.conf? That would be easy but is that a really desired feature? regards, Bapt pgpsIkuScXlSE.pgp Description: PGP signature
Re: ports 10-CURRENT
Hi,
I'm out of town at the moment but I'll take a look at this sometime next
week. If you want please submit a PR for this as well.
--
Cheers,
Cy Schubert cy.schub...@komquats.com
FreeBSD UNIX: c...@freebsd.org Web: http://www.FreeBSD.org
In message 20130607085730.ga8...@sh4-5.1blu.de, Matthias Apitz writes:
El día Sunday, May 26, 2013 a las 05:50:22PM +0200, Matthias Apitz escribió:
Hello,
Today morning, after SVN checkout /usr/ports r319094 and wiping out
all old stuff:
# rm -rf /usr/local/*
# rm -rf /var/db/pkg/*
# rm -rf /compat/linux/*
I've made the following ports:
x11/xorg
devel/imake
now the 'imake' works fine to configure, for example graphics/xv;
Good News!!!
It seems that net/vnc tries to compile its own version of the imake
tool, which is now not working anymore; see attached nohup.out;
matthias
=== Building for vnc-4.1.3_5
cd /usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc make CC=cc CXX=c++ Wo
rld
./config/util/printver.c:15:1: warning: type specifier missing, defaults to '
int' [-Wimplicit-int]
main()
^~~~
1 warning generated.
Building XFree86 version 4.3.0 (27 February 2003).
I hope you checked the configuration parameters in ./config/cf
to see if you need to pass BOOTSTRAPCFLAGS.
viernes, 7 de junio de 2013, 07:15:59 CEST
cd ./config/imake make -f Makefile.ini BOOTSTRAPCFLAGS= CC=cc clean
rm -f ccimake imake.o imake
rm -f *.CKP *.ln *.BAK *.bak *.o core errs ,* *~ *.a tags TAGS make.log \#*
rm -f -r Makefile.proto Makefile Makefile.dep bootstrap
rm -f imakemdep_cpp.h
make Makefile.boot
cd ./config/imake make -f Makefile.ini BOOTSTRAPCFLAGS= CC=cc
making imake with BOOTSTRAPCFLAGS= and CROSSCOMPILEFLAGS=-DCROSSCOMPILEDIR=
in config/imake
cc -o ccimake -DCROSSCOMPILEDIR=\\ -O -I../../include -I../../imports/x11/
include/X11 ccimake.c
ccimake.c:53:6: warning: implicit declaration of function 'write' is invalid
in C99 [-Wimplicit-function-declaration]
write(1, crosscompiledir_str, sizeof(crosscompiledir_str) - 1);
^
1 warning generated.
if [ -n ] ; then /cc -E `./ccimake` -DCROSSCOMPILE_CPP imakemdep.h ima
kemdep_cpp.h; else touch imakemdep_cpp.h; fi
cc -c -O -I../../include -I../../imports/x11/include/X11 `./ccimake` imake.c
cc -o imake -O -I../../include -I../../imports/x11/include/X11 imake.o
rm -f ./config/makedepend/Makefile.proto
./config/imake/imake -I./config/cf -s ./config/makedepend/Makefile.proto -f
./config/makedepend/Imakefile -DTOPDIR=../.. -DCURDIR=./config/makedepend
objformat: not found
In file included from Imakefile.c:16:
In file included from ./config/cf/Imake.tmpl:104:
./config/cf/FreeBSD.cf:477:35: error: '#' is not followed by a macro paramete
r
#define IncludeMakefile(file) @@# dependencies are in .depend
^
In file included from Imakefile.c:16:
In file included from ./config/cf/Imake.tmpl:300:
./config/cf/Imake.rules:1627:27: warning: empty character constant [-Winvalid
-pp-token]
for flag in ${MAKEFLAGS} ''; do \ @@\
^
./config/cf/Imake.rules:1850:35: error: '#' is not followed by a macro parame
ter
#define IncludeMakefile(file) @@# dependencies are in .depend
^
In file included from Imakefile.c:16:
./config/cf/Imake.tmpl:1982:10: fatal error: ' X11 .rules' file not found
#include ProjectRulesFile
^
./config/cf/Imake.tmpl:1980:35: note: expanded from macro 'ProjectRulesFile'
# define ProjectRulesFile Concat3(,TopLevelProject,.rules)
^
./config/cf/Imake.rules:252:23: note: expanded from macro 'Concat3'
#define Concat3(a,b,c)a/**/b/**/c
^
1 warning and 3 errors generated.
./config/imake/imake: Exit code 1.
Stop.
*** [./config/makedepend/Makefile.proto] Error code 1
Stop in /usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc.
*** [World] Error code 1
Stop in /usr/ports/net/vnc/work/vnc-4_1_3-unixsrc/unix/xc.
*** [post-build] Error code 1
Stop in /usr/ports/net/vnc.
*** [build] Error code 1
Stop in /usr/ports/net/vnc.
--
Matthias Apitz | /\ ASCII Ribbon Campaign: www.asciiribbon.or
g
E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail
WWW: http://www.unixarea.de/ | X - No proprietary attachments
phone: +49-170-4527211 | / \ - Respect for open standards
___
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: [HEADSUP] dialog4ports does not popup anymore only for global options
On 2013-06-07 13:40, Baptiste Daroussin wrote: On Fri, Jun 07, 2013 at 12:46:08PM +0200, Tijl Coosemans wrote: On 2013-06-07 12:17, Baptiste Daroussin wrote: On Fri, Jun 07, 2013 at 01:15:49PM +0300, Vitaly Magerya wrote: Baptiste Daroussin wrote: Is it possible to still show the dialog if one of those options implies additional dependencies? If not, what should those of us who do not want them installed do? make config will always show those options so you can always tune them. just make config-conditional will not fireup a new dialog automatically if the defined options are only those from the global options. I see. As far as I can tell though, and correct me if I'm wrong, but 'make install' doesn't show those options. It also does not show those options for dependent ports. Neither does 'make config-recursive'. Tools like portmaster will now ignore those as well during install and reinstall. So, again, what are my options if I don't want dependencies to be pulled in silently? You have no options and you never had one in the ports tree sorry. If you have a way to implement that cleanly, I'll be happy to push such features in the ports but really I see a way to do what you ask for. How about only suppressing the dialog if the options have been explicitly set or unset in make.conf? That would be easy but is that a really desired feature? I can only speak for myself, but I don't see DOCS as a global option. For some ports I want documentation, for others I don't, so I want the dialog to show up even if DOCS is the only option. There doesn't seem to be a clear cut line between global and per port options and different users have different opinions about it. Can you make it such that config-conditional suppresses the dialog if all options have been explicitly set or unset either through command line, make.conf or optionsfile? Or in other words only show the dialog if one of the options falls back to a default value (e.g. when a new option has been added to a port and that option has not been set globally). I think that would allow anyone to set/unset any option globally and not be bothered by dialogs without enforcing that view on everybody else. You wouldn't need GLOBAL_OPTIONS any more then. signature.asc Description: OpenPGP digital signature
Re: [HEADSUP] dialog4ports does not popup anymore only for global options
Le 07/06/2013 15:30, Tijl Coosemans a écrit : On 2013-06-07 13:40, Baptiste Daroussin wrote: On Fri, Jun 07, 2013 at 12:46:08PM +0200, Tijl Coosemans wrote: On 2013-06-07 12:17, Baptiste Daroussin wrote: On Fri, Jun 07, 2013 at 01:15:49PM +0300, Vitaly Magerya wrote: Baptiste Daroussin wrote: Is it possible to still show the dialog if one of those options implies additional dependencies? If not, what should those of us who do not want them installed do? make config will always show those options so you can always tune them. just make config-conditional will not fireup a new dialog automatically if the defined options are only those from the global options. I see. As far as I can tell though, and correct me if I'm wrong, but 'make install' doesn't show those options. It also does not show those options for dependent ports. Neither does 'make config-recursive'. Tools like portmaster will now ignore those as well during install and reinstall. So, again, what are my options if I don't want dependencies to be pulled in silently? You have no options and you never had one in the ports tree sorry. If you have a way to implement that cleanly, I'll be happy to push such features in the ports but really I see a way to do what you ask for. How about only suppressing the dialog if the options have been explicitly set or unset in make.conf? That would be easy but is that a really desired feature? I can only speak for myself, but I don't see DOCS as a global option. For some ports I want documentation, for others I don't, so I want the dialog to show up even if DOCS is the only option. There doesn't seem to be a clear cut line between global and per port options and different users have different opinions about it. Can you make it such that config-conditional suppresses the dialog if all options have been explicitly set or unset either through command line, make.conf or optionsfile? Or in other words only show the dialog if one of the options falls back to a default value (e.g. when a new option has been added to a port and that option has not been set globally). I think that would allow anyone to set/unset any option globally and not be bothered by dialogs without enforcing that view on everybody else. You wouldn't need GLOBAL_OPTIONS any more then. Like you said, every users have different opinion (as I have another than yours :-) ) and the only way I think can satisfy every one is a customizable behavior… -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail +33 (0)6 64 33 97 92 | * PDF for documents http://florent.peterschmitt.fr | Thank you :) signature.asc Description: OpenPGP digital signature
Re: [HEADSUP] dialog4ports does not popup anymore only for global options
On Fri, Jun 07, 2013 at 03:30:15PM +0200, Tijl Coosemans wrote: On 2013-06-07 13:40, Baptiste Daroussin wrote: On Fri, Jun 07, 2013 at 12:46:08PM +0200, Tijl Coosemans wrote: On 2013-06-07 12:17, Baptiste Daroussin wrote: On Fri, Jun 07, 2013 at 01:15:49PM +0300, Vitaly Magerya wrote: Baptiste Daroussin wrote: Is it possible to still show the dialog if one of those options implies additional dependencies? If not, what should those of us who do not want them installed do? make config will always show those options so you can always tune them. just make config-conditional will not fireup a new dialog automatically if the defined options are only those from the global options. I see. As far as I can tell though, and correct me if I'm wrong, but 'make install' doesn't show those options. It also does not show those options for dependent ports. Neither does 'make config-recursive'. Tools like portmaster will now ignore those as well during install and reinstall. So, again, what are my options if I don't want dependencies to be pulled in silently? You have no options and you never had one in the ports tree sorry. If you have a way to implement that cleanly, I'll be happy to push such features in the ports but really I see a way to do what you ask for. How about only suppressing the dialog if the options have been explicitly set or unset in make.conf? That would be easy but is that a really desired feature? I can only speak for myself, but I don't see DOCS as a global option. For some ports I want documentation, for others I don't, so I want the dialog to show up even if DOCS is the only option. There doesn't seem to be a clear cut line between global and per port options and different users have different opinions about it. Can you make it such that config-conditional suppresses the dialog if all options have been explicitly set or unset either through command line, make.conf or optionsfile? Or in other words only show the dialog if one of the options falls back to a default value (e.g. when a new option has been added to a port and that option has not been set globally). I think that would allow anyone to set/unset any option globally and not be bothered by dialogs without enforcing that view on everybody else. You wouldn't need GLOBAL_OPTIONS any more then. Ok so I misunderstood at first. That looks not easy to do, and I'm a bit borred with hacking the options. If someone do something in that direction, I'll be happy to review and help, but honnestly I don't plan to do it myself. regads, Bapt pgplEngOzunbX.pgp Description: PGP signature
Re: [HEADSUP] dialog4ports does not popup anymore only for global options
On Fri, 7 Jun 2013 15:42:44 +0200 Baptiste Daroussin b...@freebsd.org wrote: On Fri, Jun 07, 2013 at 03:30:15PM +0200, Tijl Coosemans wrote: On 2013-06-07 13:40, Baptiste Daroussin wrote: On Fri, Jun 07, 2013 at 12:46:08PM +0200, Tijl Coosemans wrote: On 2013-06-07 12:17, Baptiste Daroussin wrote: On Fri, Jun 07, 2013 at 01:15:49PM +0300, Vitaly Magerya wrote: Baptiste Daroussin wrote: Is it possible to still show the dialog if one of those options implies additional dependencies? If not, what should those of us who do not want them installed do? make config will always show those options so you can always tune them. just make config-conditional will not fireup a new dialog automatically if the defined options are only those from the global options. I see. As far as I can tell though, and correct me if I'm wrong, but 'make install' doesn't show those options. It also does not show those options for dependent ports. Neither does 'make config-recursive'. Tools like portmaster will now ignore those as well during install and reinstall. So, again, what are my options if I don't want dependencies to be pulled in silently? You have no options and you never had one in the ports tree sorry. If you have a way to implement that cleanly, I'll be happy to push such features in the ports but really I see a way to do what you ask for. How about only suppressing the dialog if the options have been explicitly set or unset in make.conf? That would be easy but is that a really desired feature? I can only speak for myself, but I don't see DOCS as a global option. For some ports I want documentation, for others I don't, so I want the dialog to show up even if DOCS is the only option. There doesn't seem to be a clear cut line between global and per port options and different users have different opinions about it. Can you make it such that config-conditional suppresses the dialog if all options have been explicitly set or unset either through command line, make.conf or optionsfile? Or in other words only show the dialog if one of the options falls back to a default value (e.g. when a new option has been added to a port and that option has not been set globally). I think that would allow anyone to set/unset any option globally and not be bothered by dialogs without enforcing that view on everybody else. You wouldn't need GLOBAL_OPTIONS any more then. Ok so I misunderstood at first. That looks not easy to do, and I'm a bit borred with hacking the options. If someone do something in that direction, I'll be happy to review and help, but honnestly I don't plan to do it myself. regads, Bapt I can feel your pain, Bapt :) Anyway, I think the problem with those options (especially DOCS) is that they are not really global in that you want to set them for all ports, but more like general as in well-known. So many ports provide them and the user has a good idea what they're supposed to mean, but ultimately you don't want to set them to the same value for all ports. Regardless of implementation details I would like to see something like the following at least for DOCS, either through config-recursive or - maybe more likely - through a tool like portmaster: After starting the build process and collecting dependencies, an ncurses dialog should be shown that says The following ports provide documentation and a check-box list showing all packages as well as a All and None options on top of the list. That way the user can easily select which port documentation to install and at the same time can easily set it for all affected ports, e.g. # portmaster shells/bash +-- Install documentation -+ + [ ] All + + [X] None + + [ ] converters/libiconv + + [ ] devel/gettext+ + [ ] shells/bash + +--+ + OK Cancel + +--+ I have no idea what it would take to implement this in a sane way within the current framework, but IMHO this would provide a pretty good user experience. Cheers, Michael p.s. - If you wanted to provide this for more than one general option, dialog4ports' section feature might become handy, e.g.: + General options -+ + [ ] All + + [X] None + + Documentation --+ + [ ] converters/libiconv + + [ ] devel/gettext+ + [ ] shells/bash + + Native Language Support + + [ ] devel/gettext+ + [ ] shells/bash + +--+ + OK Cancel + +--+ -- Michael Gmelin ___ freebsd-ports@freebsd.org mailing
Re: [HEADSUP] dialog4ports does not popup anymore only for global options
On 7 Jun 2013 17:57, Michael Gmelin free...@grem.de wrote: On Fri, 7 Jun 2013 15:42:44 +0200 Baptiste Daroussin b...@freebsd.org wrote: On Fri, Jun 07, 2013 at 03:30:15PM +0200, Tijl Coosemans wrote: On 2013-06-07 13:40, Baptiste Daroussin wrote: On Fri, Jun 07, 2013 at 12:46:08PM +0200, Tijl Coosemans wrote: On 2013-06-07 12:17, Baptiste Daroussin wrote: On Fri, Jun 07, 2013 at 01:15:49PM +0300, Vitaly Magerya wrote: Baptiste Daroussin wrote: Is it possible to still show the dialog if one of those options implies additional dependencies? If not, what should those of us who do not want them installed do? make config will always show those options so you can always tune them. just make config-conditional will not fireup a new dialog automatically if the defined options are only those from the global options. I see. As far as I can tell though, and correct me if I'm wrong, but 'make install' doesn't show those options. It also does not show those options for dependent ports. Neither does 'make config-recursive'. Tools like portmaster will now ignore those as well during install and reinstall. So, again, what are my options if I don't want dependencies to be pulled in silently? You have no options and you never had one in the ports tree sorry. If you have a way to implement that cleanly, I'll be happy to push such features in the ports but really I see a way to do what you ask for. How about only suppressing the dialog if the options have been explicitly set or unset in make.conf? That would be easy but is that a really desired feature? I can only speak for myself, but I don't see DOCS as a global option. For some ports I want documentation, for others I don't, so I want the dialog to show up even if DOCS is the only option. There doesn't seem to be a clear cut line between global and per port options and different users have different opinions about it. Can you make it such that config-conditional suppresses the dialog if all options have been explicitly set or unset either through command line, make.conf or optionsfile? Or in other words only show the dialog if one of the options falls back to a default value (e.g. when a new option has been added to a port and that option has not been set globally). I think that would allow anyone to set/unset any option globally and not be bothered by dialogs without enforcing that view on everybody else. You wouldn't need GLOBAL_OPTIONS any more then. Ok so I misunderstood at first. That looks not easy to do, and I'm a bit borred with hacking the options. If someone do something in that direction, I'll be happy to review and help, but honnestly I don't plan to do it myself. regads, Bapt I can feel your pain, Bapt :) Anyway, I think the problem with those options (especially DOCS) is that they are not really global in that you want to set them for all ports, but more like general as in well-known. So many ports provide them and the user has a good idea what they're supposed to mean, but ultimately you don't want to set them to the same value for all ports. Regardless of implementation details I would like to see something like the following at least for DOCS, either through config-recursive or - maybe more likely - through a tool like portmaster: After starting the build process and collecting dependencies, an ncurses dialog should be shown that says The following ports provide documentation and a check-box list showing all packages as well as a All and None options on top of the list. That way the user can easily select which port documentation to install and at the same time can easily set it for all affected ports, e.g. # portmaster shells/bash +-- Install documentation -+ + [ ] All + + [X] None + + [ ] converters/libiconv + + [ ] devel/gettext+ + [ ] shells/bash + +--+ + OK Cancel + +--+ I have no idea what it would take to implement this in a sane way within the current framework, but IMHO this would provide a pretty good user experience. Cheers, Michael p.s. - If you wanted to provide this for more than one general option, dialog4ports' section feature might become handy, e.g.: + General options -+ + [ ] All + + [X] None + + Documentation --+ + [ ] converters/libiconv + + [ ] devel/gettext+ + [ ] shells/bash + + Native Language Support + + [ ] devel/gettext+ + [ ] shells/bash + I can see your point when talking about DOCS, but for
Re: [HEADSUP] dialog4ports does not popup anymore only for global options
On Fri, 7 Jun 2013 18:15:16 +0100 Chris Rees utis...@gmail.com wrote: On 7 Jun 2013 17:57, Michael Gmelin free...@grem.de wrote: On Fri, 7 Jun 2013 15:42:44 +0200 Baptiste Daroussin b...@freebsd.org wrote: On Fri, Jun 07, 2013 at 03:30:15PM +0200, Tijl Coosemans wrote: On 2013-06-07 13:40, Baptiste Daroussin wrote: On Fri, Jun 07, 2013 at 12:46:08PM +0200, Tijl Coosemans wrote: On 2013-06-07 12:17, Baptiste Daroussin wrote: On Fri, Jun 07, 2013 at 01:15:49PM +0300, Vitaly Magerya wrote: Baptiste Daroussin wrote: Is it possible to still show the dialog if one of those options implies additional dependencies? If not, what should those of us who do not want them installed do? make config will always show those options so you can always tune them. just make config-conditional will not fireup a new dialog automatically if the defined options are only those from the global options. I see. As far as I can tell though, and correct me if I'm wrong, but 'make install' doesn't show those options. It also does not show those options for dependent ports. Neither does 'make config-recursive'. Tools like portmaster will now ignore those as well during install and reinstall. So, again, what are my options if I don't want dependencies to be pulled in silently? You have no options and you never had one in the ports tree sorry. If you have a way to implement that cleanly, I'll be happy to push such features in the ports but really I see a way to do what you ask for. How about only suppressing the dialog if the options have been explicitly set or unset in make.conf? That would be easy but is that a really desired feature? I can only speak for myself, but I don't see DOCS as a global option. For some ports I want documentation, for others I don't, so I want the dialog to show up even if DOCS is the only option. There doesn't seem to be a clear cut line between global and per port options and different users have different opinions about it. Can you make it such that config-conditional suppresses the dialog if all options have been explicitly set or unset either through command line, make.conf or optionsfile? Or in other words only show the dialog if one of the options falls back to a default value (e.g. when a new option has been added to a port and that option has not been set globally). I think that would allow anyone to set/unset any option globally and not be bothered by dialogs without enforcing that view on everybody else. You wouldn't need GLOBAL_OPTIONS any more then. Ok so I misunderstood at first. That looks not easy to do, and I'm a bit borred with hacking the options. If someone do something in that direction, I'll be happy to review and help, but honnestly I don't plan to do it myself. regads, Bapt I can feel your pain, Bapt :) Anyway, I think the problem with those options (especially DOCS) is that they are not really global in that you want to set them for all ports, but more like general as in well-known. So many ports provide them and the user has a good idea what they're supposed to mean, but ultimately you don't want to set them to the same value for all ports. Regardless of implementation details I would like to see something like the following at least for DOCS, either through config-recursive or - maybe more likely - through a tool like portmaster: After starting the build process and collecting dependencies, an ncurses dialog should be shown that says The following ports provide documentation and a check-box list showing all packages as well as a All and None options on top of the list. That way the user can easily select which port documentation to install and at the same time can easily set it for all affected ports, e.g. # portmaster shells/bash +-- Install documentation -+ + [ ] All + + [X] None + + [ ] converters/libiconv + + [ ] devel/gettext+ + [ ] shells/bash + +--+ + OK Cancel + +--+ I have no idea what it would take to implement this in a sane way within the current framework, but IMHO this would provide a pretty good user experience. Cheers, Michael p.s. - If you wanted to provide this for more than one general option, dialog4ports' section feature might become handy, e.g.: + General options -+ + [ ] All + + [X] None + + Documentation --+ + [ ] converters/libiconv + + [ ] devel/gettext
Re: [HEADSUP] dialog4ports does not popup anymore only for global options
On Fri, Jun 7, 2013 at 8:15 PM, Chris Rees utis...@gmail.com wrote: I can see your point when talking about DOCS, but for NLS it's insanity *for general use*. Give me an example of where NLS non-globals are appropriate and I'll shut up. The GIMP in Russian locale. GNU Make in any non-English locale. -- Andrew W. Nosenko andrew.w.nose...@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
Re: Conversion to new options framework over
On Thu, Jun 06, 2013 at 08:45:10AM +0200, Baptiste Daroussin wrote: The compatibility code to parse the WITH/WITHOUT entries in make.conf will be removed in 6 months either. Do not forget to convert your configuration (make.conf, portsconf etc). A reminder will be send a month before the removal of the compatibility code. It would be useful to provide a pointer to instructions for doing so -- what exactly replaces WITH/WITHOUT entries in make.conf? For example, my dedicated server has WITHOUT_X11=yes in /etc/make.conf because it's headless and doesn't run an X server. What should that become? I tried googling, and the github doc page's only mention of make.conf is to add WITH_PKGNG=yes. Likewise the FreeBSD Handbook. The wiki apparently just points to the Handbook. Thanks, Jim Trigg ___ 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: [HEADSUP] dialog4ports does not popup anymore only for global options
On Fri, Jun 7, 2013 at 8:23 PM, Michael Gmelin free...@grem.de wrote: I was mostly talking about DOCS, I (poorly) chose NLS as an additional example to show how multiple groups could work. Usually NLS is a true global option. NLS is global option only for people with en_* locale, who, therefore, just don't see the pain produced by it. DOCS are just a space on HDD. But localized names of image filters, tools Co in GIMP -- it's just a barrier to use books and other knowledge sources. And I don't say just about stupid eye-blow errors in translations, when results of automatic merge went in the release and the wild without even fast looking through by the someone, who has that language as native. -- Andrew W. Nosenko andrew.w.nose...@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
packages-8-stable: nine (9) months old
Not sure if this is intentional now that package building is back online from the compromise, but they are indeed still that old... ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8-stable/All/ ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/All/ Nice to see 8.4 out though :) ___ 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: FreeBSD ports which are currently scheduled for deletion
Hi; lini...@freebsd.org writes: The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: sysutils/sge62 description:Sun Grid Engine, a batch queueing system maintainer: po...@freebsd.org deprecated because: Ancient and unsupported release expiration date:2013-03-01 build errors: http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.10.20130313090402.pointyhat/sge-6.2.2.1_3.log (Mar 14 02:20:26 UTC 2013) overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutilsportname=sge62 Our group relies heavily on this port and it compiles and works for us. Is it possible to reconsider this removal? I don't see an alternative in the ports tree? Thanks, Joseph ___ 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
FreeBSD Port: gettext-0.18.1.1
Dear I got the following error when trying to compile gettext from 8.4-RELEASE FreeBSD 8.4-RELEASE #0 r251259 === perl-5.14.2_3 depends on shared library: gdbm.4 - not found === Verifying install for gdbm.4 in /usr/ports/databases/gdbm === gdbm-1.9.1 depends on executable: gmake - not found === Verifying install for gmake in /usr/ports/devel/gmake === gmake-3.82_1 depends on shared library: intl - not found === Verifying install for intl in /usr/ports/devel/gettext === Patching for gettext-0.18.1.1_1 === Applying FreeBSD patches for gettext-0.18.1.1_1 File to patch: Regards, Yves ___ 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: The vim port needs a refresh
On Sat, May 25, 2013 at 09:50:50AM +0100, Chris Rees wrote: For years, people have been begging him to get over his fear of OPTIONS, and he sits in the way of progress against almost everyone's wishes. It's funny -- it's not just my fear of options -- every FreeBSD using co-worker I talk to frequently about OPTIONS do not like them either. -- -- David (obr...@freebsd.org) ___ 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: [HEADSUP] dialog4ports does not popup anymore only for global options
On 7 June 2013 18:49, Andrew W. Nosenko andrew.w.nose...@gmail.com wrote: On Fri, Jun 7, 2013 at 8:15 PM, Chris Rees utis...@gmail.com wrote: I can see your point when talking about DOCS, but for NLS it's insanity *for general use*. Give me an example of where NLS non-globals are appropriate and I'll shut up. The GIMP in Russian locale. GNU Make in any non-English locale. I guess you mean the translations are bad? Chris ___ 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: The vim port needs a refresh
On Fri, May 24, 2013 at 05:23:18PM -0400, Kenta Suzumoto wrote: - It fetches almost 700 patches from what seems like a dial-up connection in AUSTRALIA. You might as well be downloading a 1080p movie from a rock in the north pole, because that's about how fast it is. This can be very easily avoided by putting all the patches into a single tarball Please take this up with the Vim folks. I agree the time it takes to fetch the number of patches are very anonying. I've perodically asked for an update of the distfiles to include the patches to date. Please join in asking for this of the Vim developers. But I believe vim.org is a very reliable offical distribution source and I do not want to get in the middle of their distribution methods. P.S. we're now at 7.3.1011 - the port could use a normal update as well. /minor complaint I agree. Now that we have have all the releases we've had in flight out the door, new packages sets built; and finally I can use pkgNG I am doing an update. -- -- David (obr...@freebsd.org) ___ 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: Conversion to new options framework over
On 7 June 2013 18:55, Jim Trigg jtr...@spamcop.net wrote: On Thu, Jun 06, 2013 at 08:45:10AM +0200, Baptiste Daroussin wrote: The compatibility code to parse the WITH/WITHOUT entries in make.conf will be removed in 6 months either. Do not forget to convert your configuration (make.conf, portsconf etc). A reminder will be send a month before the removal of the compatibility code. It would be useful to provide a pointer to instructions for doing so -- what exactly replaces WITH/WITHOUT entries in make.conf? For example, my dedicated server has WITHOUT_X11=yes in /etc/make.conf because it's headless and doesn't run an X server. What should that become? I tried googling, and the github doc page's only mention of make.conf is to add WITH_PKGNG=yes. Likewise the FreeBSD Handbook. The wiki apparently just points to the Handbook. WITH_PKGNG is not a classical OPTION, because it doesn't apply to any port in particular. There is some documentation for users at [1], basically you need to change any WITH_ variables to OPTIONS_SET=, and WITHOUT_ to OPTIONS_UNSET=. I'll hopefully find some time soon to get it in the Handbook For example; WITHOUT_X11=yes WITH_CUPS=yes WITHOUT_PULSEAUDIO=yes becomes OPTIONS_SET=CUPS OPTIONS_UNSET=PULSEAUDIO X11 Chris [1] https://wiki.freebsd.org/Ports/Options/OptionsNG#What_users_need_to_know ___ 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: ports 10-CURRENT
El día Friday, June 07, 2013 a las 04:47:32AM -0700, Cy Schubert escribió: Hi, I'm out of town at the moment but I'll take a look at this sometime next week. If you want please submit a PR for this as well. done. http://www.freebsd.org/cgi/query-pr.cgi?pr=179416 matthias -- Sent from my FreeBSD netbook Matthias Apitz, g...@unixarea.de, http://www.unixarea.de/ f: +49-170-4527211 UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ 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: Conversion to new options framework over
On Fri, Jun 07, 2013 at 08:09:30PM +0100, Chris Rees wrote: On 7 June 2013 18:55, Jim Trigg jtr...@spamcop.net wrote: On Thu, Jun 06, 2013 at 08:45:10AM +0200, Baptiste Daroussin wrote: The compatibility code to parse the WITH/WITHOUT entries in make.conf will be removed in 6 months either. Do not forget to convert your configuration (make.conf, portsconf etc). A reminder will be send a month before the removal of the compatibility code. It would be useful to provide a pointer to instructions for doing so -- what exactly replaces WITH/WITHOUT entries in make.conf? For example, my dedicated server has WITHOUT_X11=yes in /etc/make.conf because it's headless and doesn't run an X server. What should that become? I tried googling, and the github doc page's only mention of make.conf is to add WITH_PKGNG=yes. Likewise the FreeBSD Handbook. The wiki apparently just points to the Handbook. WITH_PKGNG is not a classical OPTION, because it doesn't apply to any port in particular. I hadn't meant to refer to that as one of the WITH_ options that needed to be changed... There is some documentation for users at [1], basically you need to change any WITH_ variables to OPTIONS_SET=, and WITHOUT_ to OPTIONS_UNSET=. I'll hopefully find some time soon to get it in the Handbook For example; WITHOUT_X11=yes WITH_CUPS=yes WITHOUT_PULSEAUDIO=yes becomes OPTIONS_SET=CUPS OPTIONS_UNSET=PULSEAUDIO X11 That works for binary options, but what about version options? E.g., WITH_BDB_VER=47 ... Thanks, Jim ___ 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: Status of USE_GITHUB fetching
On 6/6/2013 8:26 AM, Bryan Drewery wrote: Ports using USE_GITHUB are currently broken. Github changed their tar/compression algorithm which has resulted in mismatched checksums. I am working on changing our implementation and updating all affected ports and should have the fix committed by this weekend, after enough testing. Github fixed the checksums issue. You will see random 'size not known' warnings. These should be harmless. It's due to how they have implemented their download streaming. -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
Boston Strong: Marc Mysterio Flo Rida Team on Charity Release (Preview Here)
Marcnbsp;Mysterionbsp;amp; Flonbsp;Ridanbsp;Team Up On Charitable Exclusive Release to Benefit lsquo;One Fund Bostonrsquo; (Marathon Bombing Victims) BOSTON, JUNEnbsp;7h, 2013/WCR/nbsp;Globe-Trotting DJ/Producer Marcnbsp;Mysterionbsp;teams up with Flonbsp;Ridanbsp;on a release for charity entitled lsquo;Booty On The Floorrsquo;. The Song will be available Monday, exclusively onnbsp;Beatport. All net proceeds from the Beatport Release will go to the families affected by the Tragic April 15th Marathon Attack in Boston via OneFundBoston.org, a charity set up by Massachusetts Governor Deval Patrick and Boston Mayor Thomas Menino. ldquo;God Bless the families affected by the Boston Marathon Explosion, I#39;m praying for you allrdquo; notes Flo Rida, via Twitter. The catchy refrain goes, #39;Put your Booty on the Floor#39;nbsp;(sampled from Flo Rida#39;s #39;Respirator#39; under license from Atlantic Records and Rhino Entertainment, companies of Warner Music Group) which is accompanied by a melodic arpeggio piano riff and a massive electro lead. ldquo;For me, lsquo;Put Your Booty On The Floorrsquo; is a paraphrased way to say lsquo;Call to actionrsquo; and lsquo;get in gearrsquo; which honors the first responders in Boston, as well as those whom acted on impulse to care for the wounded. By supporting them now, we are getting our collective booties lsquo;On The Floorrsquo;rdquo;nbsp;notes Marc Mysterio, whom himself lived in Boston for many years. A promotional video to push the charitable effort and song was posted on YouTube this morning featuring Bangkok-Based Viral Tutting Star Billy Chuchat. nbsp; The YouTube Video for lsquo;Booty On The Floorrsquo; has been monetized and all revenue earned from views of it via YouTube will go to One Fund Boston as well. Therefore, please view the video and share/re-post it everywhere to give to the families in need by watching the song#39;s Video: http://www.youtube.com/watch?v=FLoeU5DH1Y8 nbsp; People can support the effort by tweeting #bootyonthefloornbsp;with the link of the YouTube Video below. nbsp; Complimentary Copies of #39;Booty On The Floor#39; for Media and DJs are available upon request. nbsp; FOR MORE INFORMATION: Claude Lapointe World Class PR press...@gmail.com Follow Marc Mysterionbsp;on his New Twitter (old one was hacked) www.twitter.com/marc_mysterio Marc Mysterio Media Photo Available here: http://img.allvoices.com/thumbs/event/609/480/98601066-marc-mysterio.jpg nbsp; Marc Mysterio Profile/Bio on Sony Music http://tinyurl.com/mnn3cmn nbsp; Direct Donations Can be made to www.onefundboston.org copy; MARC MYSTERIO Customer Support | Privacy Policy | Terms of Service Please do not reply to this email. This is an outbound e-mail only and replies will not be responded to or reviewed. You may unsubscribe from the MARC MYSTERIO email list at any time. This email was sent with the Topspin Platform by MARC MYSTERIO. 1538 20th Street, Santa Monica CA 90404 ___ 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: Conversion to new options framework over
On Fri, Jun 07, 2013 at 04:49:56PM -0400, Jim Trigg wrote: On Fri, Jun 07, 2013 at 08:09:30PM +0100, Chris Rees wrote: On 7 June 2013 18:55, Jim Trigg jtr...@spamcop.net wrote: On Thu, Jun 06, 2013 at 08:45:10AM +0200, Baptiste Daroussin wrote: The compatibility code to parse the WITH/WITHOUT entries in make.conf will be removed in 6 months either. Do not forget to convert your configuration (make.conf, portsconf etc). A reminder will be send a month before the removal of the compatibility code. It would be useful to provide a pointer to instructions for doing so -- what exactly replaces WITH/WITHOUT entries in make.conf? For example, my dedicated server has WITHOUT_X11=yes in /etc/make.conf because it's headless and doesn't run an X server. What should that become? I tried googling, and the github doc page's only mention of make.conf is to add WITH_PKGNG=yes. Likewise the FreeBSD Handbook. The wiki apparently just points to the Handbook. WITH_PKGNG is not a classical OPTION, because it doesn't apply to any port in particular. I hadn't meant to refer to that as one of the WITH_ options that needed to be changed... There is some documentation for users at [1], basically you need to change any WITH_ variables to OPTIONS_SET=, and WITHOUT_ to OPTIONS_UNSET=. I'll hopefully find some time soon to get it in the Handbook For example; WITHOUT_X11=yes WITH_CUPS=yes WITHOUT_PULSEAUDIO=yes becomes OPTIONS_SET=CUPS OPTIONS_UNSET=PULSEAUDIO X11 That works for binary options, but what about version options? E.g., WITH_BDB_VER=47 ... Thanks, Jim those haven't been touched no change for them regards, Bapt pgpU74k0pmcR4.pgp Description: PGP signature
Re: FreeBSD ports which are currently scheduled for deletion
On 8/06/2013 4:42 AM, Joseph Mingrone wrote: Hi; lini...@freebsd.org writes: The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: sysutils/sge62 description:Sun Grid Engine, a batch queueing system maintainer: po...@freebsd.org deprecated because: Ancient and unsupported release expiration date:2013-03-01 build errors: http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.10.20130313090402.pointyhat/sge-6.2.2.1_3.log (Mar 14 02:20:26 UTC 2013) overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutilsportname=sge62 Our group relies heavily on this port and it compiles and works for us. Is it possible to reconsider this removal? I don't see an alternative in the ports tree? Hi Joseph, A good first-order bet is to submit a PR with patch offering to take maintainership, and looking at addressing the build with clang failure here: http://portsmon.freebsd.org/portoverview.py?category=sysutilsportname=sge62 Koobs ___ 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: How to build openjdk7 for customized FreeBSD system
I did this in a stupid way. I am sending this out in case someone met the same problem (or to say, you want to build openjdk on an platform that have no older version of JDK supported). The main idea is, firstly find a generic FreeBSD 8.2 system, build the openjdk7 package (well, there is no problem on generic system, as long as you are using the port collections corresponding to that specific version I suppose). Then, we can leverage all the Java-built output (includes *.class, *.jar, and some *.java/*.[ch] if they are auto-generated by the build system using JVM) in the generic systems, replacing all the $(JAVAC_CMD) and $(JAVAH_CMD) lines in Makefiles with something like (or we can try direct copy of the object files, but sometimes we still need to do this since the dependencies of 'make' are not the JAR files sometimes): scp $GENERIC_BSD:$JAR_FILE_PATH $PRIVATE_BSD:$JAR_FILE_PATH Or to say, we do fetch the good 'jar' from the generic systems instead of invoking a sick JVM and build it until we met error and stop the make process. I suppose all these things need some knowledge on the Makefile structure of openjdk. This is nasty work, but it did work for us. Another solution I thought about is cross-compile the whole JDK on a generic system, and copy all the private C libraries on the private system to the generic one before-hand (this may only be working when the generic system has cross-toolchain I suppose, or in my case that the two systems are using the same CPU arch). Just an idea, no need to try currently. Hope it helps. Thanks. Peter On Tue, Jun 4, 2013 at 4:44 PM, Xu Zhe xzpe...@gmail.com wrote: Hi, all, I have posted several mails in the list, asking for different kinds of build errors when I met during the process of building openjdk7 on a customized FreeBSD 8.2 system. Today I found the root cause of all the problems. That is, the system needs one initial bootstrap Java SDK to build the openjdk7, but the tragedy is that, *all* the bootstrap JDKs are binaries. These binaries could run on our system, but will met strange issue since the system is heavily hacked in the kernel and libc part, and it's never generic at all. So here is the problem... I will never have a working Java environment as the bootstrap JDK on the hacked system. I need another generic system to help, who has a good working JDK. So please ignore all the strange errors I posted. Now I want to ask a more generic question, which I suppose is the only way to finish my porting work: How should I build all the C codes in openjdk7 on my hacked system, while build the rest Java codes on another system? Thanks in advance! Peter ___ 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
REWARD for working pam_mount
The /usr/ports/sysutils/pam_mount port is broken, because it's expecting an older version of libHX. I'd really like to have a working pam_mount, and am willing to paypal US $50 over to the first person who gets it working. I'm not subscribed to the list, so please email me directly to claim the prize. ___ 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: REWARD for working pam_mount
On 8/06/2013 1:57 PM, Janet Sullivan wrote:
The /usr/ports/sysutils/pam_mount port is broken, because it's
expecting an older version of libHX. I'd really like to have a
working pam_mount, and am willing to paypal US $50 over to the first
person who gets it working. I'm not subscribed to the list, so
please email me directly to claim the prize.
Janet,
Your offer is commendable but unnecessary :)
Try this patch I just created (cherry picked from upstream), and let me
know how it goes. You'll want to apply it to the pam_mount port directory.
There's also something you can do to ensure pam_mount will work going
forward:
I had to backport the fix because the new pam_mount 2.13 version
requires libmount. Let upstream know that FreeBSD doesn't have libmount,
and request they make it optional and configurable (--without-libmount
configure option for example), even if it disables certain functionality.
If it works for you, let me know so I can commit the change, and feel
free to consider donating to the FreeBSD Foundation instead
Koobs
Index: Makefile
===
--- Makefile(revision 320195)
+++ Makefile(working copy)
@@ -14,7 +14,7 @@
MAINTAINER=g...@freebsd.org
COMMENT= A PAM that can mount volumes for a user session
-LIB_DEPENDS= HX.27:${PORTSDIR}/lang/libhx
+LIB_DEPENDS= HX:${PORTSDIR}/lang/libhx
USE_GNOME= pkgconfig libxml2
USE_PERL5= yes
Index: files/patch-commit335500
===
--- files/patch-commit335500(revision 0)
+++ files/patch-commit335500(working copy)
@@ -0,0 +1,144 @@
+# Patch for commit 33550036cb0c9311c9dc4da9b3b359435319420e (pam-mount)
+# Log: src: update for libHX 3.12
+# Authored by: Jan Engelhardt 2011-12-02
+
+--- ./configure.ac.orig2011-10-06 22:48:08.0 +1100
./configure.ac 2013-06-08 14:52:22.855624000 +1000
+@@ -63,7 +63,7 @@
+ AM_CONDITIONAL([HAVE_MDIO], [test x$ac_cv_header_sys_mdioctl_h = xyes])
+ AM_CONDITIONAL([HAVE_VND], [test x$ac_cv_header_dev_vndvar_h = xyes])
+
+-PKG_CHECK_MODULES([libHX], [libHX = 3.10.1])
++PKG_CHECK_MODULES([libHX], [libHX = 3.12])
+ PKG_CHECK_MODULES([libxml], [libxml-2.0 = 2.6])
+
+ AC_ARG_WITH(
+--- ./src/autoloop.c.orig 2011-10-06 22:48:08.0 +1100
./src/autoloop.c 2013-06-08 14:45:47.846247000 +1000
+@@ -54,7 +54,8 @@
+ HXOPT_AUTOHELP,
+ HXOPT_TABLEEND,
+ };
+- if (HX_getopt(options_table, argc, argv, HXOPT_USAGEONERR) = 0)
++ if (HX_getopt(options_table, argc, argv, HXOPT_USAGEONERR) !=
++ HXOPT_ERR_SUCCESS)
+ return false;
+ if (*argc != 2) {
+ fprintf(stderr, Usage: %s file\n, HX_basename(**argv));
+--- ./src/ehd.c.orig 2011-10-06 22:48:08.0 +1100
./src/ehd.c2013-06-08 14:46:27.56654 +1000
+@@ -526,7 +526,8 @@
+ HXOPT_TABLEEND,
+ };
+
+- if (HX_getopt(options_table, argc, argv, HXOPT_USAGEONERR) = 0)
++ if (HX_getopt(options_table, argc, argv, HXOPT_USAGEONERR) !=
++ HXOPT_ERR_SUCCESS)
+ return false;
+
+ pg-interactive = isatty(fileno(stdin));
+--- ./src/misc.c.orig 2011-10-06 22:48:08.0 +1100
./src/misc.c 2013-06-08 14:47:27.515576000 +1000
+@@ -159,7 +159,7 @@
+ {
+ char *filled;
+
+- if (HXformat2_aprintf(vinfo, filled, arg) == 0)
++ if (HXformat_aprintf(vinfo, filled, arg) == 0)
+ /*
+* This case may happen with e.g. %(before=-o OPTIONS) where
+* OPTIONS is empty. And options expanding to nothing are
+--- ./src/mount.c.orig 2011-10-06 22:48:08.0 +1100
./src/mount.c 2013-06-08 14:47:54.65561 +1000
+@@ -487,7 +487,7 @@
+ string = HXmc_meminit(NULL, 0);
+
+ for (i = config-command[CMD_FSCK]-first; i != NULL; i = i-next) {
+- if (HXformat2_aprintf(vinfo, current, i-ptr) 0) {
++ if (HXformat_aprintf(vinfo, current, i-ptr) 0) {
+ HXmc_strcat(string, current);
+ HXmc_strcat(string, );
+ }
+--- ./src/mtab.c.orig 2011-10-06 22:48:08.0 +1100
./src/mtab.c 2013-06-08 14:48:18.965526000 +1000
+@@ -138,7 +138,7 @@
+ l0g(HX_dirname: %s\n, strerror(errno));
+ return -errno;
+ }
+- ret = HX_mkdir(dirname);
++ ret = HX_mkdir(dirname, S_IRUGO | S_IXUGO | S_IWUSR);
+ free(dirname);
+ if (ret 0) {
+ l0g(HX_mkdir: %s\n, strerror(-ret));
+--- ./src/mtcrypt.c.orig 2011-10-06 22:48:08.0 +1100
./src/mtcrypt.c2013-06-08 14:49:23.036264000 +1000
+@@ -185,7 +185,8 @@
+ bool kfpt;
+ int ret;
+
+- if (HX_getopt(options_table, argc, argv, HXOPT_USAGEONERR) = 0)
++
