Re: New OPTIONS and make.conf knobs
On Sun, Jun 03, 2012 at 04:28:16PM -0700, Doug Barton wrote:
My understanding is that one of the benefits of the new OPTIONS
framework is that it's supposed to take make.conf knobs into account
when displaying the options dialog.
yes it is if you use the new way of setting KNOBS aka a general:
OPTIONS_UNSET= NLS
WITHOUT_NLS is not triggered as a compatibility from bsd.options.mk to
OPTIONS_UNSET= NLS while NOPORTDOCS and NOPORTEXAMPLES are.
I have WITHOUT_NLS defined in make.conf, but when I started an upgrade
today for x11-toolkits/libxfce4gui the dialog came up with all options
chosen (DOCS, NLS, STARTUP) even though I have the make.conf knob, and
the following in the existing options file:
_OPTIONS_READ=libxfce4gui-4.8.1
WITHOUT_NLS=true
WITH_STARTUP=true
WITH_GLADEUI=true
WITHOUT_APIDOCS=true
if you have an existing options file then the priority is set to what is in that
options file.
The priority is set that way:
1/ the options from the bsd.options.mk if any
2/ the default options chosen by the maintainer
3/ the options set in make.conf (OPTIONS_SET/OPTIONS_UNSET)
4/ the options set per port in make.conf (${UNIQUENAME}_SET/${UNIQUENAME}_UNSET)
5/ the options from the options file with 2 way of loading: them:
- the old one figuring out the informations WITH_/WITHOUT_
- the new one: just hit ok on the dialog and have a look at the file it has
changed.
The fact that the STARTUP option is still enabled is fine, although I
suspect it's probably a side effect. The fact that the other 2 options
are showing as enabled is a bug. In the case of NLS, it's likely at
least 2 different bugs.
In my mind the NLS case is a single bug, the loading of old saved optionfile
which doesn't work as expected. I'll have a look, thanks for reporting
FWIW, this showed up using portmaster, which runs 'make
config-conditional' by default.
Doug
regards,
Bapt
pgpXZyQ7y98UH.pgp
Description: PGP signature
Re: New OPTIONS and make.conf knobs
On Sun, Jun 03, 2012 at 11:12:17PM -0400, Thomas Mueller wrote: from Doug Barton do...@freebsd.org: My understanding is that one of the benefits of the new OPTIONS framework is that it's supposed to take make.conf knobs into account when displaying the options dialog. I have WITHOUT_NLS defined in make.conf, but when I started an upgrade today for x11-toolkits/libxfce4gui the dialog came up with all options chosen (DOCS, NLS, STARTUP) even though I have the make.conf knob, and the following in the existing options file: _OPTIONS_READ=libxfce4gui-4.8.1 WITHOUT_NLS=true WITH_STARTUP=true WITH_GLADEUI=true WITHOUT_APIDOCS=true The fact that the STARTUP option is still enabled is fine, although I suspect it's probably a side effect. The fact that the other 2 options are showing as enabled is a bug. In the case of NLS, it's likely at least 2 different bugs. FWIW, this showed up using portmaster, which runs 'make config-conditional' by default. Doug I just an hour ago ran portsnap fetch update to see what new would show in UPDATING file. I too have questions about how to use the new OPTIONS framework. Could you run as BATCH? Yes you can, another possibility if you don't like the dialog UI but still want the other possible interractions then just provide NO_DIALOG=true in /etc/make.conf NetBSD pkgsrc, ported to other mostly (quasi-)Unix OSes in addition to NetBSD, reads options in mk.conf, usually in directory /etc , You can do the same with the new OPTIONS framework: OPTIONS_SET= VORBIS # enable vorbis options everywhere OPTIONS_UNSET= NLS # disable NLS on all your ports zsh_SET= PCRE # enable PCRE only for zsh zsh_UNSET= DOCS # disable docs in the case of zsh There are no FreeBSD-ports-style dialogs with pkgsrc. I have used pkgsrc only with NetBSD. I would like to know how to get a log with a portmaster upgrade, such as portmaster -r png- (why the hyphen at the end?) without the log getting messed up by an OPTIONS dialog if I use tee or script. NO_DIALOG=yes in make.conf and you can run portmaster without getting messge up by an OPTIONS dialog If I specify in /etc/portmaster.conf, PM_LOG=/var/tmp/portmaster.log (for instance), would every run of portmaster log everything I see racing by on the screen to this file? If so, I might want to move/rename this file after each portmaster run so I can see which log goes with which ports. I've run man portmaster repeatedly each time looking for something I might have previously missed. I also looked at the Porter's Handbook online. regards, Bapt pgplyrNkRnrDh.pgp Description: PGP signature
Re: Why Are You NOT Using FreeBSD?
Hello. I wish we could use FreeBSD as basic platform, but it is not possible. We met several problems which led to mass migration to Debian. First of all, hardware support. EMC multipath was not supported by FreeBSD 8, and it was a necessary thing in our environment. We tried to use custom patches, but met wired boot0 behavior - it randomly hung. We were interested in VNET jails to have separate network stack for a jail, but they were not stable enough. And the last thing - there were no means of resource control to prevent malfunctioning jail to influence badly the whole system. So, we moved our infrastructure to OpenVZ/Debian and got all this plus possibility of live migration for containers and easy binary package management. -- Best regards, Alexander Pyhalov, system administrator of Computer Center of Southern Federal University ___ 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: New OPTIONS and make.conf knobs
On Mon, Jun 04, 2012 at 08:03:50AM +0200, Baptiste Daroussin wrote:
On Sun, Jun 03, 2012 at 04:28:16PM -0700, Doug Barton wrote:
My understanding is that one of the benefits of the new OPTIONS
framework is that it's supposed to take make.conf knobs into account
when displaying the options dialog.
yes it is if you use the new way of setting KNOBS aka a general:
OPTIONS_UNSET=NLS
WITHOUT_NLS is not triggered as a compatibility from bsd.options.mk to
OPTIONS_UNSET= NLS while NOPORTDOCS and NOPORTEXAMPLES are.
I have WITHOUT_NLS defined in make.conf, but when I started an upgrade
today for x11-toolkits/libxfce4gui the dialog came up with all options
chosen (DOCS, NLS, STARTUP) even though I have the make.conf knob, and
the following in the existing options file:
_OPTIONS_READ=libxfce4gui-4.8.1
WITHOUT_NLS=true
WITH_STARTUP=true
WITH_GLADEUI=true
WITHOUT_APIDOCS=true
if you have an existing options file then the priority is set to what is in
that
options file.
The priority is set that way:
1/ the options from the bsd.options.mk if any
2/ the default options chosen by the maintainer
3/ the options set in make.conf (OPTIONS_SET/OPTIONS_UNSET)
4/ the options set per port in make.conf
(${UNIQUENAME}_SET/${UNIQUENAME}_UNSET)
5/ the options from the options file with 2 way of loading: them:
- the old one figuring out the informations WITH_/WITHOUT_
- the new one: just hit ok on the dialog and have a look at the file it has
changed.
The fact that the STARTUP option is still enabled is fine, although I
suspect it's probably a side effect. The fact that the other 2 options
are showing as enabled is a bug. In the case of NLS, it's likely at
least 2 different bugs.
In my mind the NLS case is a single bug, the loading of old saved optionfile
which doesn't work as expected. I'll have a look, thanks for reporting
FWIW, this showed up using portmaster, which runs 'make
config-conditional' by default.
Doug
regards,
Bapt
btw the new options framework only reads and convert the WITHOUT/WITH stuff from
optionsfile in case the old option framework is still in used in the ports.
Which is no more the case libxfce4gui.
I am open to suggestions here on how to do better things here.
regards,
Bapt
pgpokNQDcF6oc.pgp
Description: PGP signature
Re: Stop in /usr/ports/devel/qt4-makeqpf
2012-06-04 07:25, Leslie Jensen skrev: During the png- upgrade I now hit another obstacle. What can I do to remedy it? Thanks /Leslie devel/qt4-makeqpf:make reinstall === Patching for qt4-makeqpf-4.8.2 === Applying extra patch /usr/ports/devel/qt4-makeqpf/../../devel/qt4/files/patch-configure Ignoring previously applied (or reversed) patch. 5 out of 5 hunks ignored--saving rejects to ./configure.rej *** Error code 5 Stop in /usr/ports/devel/qt4-makeqpf. *** Error code 1 Stop in /usr/ports/devel/qt4-makeqpf ___ 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 This port has no ports that are dependent on it. At least not on my system. So I just skipped past it and all other ports has upgraded nicely :-) /Leslie ___ 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
XFCE errors
I'm getting these errors on the screen when I quit xfce: I do have dbus installed. --- (xfdesktop:37212): GLib-GObject-WARNING **: invalid cast from `XfdesktopWindowIc onManager' to `XfdesktopFileIconManager' (xfce4-session:37195): GLib-WARNING **: GError set over the top of a previous GE rror or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Failed to connect to socket /var/run/dbus/sys tem_bus_socket: Filen eller katalogen finns ej (xfce4-session:37195): GLib-WARNING **: GError set over the top of a previous GE rror or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. --- ___ 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: New OPTIONS and make.conf knobs
There is another problem with options and portmaster. I have WITHOUT_X11=yes in make.conf and if I try to install emulators/virtualbox-ose for the first time it immediately ends with error message instead of showing options dialog. # portmaster emulators/virtualbox-ose === Currently installed version: virtualbox-ose-4.1.16 === Port directory: /usr/ports/emulators/virtualbox-ose === This port is marked BROKEN === QT4 frontend requires X11 support. Run 'make config' again! === If you are sure you can build it, remove the BROKEN line in the Makefile and try again. Terminated I don't know the order of processing options / knobs so I don't know if this is the problem of portmaster, OPTIONSng or Makefile it-self. To fix this problem, I must manually run `make config` in ports directory and uncheck QT4, then run portmaster again. Miroslav Lachman ___ 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: Why Are You NOT Using FreeBSD?
On 6/3/12, Erich erichfreebsdl...@ovitrap.com wrote: ... On 03 June 2012 PM 1:12:38 b. f. wrote: On 03 June 2012 PM 5:42:55 Adam Strohl wrote: On 6/3/2012 17:24, Etienne Robillard wrote: ... With regard to your request for a versioned Ports trees -- well, we have had that for about 18 years, since the Ports tree is kept under version control in CVS, and you are free to check out snapshots using anonymous CVS or CVSup -- all you have to do is specify a tag or date I would not know for what tag I would have to go to solve a specific Problem. Here we encounter a problem with your argument: it is unlikely that your hypothetical helpless beginner would know what to do with a versioned ports tree, even if he or she knew that it does in fact exist. Any such person who requires reliability should really be using binary packages and binary base-system updates prepared by someone else, and not compiling from source. There have been considerable improvements on this front, with freebsd-update and pkgng ( http://wiki.freebsd.org/pkgng ). If you want to help, you should become familiar with these, and suggest concrete changes that you think would assist your beginner. Returning to your question: a common-sense answer would be to fall back to the last-known suitable Ports tree snapshot -- or to the snapshot distributed with the last release, or the release that you are using. To use the ports tree snapshot distributed with a particular release, use the ports (not the src!) release tags as described in: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html (Here the description could be changed to avoid confusion -- the list of specific release tags could be changed to indicate that they are src release tags only, as briefly described in the first paragraph of A.7.2, and the corresponding ports release tags could be added.) For example, in order to obtain the ports tree corresponding to the 8.3 release, use: tag=RELEASE_8_3_0 instead of the usual tag=. in a ports sup file (a comment to that effect could be added to src/share/examples/cvsup/ports-supfile) -- or use the corresponding -r option with cvs(1).The available tags are also visible through the pull-down Show only files with tag menu at the web interface: http://www.freebsd.org/cgi/cvsweb.cgi/ports/ and of course someone who is familiar with CVS could find them. The tag is one kind of version number. The other kind of version number that is available is a date spec -- for csup(1) this takes the form: [cc]yy.mm.dd.hh.mm.ss where the abbreviations represent the usual century. year, month, day, hour, minute, and second. To use this, just add a date=... line in your sup file, to replace or supersede any tag=... line. So, for example, to fetch the ports tree as it was immediately before the png update, determine the time of the png update (for example, via the cvsweb interface above, or freshports [ http://www.freshports.org ] or freshbsd [ http://www.freshbsd.org ] or the cvs-ports mailing list [ http://lists.freebsd.org/pipermail/cvs-ports/ ], or by looking at the revision time-stamp in ports/graphics/png/Makefile), and then substitute: date=2012.06.01.05.10.00 (that is, a few minutes before the png update) for the usual tag=. in a ports sup file -- or use the corresponding -D option with cvs(1). If these procedures aren't explained in great detail in the handbook or manpages, even though the tags and date specs are defined, it is probably because we assume that people who want to build specific revisions of ports from source, and who are able to do so, already have some familiarity with VCS. ... And you are, of course, free to use FreeBSD with other packaging They will feel to be free to use Windows. They can feel free to use whatever they please: I was only pointing out that using FreeBSD does not require the use of FreeBSD Ports. ... As far as your example from your other message about having to combine a png update with work over the course of a weekend -- I don't know why you would be fooling around with an update of your Ports tree or your installed ports while working under a tight deadline, but if you have backups, you should be able to recover from most problems fairly quickly. Because it is written in the handbook? Because it is common-sense to have back-ups if you require reliability. But if you feel that this should be explicitly mentioned in the handbook, submit some suggestions for changes or additions to the document committers. At least some time ago the handbook stated to update the ports tree before installing new ports. The new comer will do this and then get stuck. Do not forget that I am not talking here for people who know what they are doing, I am talking about a hurdle newcomers are facing or people who just want to use a computer as a tool. Again, a true novice who requires reliability ought to be using packages, and or get someone else to manage his
Re: Why Are You NOT Using FreeBSD?
Hi, On 04 June 2012 12:08:14 Adam Strohl wrote: On 6/4/2012 4:23, Erich Dollansky wrote: On 03 June 2012 PM 11:41:12 Adam Strohl wrote: On 6/3/2012 19:19, Erich Dollansky wrote: do a simple thing. Install a naked 8.3, 9.0 or 10.0 on a fresh hard disk. Get then the ports tree and start compiling X. I did not get a running system since at least 2007 when I did this. There was always at least one manual intervention needed. I did this the last time in the first week of May. Yes, I know how to fix this. Yes, I reported things like this at the beginning. After getting always the answer that it is working on my machine, I stopped reporting it. Just built a VM and installed 9.0-R from the ISO. Installed gnu-screen and bash (from ports). you did not compile it as the first item. I don't understand what you are saying. I did a 'make install' on a clean system with only bash and screen installed (I did update ports first). yes, you installed bash and screen first. Can you try it without? I really try to install X as the first thing after I finished installation. I wonder why you need bash from the ports at that stage? If this still works for you, I will have to install FreeBSD after my return. This will take some weeks. It could even be that my journey will get extended. So, be patient. Erich ___ 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
Current problem reports assigned to po...@freebsd.org
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o ports/168328 ports [REPOCOPY] devel/codeblocks -- devel/codeblocks-devel 1 problem total. ___ 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: New OPTIONS and make.conf knobs
On 04.06.2012 11:55, Miroslav Lachman wrote: There is another problem with options and portmaster. I have WITHOUT_X11=yes in make.conf and if I try to install emulators/virtualbox-ose for the first time it immediately ends with error message instead of showing options dialog. # portmaster emulators/virtualbox-ose === Currently installed version: virtualbox-ose-4.1.16 === Port directory: /usr/ports/emulators/virtualbox-ose === This port is marked BROKEN === QT4 frontend requires X11 support. Run 'make config' again! === If you are sure you can build it, remove the BROKEN line in the Makefile and try again. Terminated I don't know the order of processing options / knobs so I don't know if this is the problem of portmaster, OPTIONSng or Makefile it-self. To fix this problem, I must manually run `make config` in ports directory and uncheck QT4, then run portmaster again. That is not a bug at all. It was that way for the last 2 years and still is. The virtualbox ports do not use the new optionsng stuff yet and the problem that you are seeing is just because QT4 GUI without X11 doesn't make sense. If you don't want X11 you also don't want QT4. -- Bernhard Froehlich http://www.bluelife.at/ ___ 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: New OPTIONS and make.conf knobs
Bernhard Froehlich wrote: On 04.06.2012 11:55, Miroslav Lachman wrote: There is another problem with options and portmaster. I have WITHOUT_X11=yes in make.conf and if I try to install emulators/virtualbox-ose for the first time it immediately ends with error message instead of showing options dialog. # portmaster emulators/virtualbox-ose === Currently installed version: virtualbox-ose-4.1.16 === Port directory: /usr/ports/emulators/virtualbox-ose === This port is marked BROKEN === QT4 frontend requires X11 support. Run 'make config' again! === If you are sure you can build it, remove the BROKEN line in the Makefile and try again. Terminated I don't know the order of processing options / knobs so I don't know if this is the problem of portmaster, OPTIONSng or Makefile it-self. To fix this problem, I must manually run `make config` in ports directory and uncheck QT4, then run portmaster again. That is not a bug at all. It was that way for the last 2 years and still is. The virtualbox ports do not use the new optionsng stuff yet and the problem that you are seeing is just because QT4 GUI without X11 doesn't make sense. If you don't want X11 you also don't want QT4. Yes, that's right. But I am confused why portmaster does not show the options dialog to let user uncheck QT4? What I expect is: - run portmaster - show dialog with unchecked X11 - let user uncheck QT4 - save options in /var/db/ports - show error about conflicting options Now is: - run portmaster - show error about conflicting options I don't know if it can be solved by portmaster, ports framework or anything else. Miroslav Lachman ___ 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: Why Are You NOT Using FreeBSD?
On 6/4/2012 18:07, Erich wrote: yes, you installed bash and screen first. Can you try it without? Doesn't tinderbox do this every night? I really try to install X as the first thing after I finished installation. I wonder why you need bash from the ports at that stage? Because that is what I use as my shell, and I use GNU Screen so if my connection terminates I can reattach. ___ 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: Why Are You NOT Using FreeBSD?
On 6/4/12 7:36 AM, Adam Strohl wrote: Doesn't tinderbox do this every night? And, as a committer, here is the point. We get reports of 'this doesn't build'. (no fixed attached, no logs, no indication of what was installed first, what options taken), we try to get information on what happended and just get 'I am just trying to tel lyou its broken, and I don't have time to tell you why, its your os, you fix it') want a link to a recient pr where that happened? So, we run it up in a tinderbox (for the newbie who wants this to work like windoes or linx , I will explain: A tinderbox is a special virtual chrooted (jail) envirnoment. The tinderbox creates a blank tree, with a free copy of FreeBSD (x), copies a free ports tree to it, and creates packages. (pkg_create). /generically/ it builds these with default options (since this is a batch process, that is all we can do). If the system can fetch the source, apply the patches, compile the program, package it, pulls in all the necessary LIB and BUILD depends and then deletes the packages without leaving any leftovers, we consider the package fine /with default options/ This is why we ask that the luser tell us what strange things they have in make.conf, recommend that they update their ports tree (since we are running with a free ports tree), and tell us what non standard options were selected. If we can't reproduce it, we can't fix it. Many times we find that the user did not update the ports according to the instructions in /usr/ports/UPDATING, which, for all language ports (python, perl, php), involve more then just 'portmaster php-') Once a ports tree is broken by (even a seemingly successful update), sometime down the road, something can and will rise up to byte[sic] you. Give us the billions and billions of $$ MS has and the minions they have and maybe we can spend a year between os releases (oh, and sorry, but MS has no ports tree, and if a third party product doesn't work, don't even call them, they will charge you $300 to tell you to go back to the manufacturer) -- Michael Scheidell, CTO *| * SECNAP Network Security Corporation d: +1.561.948.2259 w: http://people.freebsd.org/~scheidell ___ 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
net-im/skype-devel
Hi, I run 10-CURRENT r235646 and CVS updated ports (both from May, 19); skype-2.1.0.81,1 is working fine, uncluding viedo: the port net-im/skype-devel still says, that video is broken; is there some pre-view to test or to help debugging? thanks matthias -- Matthias Apitz Release Manager - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany tel +49-89-61308 351 - fax +49-89-61308 399 - mobile +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 - End forwarded message - -- Matthias Apitz e g...@unixarea.de - w http://www.unixarea.de/ 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: Why Are You NOT Using FreeBSD?
Hi, On 03 June 2012 23:03:47 Janketh Jay wrote: On 06/03/2012 08:50 PM, Erich Dollansky wrote: On 03 June 2012 PM 7:54:46 Janketh Jay wrote: a person who operated Windows for some years does not see him/herself as a newcomer but still fails on FreeBSD. The word goes around then that FreeBSD is bad. This is fine, actually. As mentioned, it's not intended for individuals that want everything handed to them on a silver platter. Anyone who labels FreeBSD as bad because they aren't familiar with it is an idiot, IMO. This isn't Microsoft, no matter how much people might want it to be. And, it never will be. Use this list if you have questions about ports. Is that really so difficult for people to do? If so, no big deal. The FreeBSD developers, contributors and maintainers are not here to hold people's hands. We're here to help people help themselves... how will you ever get newcomers to FreeBSD if not via Linux? Why should people running Linux switch to FreeBSD? This is a dangerous route. Did you forget how you started with FreeBSD? We don't need people from Linux to migrate to FreeBSD. There are plenty of others out there that simply want to try it. Generally, Linux users are very adamant about it. So, they continue to use it regardless of what else is out there. Same for Windows and Mac users. To each their own. If someone feels the need to check it out, the more the merrier. FreeBSD isn't in the business of sucking people in. Curiosity alone is enough to keep people using it. Especially when they find out how solid it is. As far as how I started using it, this had nothing to do with Linux. In fact, I used BSD before I even gave Linux a second thought. I was intrigued with the fact that many large businesses (Including Microsoft) used FreeBSD as their server OS. The rest is history. I began using it - I struggled - I read the Handbook - I asked questions. That's it. I'm extremely happy I did so and I can't fathom migrating my production systems to anything else. You are really working hard to keep the FreeBSD installations low. It does not help FreeBSD if it is believed to be an elite operating system. Linux is by no way less complex and still many more people us it. Why? FreeBSD *IS* an elite operating system. By elite I don't mean what most people will think I mean. I'm simply stating that it takes a reasonable amount of time to grow comfortable with it. Along with any UNIX-like OS. If it were really simple to use, everyone would be using it, right? This should not be a reason to make its use more difficult for beginners. What will happen to FreeBSD when there are not beginners anymore? You cannot ask people to learn first with other operating systems and then move to FreeBSD. At least I can still claim that I learned with BSD at the university. This is even the main reason for using FreeBSD. I do not understand why people get pushed away instead of offering them a helping hand. This is at least what I do whenever possible. There will always be beginners. People are curious. That's how everything gets it's start. Well, besides Microsoft who was basically the only supplier of personal computers in the beginning. No one is asking anyone to learn something else first. People can come straight to FreeBSD (or any BSD for that matter) directly out of the womb. However, expecting hand-holding is something that simply isn't going to happen. In fact, I've RTFM so many times it makes me sick. But, that sickness has turned into a love. It's all about solidity, man! Curiosity kills every cat. :) There is no reason to assume that people get pushed away from using FBSD. There are plenty of resources out there where people have gone above and beyond to help n00bs out. There is how-to for almost anything! On top of that, the forums and mailing lists are STILL helping people that refuse to RTFM. There are exponential amounts of help out there. If people aren't willing to learn, that's where the problem ensues. And Linux, as far as I'm concerned is more complex than FreeBSD. I would not use the word complex, I use the word chaotic. I can agree with chaotic... Especially it's package management. I don't like the idea of having no choices when I install an application. Of course, I could go WAY out This depends very much on the distribution. This even changes very fast from release to release. The release changes are actually what drive me the most nuts. I can't remember the last time I was able to update a Debian or Ubuntu release without having to do SERIOUS work to make it function the same as before. I don't like dealing with that. of my way to create, build, and install an SRPM, but bugger that! It's not easy! Linux is only thought of as easy because of the graphical
Re: New OPTIONS and make.conf knobs
On 04.06.2012 13:29, Miroslav Lachman wrote: Bernhard Froehlich wrote: On 04.06.2012 11:55, Miroslav Lachman wrote: There is another problem with options and portmaster. I have WITHOUT_X11=yes in make.conf and if I try to install emulators/virtualbox-ose for the first time it immediately ends with error message instead of showing options dialog. # portmaster emulators/virtualbox-ose === Currently installed version: virtualbox-ose-4.1.16 === Port directory: /usr/ports/emulators/virtualbox-ose === This port is marked BROKEN === QT4 frontend requires X11 support. Run 'make config' again! === If you are sure you can build it, remove the BROKEN line in the Makefile and try again. Terminated I don't know the order of processing options / knobs so I don't know if this is the problem of portmaster, OPTIONSng or Makefile it-self. To fix this problem, I must manually run `make config` in ports directory and uncheck QT4, then run portmaster again. That is not a bug at all. It was that way for the last 2 years and still is. The virtualbox ports do not use the new optionsng stuff yet and the problem that you are seeing is just because QT4 GUI without X11 doesn't make sense. If you don't want X11 you also don't want QT4. Yes, that's right. But I am confused why portmaster does not show the options dialog to let user uncheck QT4? What I expect is: - run portmaster - show dialog with unchecked X11 - let user uncheck QT4 - save options in /var/db/ports - show error about conflicting options Now is: - run portmaster - show error about conflicting options I don't know if it can be solved by portmaster, ports framework or anything else. From the BROKEN message: QT4 frontend requires X11 support. Run 'make config' again! I think it will be fixed once virtualbox uses optionsng because it is able to handle such option dependencies but for now it's the same as it ever was. -- Bernhard Fröhlich http://www.bluelife.at/ ___ 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] Please convert your ports to new options framework
On 6/3/2012 1:44 PM, Baptiste Daroussin wrote: Hi, The new options framework is now in the port for a week, most of the problems directly concerning the framework seems to have been addressed. regards, Bapt A common question I have seen is how to support 0 or 1 in the SINGLE list. You can achieve this by adding the SINGLE group to the OPTIONS_DEFINE. For example: OPTIONS_DEFINE= DB_OVERRIDE OPTIONS_SINGLE= DB_OVERRIDE OPTIONS_SINGLE_DB_OVERRIDE= BDB4 BDB1 OPTIONS_DEFAULT=DB_OVERRIDE BDB4 DB_OVERRIDE_DESC= Override DB backend instead of default DBM BDB1_DESC= Use Berkeley DB 1 BDB4_DESC= Use Berkeley DB =2 Here DB_OVERRIDE must be selected to select either of BDB4 or BDB1. This gives you 0 or 1 on the BDB4/BDB1. Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
Re: New OPTIONS and make.conf knobs
On 4-6-2012 14:58, Bernhard Froehlich wrote:
On 04.06.2012 13:29, Miroslav Lachman wrote:
Bernhard Froehlich wrote:
On 04.06.2012 11:55, Miroslav Lachman wrote:
There is another problem with options and portmaster.
I have WITHOUT_X11=yes in make.conf and if I try to install
emulators/virtualbox-ose for the first time it immediately ends with
error message instead of showing options dialog.
# portmaster emulators/virtualbox-ose
=== Currently installed version: virtualbox-ose-4.1.16
=== Port directory: /usr/ports/emulators/virtualbox-ose
=== This port is marked BROKEN
=== QT4 frontend requires X11 support. Run 'make config' again!
=== If you are sure you can build it, remove the
BROKEN line in the Makefile and try again.
Terminated
I don't know the order of processing options / knobs so I don't know
if this is the problem of portmaster, OPTIONSng or Makefile it-self.
To fix this problem, I must manually run `make config` in ports
directory and uncheck QT4, then run portmaster again.
That is not a bug at all. It was that way for the last 2 years and still
is. The virtualbox ports do not use the new optionsng stuff yet and the
problem that you are seeing is just because QT4 GUI without X11 doesn't
make sense. If you don't want X11 you also don't want QT4.
Yes, that's right. But I am confused why portmaster does not show the
options dialog to let user uncheck QT4?
What I expect is:
- run portmaster
- show dialog with unchecked X11
- let user uncheck QT4
- save options in /var/db/ports
- show error about conflicting options
Now is:
- run portmaster
- show error about conflicting options
I don't know if it can be solved by portmaster, ports framework or
anything else.
From the BROKEN message:
QT4 frontend requires X11 support. Run 'make config' again!
I think it will be fixed once virtualbox uses optionsng because it is
able to handle such option dependencies but for now it's the same as
it ever was.
I think only the port can handle this as it falls in the sane defaults
category and a framework can never assess what is sane in the specific
port's case.
A solution that works with old options is to assign the On/Off state
with a variable:
.ifdef WITHOUT_X11
QT4_DEFAULT=off
.else
QT4_DEFAULT=on
.endif
OPTIONS=QT4 Enable QT4 support ${QT4_DEFAULT}
I think the same will work with optionsng and probably offers better
sanity checking as you can query for ${UNIQUENAME}_SET of a related
port, like OPENLDAP24_SASL_SET to set the default for ldap sasl support
accordingly instead of throwing an exception.
--
Mel
___
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: Stop in /usr/ports/devel/qt4-makeqpf
Leslie Jensen les...@eskk.nu writes: During the png- upgrade I now hit another obstacle. What can I do to remedy it? Thanks /Leslie devel/qt4-makeqpf:make reinstall === Patching for qt4-makeqpf-4.8.2 === Applying extra patch /usr/ports/devel/qt4-makeqpf/../../devel/qt4/files/patch-configure Ignoring previously applied (or reversed) patch. 5 out of 5 hunks ignored--saving rejects to ./configure.rej *** Error code 5 Stop in /usr/ports/devel/qt4-makeqpf. *** Error code 1 Stop in /usr/ports/devel/qt4-makeqpf `make patch' works just fine here. My guess is that you did not clean your work directory and the patch is then being applied to an already patched tree. ___ 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: Stop in /usr/ports/devel/qt4-makeqpf
Hi!
devel/qt4-makeqpf:make reinstall
=== Patching for qt4-makeqpf-4.8.2
=== Applying extra patch
/usr/ports/devel/qt4-makeqpf/../../devel/qt4/files/patch-configure
Ignoring previously applied (or reversed) patch.
5 out of 5 hunks ignored--saving rejects to ./configure.rej
*** Error code 5
Stop in /usr/ports/devel/qt4-makeqpf.
*** Error code 1
Stop in /usr/ports/devel/qt4-makeqpf
`make patch' works just fine here. My guess is that you did not clean
your work directory and the patch is then being applied to an already
patched tree.
Nope, happens where with 8.1 as well due to:
.if ${OSVERSION} 802502
EXTRA_PATCHES+= ${FILESDIR}/extra-patch-tools__makeqpf__qpf2.cpp
.endif
or so.
--
p...@opsec.eu+49 171 3101372 8 years to go !
___
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
Snort loggin
Hello. I've got a (little) problem with snort.. _ In /usr/local/etc/snort/snort.conf I have: output alert_syslog: LOG_SECURITY LOG_ALERT _ in /etc/syslog.conf: security.* /var/log/security auth.info /var/log/auth.log Yet all snort message go to /var/log/auth.log, not /var/log/security. Am I doing something wrong? Should I put something else in snort.conf? bye Thanks av. ___ 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: Why Are You NOT Using FreeBSD?
On 6/4/2012 18:36, Adam Strohl wrote: On 6/4/2012 18:07, Erich wrote: yes, you installed bash and screen first. Can you try it without? From a 100% clean install: - portsnap fetch extract update - compiled x-org + VMware driver No issues, works fine.
Re: Stop in /usr/ports/devel/qt4-makeqpf
Kurt Jaeger li...@opsec.eu writes:
Hi!
devel/qt4-makeqpf:make reinstall
=== Patching for qt4-makeqpf-4.8.2
=== Applying extra patch
/usr/ports/devel/qt4-makeqpf/../../devel/qt4/files/patch-configure
Ignoring previously applied (or reversed) patch.
5 out of 5 hunks ignored--saving rejects to ./configure.rej
*** Error code 5
Stop in /usr/ports/devel/qt4-makeqpf.
*** Error code 1
Stop in /usr/ports/devel/qt4-makeqpf
`make patch' works just fine here. My guess is that you did not clean
your work directory and the patch is then being applied to an already
patched tree.
Nope, happens where with 8.1 as well due to:
.if ${OSVERSION} 802502
EXTRA_PATCHES+= ${FILESDIR}/extra-patch-tools__makeqpf__qpf2.cpp
.endif
or so.
That doesn't seem to be the same problem reported by Leslie (the one you
mention was reportedly fixed by bapt@ a few days ago).
___
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
graphics/gdal 1.9.0 is broken again
After big update session from weekend, when trying to build graphics/gdal, I get the following messages: [...] gmake[2]: Entering directory `/usr/ports/graphics/gdal/work/gdal-1.9.0/frmts/gif' /bin/sh /usr/local/bin/libtool --mode=compile --tag=CXX c++ -O2 -pipe -O2 -fno-strict-aliasing -pipe -msse3 -Wall -I/usr/ports/graphics/gdal/work/gdal-1.9.0/port -I/usr/ports/graphics/gdal/work/gdal-1.9.0/gcore -I/usr/ports/graphics/gdal/work/gdal-1.9.0/alg -I/usr/ports/graphics/gdal/work/gdal-1.9.0/ogr -I/usr/ports/graphics/gdal/work/gdal-1.9.0/ogr/ogrsf_frmts -DOGR_ENABLED -I/usr/local/include -I/usr/ports/graphics/gdal/work/gdal-1.9.0/port -I/usr/local/include -I/usr/local -I/usr/local/include -I/usr/local/include -I/usr/local -I/usr/local/include -I/usr/local -I/usr/local/include -I/usr/local/include -I/usr/local/include -I/usr/local -I/usr/local/include -I/usr -I/usr/include -c -o ../o/gifdataset.lo gifdataset.cpp libtool: compile: c++ -O2 -pipe -O2 -fno-strict-aliasing -pipe -msse3 -Wall -I/usr/ports/graphics/gdal/work/gdal-1.9.0/port -I/usr/ports/graphics/gdal/work/gdal-1.9.0/gcore -I/usr/ports/graphics/gdal/work/gdal-1.9.0/alg -I/usr/ports/graphics/gdal/work/gdal-1.9.0/ogr -I/usr/ports/graphics/gdal/work/gdal-1.9.0/ogr/ogrsf_frmts -DOGR_ENABLED -I/usr/local/include -I/usr/ports/graphics/gdal/work/gdal-1.9.0/port -I/usr/local/include -I/usr/local -I/usr/local/include -I/usr/local/include -I/usr/local -I/usr/local/include -I/usr/local -I/usr/local/include -I/usr/local/include -I/usr/local/include -I/usr/local -I/usr/local/include -I/usr -I/usr/include -c gifdataset.cpp -fPIC -DPIC -o ../o/.libs/gifdataset.o gifdataset.cpp: In static member function 'static GDALDataset* GIFDataset::CreateCopy(const char*, GDALDataset*, int, char**, int (*)(double, const char*, void*), void*)': gifdataset.cpp:599: error: 'PrintGifError' was not declared in this scope gifdataset.cpp:625: error: 'PrintGifError' was not declared in this scope gmake[2]: *** [../o/gifdataset.lo] Fehler 1 gmake[2]: Leaving directory `/usr/ports/graphics/gdal/work/gdal-1.9.0/frmts/gif' gmake[1]: *** [gif-install-obj] Fehler 2 gmake[1]: Leaving directory `/usr/ports/graphics/gdal/work/gdal-1.9.0/frmts' gmake: *** [frmts-target] Fehler 2 *** [do-build] Error code 1 This also happens on pointyhat, eg: http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.7.20120603171103/gdal-1.9.0_1.log Could this be related to the update of graphics/giflib? Thanks for any help, Rainer Hurling ___ 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: Why Are You NOT Using FreeBSD?
Hi, On 04 June 2012 21:10:31 Adam Strohl wrote: On 6/4/2012 18:36, Adam Strohl wrote: On 6/4/2012 18:07, Erich wrote: yes, you installed bash and screen first. Can you try it without? From a 100% clean install: - portsnap fetch extract update - compiled x-org + VMware driver No issues, works fine. I was not that lucky. For 8.0, it was with the NVidea driver, in the first week of my, it was with 9.0 and the Intel driver. Let me arrive back home to have another try. Erich ___ 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: Why Are You NOT Using FreeBSD?
On 6/4/2012 21:59, Erich wrote: Hi, On 04 June 2012 21:10:31 Adam Strohl wrote: On 6/4/2012 18:36, Adam Strohl wrote: On 6/4/2012 18:07, Erich wrote: yes, you installed bash and screen first. Can you try it without? From a 100% clean install: - portsnap fetch extract update - compiled x-org + VMware driver No issues, works fine. I was not that lucky. For 8.0, it was with the NVidea driver, in the first week of my, it was with 9.0 and the Intel driver. Let me arrive back home to have another try. Sure, and if you do have issues post what the specific error and port is where it happened. ___ 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
Libreoffice, javaPathHelper: not found
I have just installed libreoffice-3.5.2_4 and are now getting the following error javaPathHelper: not found I understand that this error is known according to this tread http://forums.freebsd.org/showthread.php?t=27035 I'm wondering if there's any fix available? Regards /Leslie ___ 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: graphics/gdal 1.9.0 is broken again
On 04.06.2012 16:47 (UTC+2), Rainer Hurling wrote:
After big update session from weekend, when trying to build
graphics/gdal, I get the following messages:
[...]
gmake[2]: Entering directory
`/usr/ports/graphics/gdal/work/gdal-1.9.0/frmts/gif'
/bin/sh /usr/local/bin/libtool --mode=compile --tag=CXX c++ -O2 -pipe
-O2 -fno-strict-aliasing -pipe -msse3 -Wall
-I/usr/ports/graphics/gdal/work/gdal-1.9.0/port
-I/usr/ports/graphics/gdal/work/gdal-1.9.0/gcore
-I/usr/ports/graphics/gdal/work/gdal-1.9.0/alg
-I/usr/ports/graphics/gdal/work/gdal-1.9.0/ogr
-I/usr/ports/graphics/gdal/work/gdal-1.9.0/ogr/ogrsf_frmts -DOGR_ENABLED
-I/usr/local/include -I/usr/ports/graphics/gdal/work/gdal-1.9.0/port
-I/usr/local/include -I/usr/local -I/usr/local/include
-I/usr/local/include -I/usr/local -I/usr/local/include -I/usr/local
-I/usr/local/include -I/usr/local/include -I/usr/local/include
-I/usr/local -I/usr/local/include -I/usr -I/usr/include -c -o
../o/gifdataset.lo gifdataset.cpp
libtool: compile: c++ -O2 -pipe -O2 -fno-strict-aliasing -pipe -msse3
-Wall -I/usr/ports/graphics/gdal/work/gdal-1.9.0/port
-I/usr/ports/graphics/gdal/work/gdal-1.9.0/gcore
-I/usr/ports/graphics/gdal/work/gdal-1.9.0/alg
-I/usr/ports/graphics/gdal/work/gdal-1.9.0/ogr
-I/usr/ports/graphics/gdal/work/gdal-1.9.0/ogr/ogrsf_frmts -DOGR_ENABLED
-I/usr/local/include -I/usr/ports/graphics/gdal/work/gdal-1.9.0/port
-I/usr/local/include -I/usr/local -I/usr/local/include
-I/usr/local/include -I/usr/local -I/usr/local/include -I/usr/local
-I/usr/local/include -I/usr/local/include -I/usr/local/include
-I/usr/local -I/usr/local/include -I/usr -I/usr/include -c
gifdataset.cpp -fPIC -DPIC -o ../o/.libs/gifdataset.o
gifdataset.cpp: In static member function 'static GDALDataset*
GIFDataset::CreateCopy(const char*, GDALDataset*, int, char**, int
(*)(double, const char*, void*), void*)':
gifdataset.cpp:599: error: 'PrintGifError' was not declared in this scope
gifdataset.cpp:625: error: 'PrintGifError' was not declared in this scope
gmake[2]: *** [../o/gifdataset.lo] Fehler 1
gmake[2]: Leaving directory
`/usr/ports/graphics/gdal/work/gdal-1.9.0/frmts/gif'
gmake[1]: *** [gif-install-obj] Fehler 2
gmake[1]: Leaving directory
`/usr/ports/graphics/gdal/work/gdal-1.9.0/frmts'
gmake: *** [frmts-target] Fehler 2
*** [do-build] Error code 1
This also happens on pointyhat, eg:
http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.7.20120603171103/gdal-1.9.0_1.log
Could this be related to the update of graphics/giflib?
Sorry for answering myself. I just found that it is fixed upstream for
existing 1.9 branches and upcoming gdal 1.9.2 (trunk), see
http://trac.osgeo.org/gdal/ticket/4675
I attached a patch for our ports version 1.9.0, which should solve this
issue.
Thanks for any help,
Rainer Hurling
--- frmts/gif/gifdataset.cpp.orig 2012-01-04 08:03:28.0 +0100
+++ frmts/gif/gifdataset.cpp2012-06-04 17:21:24.0 +0200
@@ -470,6 +470,28 @@
}
//
+/*GDALPrintGifError() */
+//
+
+static void GDALPrintGifError(const char* pszMsg)
+{
+/* GIFLIB_MAJOR is only defined in libgif = 4.2.0 */
+/* libgif 4.2.0 has retired PrintGifError() and added GifErrorString() */
+#if defined(GIFLIB_MAJOR) defined(GIFLIB_MINOR) \
+((GIFLIB_MAJOR == 4 GIFLIB_MINOR = 2) || GIFLIB_MAJOR 4)
+/* Static string actually, hence the const char* cast */
+const char* pszGIFLIBError = (const char*) GifErrorString();
+if (pszGIFLIBError == NULL)
+pszGIFLIBError = Unknown error;
+CPLError( CE_Failure, CPLE_AppDefined,
+ %s. GIFLib Error : %s, pszMsg, pszGIFLIBError );
+#else
+PrintGifError();
+CPLError( CE_Failure, CPLE_AppDefined, %s, pszMsg );
+#endif
+}
+
+//
/* CreateCopy() */
//
@@ -596,9 +618,7 @@
psGifCT-ColorCount, 255, psGifCT) == GIF_ERROR)
{
FreeMapObject(psGifCT);
-PrintGifError();
-CPLError( CE_Failure, CPLE_AppDefined,
- Error writing gif file. );
+GDALPrintGifError(Error writing gif file.);
EGifCloseFile(hGifFile);
VSIFCloseL( fp );
return NULL;
@@ -622,9 +642,7 @@
if (EGifPutImageDesc(hGifFile, 0, 0, nXSize, nYSize, bInterlace, NULL) ==
GIF_ERROR )
{
-PrintGifError();
-CPLError( CE_Failure, CPLE_AppDefined,
- Error writing gif file. );
+GDALPrintGifError(Error writing gif file.);
EGifCloseFile(hGifFile);
VSIFCloseL( fp );
return NULL;
___
! x11-toolkits/pango (pango-1.28.4) (missing header
Hi. can someone help me with this - It occured after the PNG lib update CC libpangocairo_1_0_la-pangocairo-context.lo CC libpangocairo_1_0_la-pangocairo-font.lo CC libpangocairo_1_0_la-pangocairo-fontmap.lo CC libpangocairo_1_0_la-pangocairo-render.lo CC libpangocairo_1_0_la-pangocairo-fcfont.lo CC libpangocairo_1_0_la-pangocairo-fcfontmap.lo CCLD libpangocairo-1.0.la CC querymodules.o CCLD pango-querymodules GISCAN Pango-1.0.gir Package cairo-gobject was not found in the pkg-config search path. Perhaps you should add the directory containing `cairo-gobject.pc' to the PKG_CONFIG_PATH environment variable No package 'cairo-gobject' found In file included from stdin:5: /usr/ports/x11-toolkits/pango/work/pango-1.28.4/pango/pango-impl-utils.h:26:18: error: glib.h: No such file or directory /usr/ports/x11-toolkits/pango/work/pango-1.28.4/pango/pango-impl-utils.h:27:25: error: glib-object.h: No such file or directory Error while processing the source. gmake[4]: *** [Pango-1.0.gir] Error 1 gmake[4]: Leaving directory `/usr/ports/x11-toolkits/pango/work/pango-1.28.4/pango' gmake[3]: *** [all-recursive] Error 1 gmake[3]: Leaving directory `/usr/ports/x11-toolkits/pango/work/pango-1.28.4/pango' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/usr/ports/x11-toolkits/pango/work/pango-1.28.4/pango' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/x11-toolkits/pango/work/pango-1.28.4' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/x11-toolkits/pango. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20120604-11340-1ybvf2a-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=pango-1.28.4 UPGRADE_PORT_VER=1.28.4 make BATCH=yes ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! x11-toolkits/pango (pango-1.28.4) (missing header) Heino ___ 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: Libreoffice, javaPathHelper: not found
On Mon, Jun 04, 2012 at 05:22:30PM +0200, Leslie Jensen wrote: I have just installed libreoffice-3.5.2_4 and are now getting the following error javaPathHelper: not found I understand that this error is known according to this tread http://forums.freebsd.org/showthread.php?t=27035 I'm wondering if there's any fix available? Regards /Leslie ___ 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 This is not an error this is expected :) Expect if you have java installed. regards, Bapt pgp6ObjThc0QK.pgp Description: PGP signature
Re: ! x11-toolkits/pango (pango-1.28.4) (missing header
On Mon, Jun 4, 2012 at 9:26 AM, Heino Tiedemann rotkaps_spam_t...@gmx.de wrote: Hi. can someone help me with this - It occured after the PNG lib update CC libpangocairo_1_0_la-pangocairo-context.lo CC libpangocairo_1_0_la-pangocairo-font.lo CC libpangocairo_1_0_la-pangocairo-fontmap.lo CC libpangocairo_1_0_la-pangocairo-render.lo CC libpangocairo_1_0_la-pangocairo-fcfont.lo CC libpangocairo_1_0_la-pangocairo-fcfontmap.lo CCLD libpangocairo-1.0.la CC querymodules.o CCLD pango-querymodules GISCAN Pango-1.0.gir Package cairo-gobject was not found in the pkg-config search path. Perhaps you should add the directory containing `cairo-gobject.pc' to the PKG_CONFIG_PATH environment variable No package 'cairo-gobject' found In file included from stdin:5: /usr/ports/x11-toolkits/pango/work/pango-1.28.4/pango/pango-impl-utils.h:26:18: error: glib.h: No such file or directory /usr/ports/x11-toolkits/pango/work/pango-1.28.4/pango/pango-impl-utils.h:27:25: error: glib-object.h: No such file or directory Error while processing the source. gmake[4]: *** [Pango-1.0.gir] Error 1 gmake[4]: Leaving directory `/usr/ports/x11-toolkits/pango/work/pango-1.28.4/pango' gmake[3]: *** [all-recursive] Error 1 gmake[3]: Leaving directory `/usr/ports/x11-toolkits/pango/work/pango-1.28.4/pango' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/usr/ports/x11-toolkits/pango/work/pango-1.28.4/pango' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/x11-toolkits/pango/work/pango-1.28.4' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/x11-toolkits/pango. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20120604-11340-1ybvf2a-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=pango-1.28.4 UPGRADE_PORT_VER=1.28.4 make BATCH=yes ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! x11-toolkits/pango (pango-1.28.4) (missing header) I'd love to better understand how gobject-introspection does its thing, but this is NOT a missing header. It is GISCAN believing that the header should exist.. To fix this, re-install gobject-introspection, then update pango. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@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: make failed for editors/libreoffice
On Sat, Jun 2, 2012 at 3:37 PM, Kevin Oberman kob6...@gmail.com wrote:
On Fri, Jun 1, 2012 at 12:02 AM, Sergio de Almeida Lenzi
lenzi.ser...@gmail.com wrote:
Em Qui, 2012-05-31 às 17:31 +0200, Leslie Jensen escreveu:
2012-05-31 14:24, Robert Huff skrev:
Leslie Jensen writes:
---
Oh dear - something failed during the build - sorry !
For more help with debugging build errors, please see the section
in:
http://wiki.documentfoundation.org/Development
internal build errors:
ERROR: error 65280 occurred while making
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/vcl/prj
it seems that the error is inside 'vcl', please re-run build
inside this module to isolate the error and/or test your fix:
---
/usr/local/bin/bash
cd /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2
source ./Env.Host.sh
cd vcl
gmake clean # optional
gmake -r
when the problem is isolated and fixed exit and re-run 'make' from the
top-level
Did you follow the instructions?
Robert Huff
___
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
After four manual procedures I'm getting stuck here.
What can I do?
--
[ build MOD ] writerperfect
Bus error (core dumped)
File tested,Test Result,Execution Time (ms)
file:///usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/lotuswordpro/qa/cppunit/data/pass/A14.lwp,Signal
11 during cups initialization called, ignoring cups
Error: a unit test failed, please do one of:
export DEBUGCPPUNIT=TRUE # for exception catching
export GDBCPPUNITTRACE=gdb --args # for interactive debugging
export VALGRIND=memcheck # for memory checking
and retry.
gmake[1]: ***
[/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/workdir/unxfbsd.pro/CppunitTest/lotuswordpro_test_lotuswordpro.test]
Error 1
gmake[1]: *** Inväntar oavslutade jobb...
TEMPFILE=/tmp/gbuild.XX.gNM6YJsj mv ${TEMPFILE}
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/workdir/unxfbsd.pro/LinkTarget/Library/writerfilter_uno.uno.so.objectlist
gmake[1]: Lämnar katalogen
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/tail_build
gmake: *** [source-env-and-recurse] Error 2
___
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
there is an error in the lotuswordpro testing... if you are not going
to use lotuswrordpro
apply these patch at the
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2
==
--- lotuswordpro/Module_lotuswordpro.mk.orig 2012-05-31
19:34:52.014043605 -0300
+++ lotuswordpro/Module_lotuswordpro.mk 2012-05-31 19:29:29.276164732
-0300
@@ -31,8 +31,8 @@
Library_lwpft \
))
-$(eval $(call gb_Module_add_check_targets,lotuswordpro,\
- CppunitTest_lotuswordpro_test_lotuswordpro \
-))
+#$(eval $(call gb_Module_add_check_targets,lotuswordpro,\
+# CppunitTest_lotuswordpro_test_lotuswordpro \
+#))
# vim: set noet sw=4 ts=4:
=
I hit the same problem, applied the suggested patch and tried gmake
(in lotuswordpro) again.
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/solenv/gbuild/Library.mk:54:
*** gb_Deliver_deliver: file does not exist in solver, and cannot be
delivered:
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/solver/unxfbsd.pro/lib/libsfxlo.so.
Stop.
gmake[1]: *** Waiting for unfinished jobs
rm
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/workdir/unxfbsd.pro/ExternalHeaders/Library/libsvxcorelo.so
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/workdir/unxfbsd.pro/ExternalHeaders/Library/libsvtlo.so
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/workdir/unxfbsd.pro/ExternalHeaders/Library/libsfxlo.so
gmake[1]: Leaving directory
`/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/lotuswordpro'
gmake: *** [source-env-and-recurse] Error 2
Any idea how I can proceed?
I have now completed the build of libreoffice, but not easily. It
looks like something in the parallelization of build might be broken.
I have a dual-core Sandybridge CPU (so it has 4 CPUs with
hyperthreading). If I try to make libreoffice I get failures in vcl,
framework, sfx2, and tail_builds. (I also have to apply the patch to
prevent the
Re: net-im/skype-devel
In article 20120604120054.GA1849@tiny you write: Hi, Hi! I run 10-CURRENT r235646 and CVS updated ports (both from May, 19); skype-2.1.0.81,1 is working fine, uncluding viedo: the port net-im/skype-devel still says, that video is broken; is there some pre-view to test or to help debugging? I'm not itetcu but... Skype is closed source so it's not easy to find out why video doesn't work with the version in net-im/skype-devel, but IIRC linux_kdump showed it's trying to use the Linux inotify syscall which is still missing in the Linuxolator. Is this the cause video doesn't work? Only those with the source know... HTH, Juergen ___ 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: ! x11-toolkits/pango (pango-1.28.4) (missing header
Kevin Oberman kob6...@gmail.com wrote: On Mon, Jun 4, 2012 at 9:26 AM, Heino Tiedemann rotkaps_spam_t...@gmx.de wrote: Hi. can someone help me with this - It occured after the PNG lib update CC libpangocairo_1_0_la-pangocairo-context.lo CC libpangocairo_1_0_la-pangocairo-font.lo CC libpangocairo_1_0_la-pangocairo-fontmap.lo CC libpangocairo_1_0_la-pangocairo-render.lo CC libpangocairo_1_0_la-pangocairo-fcfont.lo CC libpangocairo_1_0_la-pangocairo-fcfontmap.lo CCLD libpangocairo-1.0.la CC querymodules.o CCLD pango-querymodules GISCAN Pango-1.0.gir Package cairo-gobject was not found in the pkg-config search path. Perhaps you should add the directory containing `cairo-gobject.pc' to the PKG_CONFIG_PATH environment variable No package 'cairo-gobject' found In file included from stdin:5: /usr/ports/x11-toolkits/pango/work/pango-1.28.4/pango/pango-impl-utils.h:26:18: error: glib.h: No such file or directory /usr/ports/x11-toolkits/pango/work/pango-1.28.4/pango/pango-impl-utils.h:27:25: error: glib-object.h: No such file or directory Error while processing the source. gmake[4]: *** [Pango-1.0.gir] Error 1 gmake[4]: Leaving directory `/usr/ports/x11-toolkits/pango/work/pango-1.28.4/pango' gmake[3]: *** [all-recursive] Error 1 gmake[3]: Leaving directory `/usr/ports/x11-toolkits/pango/work/pango-1.28.4/pango' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/usr/ports/x11-toolkits/pango/work/pango-1.28.4/pango' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/x11-toolkits/pango/work/pango-1.28.4' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/x11-toolkits/pango. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20120604-11340-1ybvf2a-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=pango-1.28.4 UPGRADE_PORT_VER=1.28.4 make BATCH=yes ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! x11-toolkits/pango (pango-1.28.4) (missing header) I'd love to better understand how gobject-introspection does its thing, but this is NOT a missing header. It is GISCAN believing that the header should exist.. To fix this, re-install gobject-introspection, then update pango. the solution was in graphics/cairo I had to Build it WITH GLIB Enable GObject Functions Feature That was Off (by me). Heino ___ 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: optionsng ignores /var/db/ports/portname/options
On Sun, Jun 03, 2012 at 11:54:06PM +0200, Baptiste Daroussin wrote: You found a nice bug. The options file is read the thing is that the UNIQUENAME is changed is py-py-stl when the optionsfile is read and it is py27-py-stl when it is written. I don't know why yet, I'll fix it asap. regards, Bapt FYI the bug you found also happen with python and rubygem ports, it can also happen with apache ports, in fact any ports depending on bsd.*.mk where bsd.*.mk defines the pkgnameprefix. nothing directly related to optionsNG a good example of workaround is: look at py-yaml You can have multiple workarounds: first one: define OPTIONSFILE in your ports like py-yaml I did that, and it works fine. It seems the a simple solution. second one: replace bsd.port.options.mk by bsd.port.pre.mk (do not forget in that case the bsd.port.post.mk in the end) I had pre and post in my port makefile: it didn't work. Thanks for your help! Roland -- R.F.Smith http://rsmith.home.xs4all.nl/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpyNAgL7wzZx.pgp Description: PGP signature
Re: make failed for editors/libreoffice
On 31.05.2012 11:36, Leslie Jensen wrote: Help Please! Thanks --- Oh dear - something failed during the build - sorry ! For more help with debugging build errors, please see the section in: http://wiki.documentfoundation.org/Development internal build errors: ERROR: error 65280 occurred while making /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/vcl/prj it seems that the error is inside 'vcl', please re-run build inside this module to isolate the error and/or test your fix: --- /usr/local/bin/bash cd /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2 source ./Env.Host.sh cd vcl gmake clean # optional gmake -r when the problem is isolated and fixed exit and re-run 'make' from the top-level gmake[1]: *** [build] Fel 1 gmake[1]: Lämnar katalogen /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2 gmake: *** [source-env-and-recurse] Fel 2 *** Error code 1 Stop in /usr/ports/editors/libreoffice. === make failed for editors/libreoffice === Aborting update === Update for editors/libreoffice failed === Aborting update Terminated ___ 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 I had built LibreOffice with GCC 4.6 and adding /etc/libmap.conf like this: libgcc_s.so.1 gcc46/libgcc_s.so.1 libgomp.so.1gcc46/libgomp.so.1 libobjc.so.3gcc46/libobjc.so.3 libssp.so.0 gcc46/libssp.so.0 libstdc++.so.6 gcc46/libstdc++.so.6 cd /usr/port/editors/libreoffice make -DWITH_GCC Maybe cppunit will fail, then do exactly what the error message says. It requires lang/gcc46 to be installed and it's not a solution, but for those cannot wait for a fix, this can work... ___ 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
graphics/gdal: gifdataset.cpp:599:23: error: 'PrintGifError' was not declared in this scope
Since the last port update, I get this sticky error in gdal: libtool: compile: g++46 -O3 -pipe -fno-strict-aliasing -march=native -Wl,-rpath=/usr/local/lib/gcc46 -Wall -I/usr/ports/graphics/gdal/work/gdal-1.9.0/port -I/usr/ports/graphics/gdal/work/gdal-1.9.0/gcore -I/usr/ports/graphics/gdal/work/gdal-1.9.0/alg -I/usr/ports/graphics/gdal/work/gdal-1.9.0/ogr -I/usr/ports/graphics/gdal/work/gdal-1.9.0/ogr/ogrsf_frmts -DOGR_ENABLED -I/usr/local/include -I/usr/ports/graphics/gdal/work/gdal-1.9.0/port -I/usr/local/include -I/usr/local -I/usr/local/include -I/usr/local/include -I/usr/local -I/usr/local/include -I/usr/local -I/usr/local/include -I/usr/local/include -I/usr/local -I/usr/local/include -I/usr/local -I/usr/local/include -I/usr -I/usr/include -c gifdataset.cpp -fPIC -DPIC -o ../o/.libs/gifdataset.o gifdataset.cpp: In static member function 'static GDALDataset* GIFDataset::CreateCopy(const char*, GDALDataset*, int, char**, GDALProgressFunc, void*)': gifdataset.cpp:599:23: error: 'PrintGifError' was not declared in this scope gifdataset.cpp:625:23: error: 'PrintGifError' was not declared in this scope gmake[2]: *** [../o/gifdataset.lo] Error 1 gmake[2]: Leaving directory `/usr/ports/graphics/gdal/work/gdal-1.9.0/frmts/gif' gmake[1]: *** [gif-install-obj] Error 2 gmake[1]: Leaving directory `/usr/ports/graphics/gdal/work/gdal-1.9.0/frmts' gmake: *** [frmts-target] Error 2 *** [do-build] Error code 1 Stop in /usr/ports/graphics/gdal. *** [build] Error code 1 Stop in /usr/ports/graphics/gdal. === make failed for graphics/gdal === Aborting update Terminated === You can restart from the point of failure with this command line: portmaster flags graphics/gdal Regards, Oliver signature.asc Description: OpenPGP digital signature
Re: graphics/gdal: gifdataset.cpp:599:23: error: 'PrintGifError' was not declared in this scope
Hi! Since the last port update, I get this sticky error in gdal: It's in graphics/giflib, the latest update to 4.2.0 dropped the symbol PrintGifError. All the dependent packages need to be recompiled 8-( Yes, I know. This is messy. libtool: compile: g++46 -O3 -pipe -fno-strict-aliasing -march=native -Wl,-rpath=/usr/local/lib/gcc46 -Wall -I/usr/ports/graphics/gdal/work/gdal-1.9.0/port -I/usr/ports/graphics/gdal/work/gdal-1.9.0/gcore -I/usr/ports/graphics/gdal/work/gdal-1.9.0/alg -I/usr/ports/graphics/gdal/work/gdal-1.9.0/ogr -I/usr/ports/graphics/gdal/work/gdal-1.9.0/ogr/ogrsf_frmts -DOGR_ENABLED -I/usr/local/include -I/usr/ports/graphics/gdal/work/gdal-1.9.0/port -I/usr/local/include -I/usr/local -I/usr/local/include -I/usr/local/include -I/usr/local -I/usr/local/include -I/usr/local -I/usr/local/include -I/usr/local/include -I/usr/local -I/usr/local/include -I/usr/local -I/usr/local/include -I/usr -I/usr/include -c gifdataset.cpp -fPIC -DPIC -o ../o/.libs/gifdataset.o gifdataset.cpp: In static member function 'static GDALDataset* GIFDataset::CreateCopy(const char*, GDALDataset*, int, char**, GDALProgressFunc, void*)': gifdataset.cpp:599:23: error: 'PrintGifError' was not declared in this scope gifdataset.cpp:625:23: error: 'PrintGifError' was not declared in this scope gmake[2]: *** [../o/gifdataset.lo] Error 1 gmake[2]: Leaving directory `/usr/ports/graphics/gdal/work/gdal-1.9.0/frmts/gif' gmake[1]: *** [gif-install-obj] Error 2 gmake[1]: Leaving directory `/usr/ports/graphics/gdal/work/gdal-1.9.0/frmts' gmake: *** [frmts-target] Error 2 *** [do-build] Error code 1 Stop in /usr/ports/graphics/gdal. *** [build] Error code 1 Stop in /usr/ports/graphics/gdal. === make failed for graphics/gdal === Aborting update Terminated === You can restart from the point of failure with this command line: portmaster flags graphics/gdal Regards, Oliver -- p...@opsec.eu+49 171 3101372 8 years to go ! ___ 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: net-im/skype-devel
On Mon, 4 Jun 2012 19:50:52 +0200 (CEST) Juergen Lock n...@jelal.kn-bremen.de wrote: In article 20120604120054.GA1849@tiny you write: Hi, Hi! I run 10-CURRENT r235646 and CVS updated ports (both from May, 19); skype-2.1.0.81,1 is working fine, uncluding viedo: the port net-im/skype-devel still says, that video is broken; is there some pre-view to test or to help debugging? I'm not itetcu but... Skype is closed source so it's not easy to find out why video doesn't work with the version in net-im/skype-devel, but IIRC linux_kdump showed it's trying to use the Linux inotify syscall which is still missing in the Linuxolator. Is this the cause video doesn't work? Last time I tested, yes, that was one of the problems. Current beta from skype is at .99, you could give it a try, but I don't expect anything better. And upcoming 3 is even worse. Only those with the source know... Well, yeh. Trouble is linux version has the lowest priority (and the user base is constant, unlike the user base for the other versions); and while the skype devs are really nice people, there's a high level of institutional legal paranoia which doesn't help at all. So ... -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B ___ 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: [OPTIONS NG] multiple OPTIONS_MULTI not possible
On 04/06/2012 21:29, Lars Engels wrote: OPTIONS_DEFINE= CDDA2WAV OPTIONS_MULTI= ENCODER OPTIONS_MULTI_ENCODER= LAME VORBIS FLAC OPTIONS_MULTI= ENGINE OPTIONS_MULTI_ENGINE= MPLAYER XINE OPTIONS_DEFAULT=MPLAYER CDDA2WAV LAME VORBIS You need: OPTIONS_MULTI= ENCODER ENGINE OPTIONS_MULTI_ENCODER= LAME VORBIS FLAC OPTIONS_MULTI_ENGINE= MPLAYER XINE Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
NO_OPTIONS_SORT makes options disappear
The new options framework sorts all of the options by default before presenting them to the user. I have mixed feelings about this, however there is supposed to be a workaround for those of us who have grouped the options for our ports into logical chunks, NO_OPTIONS_SORT. Today I tried defining that in my BIND ports so that users would not be confused during the upgrade process, and got this: make config === No options to configure I tried defining NO_OPTIONS_SORT both before and after including bsd.port.pre.mk, got the same result for both. Suggestions welcome, Doug -- This .signature sanitized for your protection ___ 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: [OPTIONS NG] multiple OPTIONS_MULTI not possible
On Mon, Jun 04, 2012 at 09:41:40PM +0100, Matthew Seaman wrote: On 04/06/2012 21:29, Lars Engels wrote: OPTIONS_DEFINE= CDDA2WAV OPTIONS_MULTI= ENCODER OPTIONS_MULTI_ENCODER= LAME VORBIS FLAC OPTIONS_MULTI= ENGINE OPTIONS_MULTI_ENGINE= MPLAYER XINE OPTIONS_DEFAULT=MPLAYER CDDA2WAV LAME VORBIS You need: OPTIONS_MULTI=ENCODER ENGINE OPTIONS_MULTI_ENCODER=LAME VORBIS FLAC OPTIONS_MULTI_ENGINE= MPLAYER XINE Thanks Matthew, the PH should be a bit clearer here. :) Lars pgpU2V9xKGl4L.pgp Description: PGP signature
Why does giflib 4.2.0 require xmlto?
Hello, It seems that giflib 4.2.0 (graphics/giflib) requires xmlto (textproc/xmlto) and xmlto drags in w3m, which I do not want. Why does version 4.2.0 of giflib suddenly require xmlto? Previous versions of giflib managed fine without it. -- Regards, Torfinn Ingolfsen ___ 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: make failed for editors/libreoffice
With gcc47 unfortunately I'm stuck on a boost. ERROR: error 65280 occurred while making /usr/obj/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/boost it seems that the error is inside 'boost', please re-run build inside this module to isolate the error and/or test your fix: --- /usr/local/bin/bash cd /usr/obj/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2 source ./Env.Host.sh cd boost rm -Rf /usr/obj/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/boost/unxfbsd.pro # optional module 'clean' build With cppunit it helped, with boost not so much. -- View this message in context: http://freebsd.1045724.n5.nabble.com/make-failed-for-editors-libreoffice-tp5713591p5715076.html Sent from the freebsd-ports mailing list archive at Nabble.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: NO_OPTIONS_SORT makes options disappear
On Mon, Jun 04, 2012 at 01:47:03PM -0700, Doug Barton wrote: The new options framework sorts all of the options by default before presenting them to the user. I have mixed feelings about this, however there is supposed to be a workaround for those of us who have grouped the options for our ports into logical chunks, NO_OPTIONS_SORT. Today I tried defining that in my BIND ports so that users would not be confused during the upgrade process, and got this: make config === No options to configure I tried defining NO_OPTIONS_SORT both before and after including bsd.port.pre.mk, got the same result for both. Suggestions welcome, Doug -- This .signature sanitized for your protection Have you tried keeping you port as-is or converting it ? Can you send me a diff so that I can have a deeper look tomorrow morning GMT+1? regards, Bapt pgpfOrZymwIrq.pgp Description: PGP signature
Re: NO_OPTIONS_SORT makes options disappear
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/04/2012 15:22, Baptiste Daroussin wrote: On Mon, Jun 04, 2012 at 01:47:03PM -0700, Doug Barton wrote: The new options framework sorts all of the options by default before presenting them to the user. I have mixed feelings about this, however there is supposed to be a workaround for those of us who have grouped the options for our ports into logical chunks, NO_OPTIONS_SORT. Today I tried defining that in my BIND ports so that users would not be confused during the upgrade process, and got this: make config === No options to configure I tried defining NO_OPTIONS_SORT both before and after including bsd.port.pre.mk, got the same result for both. Have you tried keeping you port as-is I left it as-is since I don't have time to do anything else. This results in a bad user experience since the options are now all sorted into alphabetical order instead of the meaningful groupings that I had them in. or converting it ? I don't have time to do that right now, and this should not be necessary in order to maintain backwards compatibility with what I already had. I can accept adding the NO_OPTIONS_SORT knob, but the fact that adding it causes things to be dramatically more broken than they already are is a bug. Can you send me a diff so that I can have a deeper look tomorrow morning GMT+1? I described what I did in detail in my OP. Adding NO_OPTIONS_SORT was the only change I made. Doug - -- This .signature sanitized for your protection -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJPzTaIAAoJEFzGhvEaGryEOuUH/2WcSn0Wn8xMoUzhIJBm2x2Z Axog5WoLoL/uuddijCsAQyQlG4OxYaatMvIPBg2kImqZDdZV0wDvrp/vcg3vngYX zvq2kpzfc0y8BT01UWi6BNGJXymDHZ0/b8NKv7pYrUWvTLta4Ae8wxtxZciGsAVL ITMFXygIDhu8KWtWmfakP5bJpwexz+v20M1CoKhBWJ8FuawcicZctOscbUCYn4HE KK4kYcmO/sb8C5n8aCehJXQbcZX77wftSDUatfNpv8WTxyDPzKpms3SwmfOUIMnd XSnh4O4eiyIccPk9OCE4EMOmizlJhBxMpgEPp6a0QeAwmWaYA09dTiyhbexXcXQ= =FlRt -END PGP SIGNATURE- ___ 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: NO_OPTIONS_SORT makes options disappear
On Mon, Jun 04, 2012 at 03:28:24PM -0700, Doug Barton wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/04/2012 15:22, Baptiste Daroussin wrote: On Mon, Jun 04, 2012 at 01:47:03PM -0700, Doug Barton wrote: The new options framework sorts all of the options by default before presenting them to the user. I have mixed feelings about this, however there is supposed to be a workaround for those of us who have grouped the options for our ports into logical chunks, NO_OPTIONS_SORT. Today I tried defining that in my BIND ports so that users would not be confused during the upgrade process, and got this: make config === No options to configure I tried defining NO_OPTIONS_SORT both before and after including bsd.port.pre.mk, got the same result for both. Have you tried keeping you port as-is I left it as-is since I don't have time to do anything else. This results in a bad user experience since the options are now all sorted into alphabetical order instead of the meaningful groupings that I had them in. or converting it ? I don't have time to do that right now, and this should not be necessary in order to maintain backwards compatibility with what I already had. I can accept adding the NO_OPTIONS_SORT knob, but the fact that adding it causes things to be dramatically more broken than they already are is a bug. I'll try to come asap with a fix for that Can you send me a diff so that I can have a deeper look tomorrow morning GMT+1? I described what I did in detail in my OP. Adding NO_OPTIONS_SORT was the only change I made. Doug - -- This .signature sanitized for your protection -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJPzTaIAAoJEFzGhvEaGryEOuUH/2WcSn0Wn8xMoUzhIJBm2x2Z Axog5WoLoL/uuddijCsAQyQlG4OxYaatMvIPBg2kImqZDdZV0wDvrp/vcg3vngYX zvq2kpzfc0y8BT01UWi6BNGJXymDHZ0/b8NKv7pYrUWvTLta4Ae8wxtxZciGsAVL ITMFXygIDhu8KWtWmfakP5bJpwexz+v20M1CoKhBWJ8FuawcicZctOscbUCYn4HE KK4kYcmO/sb8C5n8aCehJXQbcZX77wftSDUatfNpv8WTxyDPzKpms3SwmfOUIMnd XSnh4O4eiyIccPk9OCE4EMOmizlJhBxMpgEPp6a0QeAwmWaYA09dTiyhbexXcXQ= =FlRt -END PGP SIGNATURE- pgpc86sRXYAg9.pgp Description: PGP signature
Re: New OPTIONS and make.conf knobs
On 06/04/2012 04:29, Miroslav Lachman wrote: Yes, that's right. But I am confused why portmaster does not show the options dialog to let user uncheck QT4? There is code to do this if you use the --force-config option. I haven't made that the default yet because it's a fairly complex part of the code, and I'm not sure that making it the default won't do more harm than good. Please try it and let me know how it goes for you. Doug -- This .signature sanitized for your protection ___ 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: NO_OPTIONS_SORT makes options disappear
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/04/2012 15:31, Baptiste Daroussin wrote: I'll try to come asap with a fix for that Thanks! - -- This .signature sanitized for your protection -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJPzTggAAoJEFzGhvEaGryEDWQIANWiHMBaIxszTHK1lCRqMEWh 4u92DCt9C7JpqKRPnNf+5Do/AWivaWY23lXEeNN3IuJM2p6gy41qbu/zHWxJ8enm E/UWiDY2vwaWxmsi0ZdUZV9VzV11IZ59/mO5ewLZ+U/WzQcfmDiOYMpQa721kU7o 10meB+YY5inpH6tOSU/ZcaEuREIpb2vSgOmk9EMv5Ki8j6dBETKafeOYMO8SpJKQ u6ofVsqkeOg3vZqexaPd/Xp3KXekkfof+4EFwarvh1OZtzau1OVhRss2hnpzcsQW WAz4PkMXAyMXJ8NYm1wY5TGNOYCqaIqhyzTXHchIYSlH8gtsJ5UaXkXfmU+dt0o= =vPPy -END PGP SIGNATURE- ___ 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: NO_OPTIONS_SORT makes options disappear
On Mon, Jun 04, 2012 at 03:28:24PM -0700, Doug Barton wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/04/2012 15:22, Baptiste Daroussin wrote: On Mon, Jun 04, 2012 at 01:47:03PM -0700, Doug Barton wrote: The new options framework sorts all of the options by default before presenting them to the user. I have mixed feelings about this, however there is supposed to be a workaround for those of us who have grouped the options for our ports into logical chunks, NO_OPTIONS_SORT. Today I tried defining that in my BIND ports so that users would not be confused during the upgrade process, and got this: make config === No options to configure I tried defining NO_OPTIONS_SORT both before and after including bsd.port.pre.mk, got the same result for both. Have you tried keeping you port as-is I left it as-is since I don't have time to do anything else. This results in a bad user experience since the options are now all sorted into alphabetical order instead of the meaningful groupings that I had them in. or converting it ? I don't have time to do that right now, and this should not be necessary in order to maintain backwards compatibility with what I already had. I can accept adding the NO_OPTIONS_SORT knob, but the fact that adding it causes things to be dramatically more broken than they already are is a bug. Can you send me a diff so that I can have a deeper look tomorrow morning GMT+1? I described what I did in detail in my OP. Adding NO_OPTIONS_SORT was the only change I made. Doug - -- This .signature sanitized for your protection -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJPzTaIAAoJEFzGhvEaGryEOuUH/2WcSn0Wn8xMoUzhIJBm2x2Z Axog5WoLoL/uuddijCsAQyQlG4OxYaatMvIPBg2kImqZDdZV0wDvrp/vcg3vngYX zvq2kpzfc0y8BT01UWi6BNGJXymDHZ0/b8NKv7pYrUWvTLta4Ae8wxtxZciGsAVL ITMFXygIDhu8KWtWmfakP5bJpwexz+v20M1CoKhBWJ8FuawcicZctOscbUCYn4HE KK4kYcmO/sb8C5n8aCehJXQbcZX77wftSDUatfNpv8WTxyDPzKpms3SwmfOUIMnd XSnh4O4eiyIccPk9OCE4EMOmizlJhBxMpgEPp6a0QeAwmWaYA09dTiyhbexXcXQ= =FlRt -END PGP SIGNATURE- Can you try with this patch ? http://people.freebsd.org/~bapt/bsd.options.mk.diff Still adding NO_OPTIONS_SORT=yes regards, Bapt pgpqB5zUo4uGd.pgp Description: PGP signature
Re: Why Are You NOT Using FreeBSD?
On Mon, Jun 04, 2012 at 07:53:52AM -0400, Michael Scheidell wrote: On 6/4/12 7:36 AM, Adam Strohl wrote: Doesn't tinderbox do this every night? And, as a committer, here is the point. We get reports of 'this doesn't build'. (no fixed attached, no logs, no indication of what was installed first, what options taken), [...] So, we run it up in a tinderbox People who want to understand port failures should be first checking to see if the port builds in a completely clean environment. The best way to do this is to see if it has built on our build cluster (where a clean environment is forced), and the quickest way to do that is to use portsmon as a summary of the port across the various buildenvs. For example: http://portsmon.freebsd.org/portoverview.py?category=wwwportname=chromium We can see that chromium is currently having a number of build problems. It also has a number of PRs filed against it. On the overview page for each port are links to both CVSWeb, as well as the information FreshPorts displays for the port: http://www.freebsd.org/cgi/cvsweb.cgi/ports/www/chromium/ http://www.freshports.org/www/chromium So I recommend that we suggest to people who are having problems with a particular port use portsmon as a start here resource. mcl ___ 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: make failed for editors/libreoffice
Leslie Jensen les...@eskk.nu wrote: --- Oh dear - something failed during the build - sorry ! For more help with debugging build errors, please see the section in: http://wiki.documentfoundation.org/Development internal build errors: ERROR: error 65280 occurred while making /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/vcl/prj it seems that the error is inside 'vcl', please re-run build inside this module to isolate the error and/or test your fix: --- /usr/local/bin/bash cd /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2 source ./Env.Host.sh cd vcl gmake clean # optional gmake -r when the problem is isolated and fixed exit and re-run 'make' from the top-level gmake[1]: *** [build] Fel 1 gmake[1]: Lämnar katalogen /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2 gmake: *** [source-env-and-recurse] Fel 2 *** Error code 1 Stop in /usr/ports/editors/libreoffice. I have this again, again and again in a lot of modules: - vlc - framework - sfx2 - ... In this way I need a lot of days to build Libreoffice. Because I cannot watch the build process all the time - every day some build error occurded, und I have to fix it by hand. Heino ___ 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: net-im/skype-devel
On Mon, 4 Jun 2012 23:41:05 +0300 Ion-Mihai Tetcu ite...@freebsd.org wrote: Last time I tested, yes, that was one of the problems. Current beta from skype is at .99, you could give it a try, but I don't expect anything better. And upcoming 3 is even worse. I tested already it doesn't work, because it requires libtiff.so.4. - Martin -- +--oOO--(_)--OOo+ Facebook: miwi1 Twitter:miwi_ With best Regards, Martin Wilke (miwi_(at)_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: make failed for editors/libreoffice
Le 05.06.2012 05:48, Heino Tiedemann a écrit : Leslie Jensenles...@eskk.nu wrote: --- Oh dear - something failed during the build - sorry ! For more help with debugging build errors, please see the section in: http://wiki.documentfoundation.org/Development internal build errors: ERROR: error 65280 occurred while making /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/vcl/prj it seems that the error is inside 'vcl', please re-run build inside this module to isolate the error and/or test your fix: --- /usr/local/bin/bash cd /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2 source ./Env.Host.sh cd vcl gmake clean # optional gmake -r when the problem is isolated and fixed exit and re-run 'make' from the top-level gmake[1]: *** [build] Fel 1 gmake[1]: Lämnar katalogen /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2 gmake: *** [source-env-and-recurse] Fel 2 *** Error code 1 Stop in /usr/ports/editors/libreoffice. I have this again, again and again in a lot of modules: - vlc - framework - sfx2 - ... In this way I need a lot of days to build Libreoffice. Because I cannot watch the build process all the time - every day some build error occurded, und I have to fix it by hand. Heino ___ 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 I have the same problem but i can pass it except for tail_build. My options : GTK3 (I don't remember, but maybe tested also with GTK2) JAVA MMEDIA PGSQL SVG Regards ___ 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: Libreoffice, javaPathHelper: not found
2012-06-04 18:58, Baptiste Daroussin skrev: On Mon, Jun 04, 2012 at 05:22:30PM +0200, Leslie Jensen wrote: I have just installed libreoffice-3.5.2_4 and are now getting the following error javaPathHelper: not found I understand that this error is known according to this tread http://forums.freebsd.org/showthread.php?t=27035 I'm wondering if there's any fix available? Regards /Leslie ___ 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 This is not an error this is expected :) Expect if you have java installed. regards, Bapt Thanks! That is of course logical. Shouldn't java be a dependency if Libreoffice can't start without it? Exactly which java do you recommend that I install? /Leslie ___ 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
