Re: how to enforce one version of python
On Wed, 12 Sep 2018 at 19:35, tech-lists wrote: > > On 12/09/2018 13:33, Robert Huff wrote: > > How many ports_require_ python 3? > > How many ports_require_ python 2? > > yeah, I'd like to know too. I mean, I've never installed python as like > requiring it to program - it's installed as a dependency of other stuff > I want to actually run. And I thought python2 and 3 are actually > different languages rather than simply versions. Might be wrong though. > > tjhanks, > > -- > J. They are kind of both, which is both a blessing and a curse. With a bit of care you can write code that's legal in both, and even if you don't, the automatic 2to3 converter is often good enough. Thus, many packages support being configured for either version from the same source, which is why it's kind of a compile-time decision. The fun part is the combination of 2-only holdouts and new 3-only code, which is why it's easy to end up with both installed. At least there's a definite sunset for 2, so it will _eventually_ work itself out. -- Daniel Nebdal ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [FreeBSD-Ports-Announce] Time to bid farewell to the old pkg_ tools
On Thu, Feb 6, 2014 at 1:45 PM, Matthias Apitz wrote: > El día Thursday, February 06, 2014 a las 01:27:50PM +0100, Julian H. Stacey > escribió: > >> Michel Talon wrote: >> >> > The old package system was total = >> > crap, >> >> local.sqlite is also crap, breaks decades of accessibility by find & grep >> & other text pipe / search tools. > > Since many years I have always compiled "my" (i.e. the ports I need) > from CVS or now SVN ports tree on some fast baquery maschine. After > compiling I just did something like: > > # mkdir PKG > # cd PKG > # pkg_create -Rnb `cd /var/db/pkg ; ls -C1` > > and moved the resulting ~1500 packages to my laptops or smaller > netbooks. Until today I'm still using the old pkg_info/_add/_create > tools and skipped pkgng until today. > > Will the above procedure work fine too in the future? > > Why not keep the old methods unchanged in place as today? > > Thanks > > matthias > The recommended way to do that is to set up poudriere. It's a different tool, but easy enough to work with, and it has certain benefits [1]. Obviously, that's neither a "yes" nor a "no" - and in short I don't know how pkg supports that specific use. [1] It's smarter about building in parallel, so it should be faster. It also handles compiling upgraded packages better - the logic is about the same as in portmaster/portupgrade, though building each port in a clean jail (with dependencies installed from the packages it has already created) reduces the risk of contamination from old versions on the host (typically automake scripts detecting some installed and not-yet upgraded library that's not set as a dependency ... at least that has happened to me a few times). It also creates a pkg repository with the packages, so if you have network access (nfs or http) you can use pkg to do installs or upgrades on the "client" machines (especially upgrades are very smooth like that). -- Daniel Nebdal ___ 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-Announce] Time to bid farewell to the old pkg_ tools
On Thu, Feb 6, 2014 at 12:41 PM, Rick Miller wrote: > On Thu, Feb 6, 2014 at 2:59 AM, Big Lebowski wrote: > >> On Thu, Feb 6, 2014 at 7:45 AM, Matthew Seaman < >> m.sea...@infracaninophile.co.uk> wrote: >> >> > >> > I'd be interested to hear what features you think are missing. We will >> > implement anything (eventually...) that there is demand for and that is >> > technically feasible, and that fits with the overall concept of what we >> > think a packaging system should do. There's a number of ideas in the >> > github issue list already (usually tagged with 'longterm' or 'thinking') >> > and we are happy for people to add to that, or to discuss ideas -- the >> > freebsd-pkg@ list is a good place for that. >> > >> >> The ability to install certain package version, instead of installing >> simply the latest one. Please, please, pretty please! :) > > > I echo this sentiment, but I would like to take it a step further and say > "a certain version or greater". > > I suspect he meant "a certain version, and *not* newer" - sometimes you might want to hold back a package. -- Daniel Nebdal ___ 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: opencv update
On Wed, Dec 4, 2013 at 2:10 PM, Ajtim wrote: > I did what is in /usr/ports/UPDATING and looks like I am in trouble now. > My system is FreeBSD 10.0-BETA4 (amd64): > > ===> FreeBSD 10 autotools fix applied to > /usr/ports/multimedia/ffmpeg0/work/ffmpeg-0.7.16/configure > ERROR: opencv-core not found > > If you think configure made a mistake, make sure you are using the latest > version from Git. If the latest version fails, report the problem to the > ffmpeg-u...@ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net. > Include the log file "config.log" produced by configure as this will help > solving the problem. > ===> Script "configure" failed unexpectedly. > Please report the problem to w...@freebsd.org [maintainer] and attach the > "/usr/ports/multimedia/ffmpeg0/work/ffmpeg-0.7.16/config.err" including the > output of the failure of your make command. Also, it might be a good idea > to > provide an overview of all packages installed on your system (e.g. a > /usr/local/sbin/pkg-static info -g -Ea). > *** Error code 1 > > Stop. > make[1]: stopped in /usr/ports/multimedia/ffmpeg0 > *** Error code 1 > > Stop. > make: stopped in /usr/ports/multimedia/ffmpeg0 > > ===>>> make failed for multimedia/ffmpeg0 > ===>>> Aborting update > > ===>>> Update for multimedia/ffmpeg0 failed > ===>>> Aborting update > > ===>>> Killing background jobs > Terminated > ===>>> The following actions were performed: > Installation of graphics/opencv-core (opencv-core-2.4.7) > Upgrade of ffmpeg-2.1.1,1 to ffmpeg-2.1.1_1,1 > > > ===>>> You can restart from the point of failure with this command line: >portmaster multimedia/ffmpeg0 > graphics/gstreamer-plugins-opencv graphics/opencv graphics/openimageio > x11/xterm > > Thank you. > -- > Mitja > --- > http://www.redbubble.com/people/lumiwa I ran into something like that when the relevant files were installed, but didn't work (missing symbols in something it was linked to, I believe). What does the config.err file say? -- Daniel Nebdal ___ 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: pkgng upgrade options
On Tue, Dec 3, 2013 at 11:54 AM, Beeblebrox wrote: > >> There should be some OPTONS_FILE_UNSET variables > I just left those out and only posted those with " OPTIONS_FILE_SET" > > >>It's possible that the FreeBSD repo is before your local repo. > >>To see the repository order use: pkg -v -v > Yes, the FreeBSD repo is listed first while myrepo is #2. I don't see how I > can change the order though. Combining all repo info into a single file > comes to mind; tried and it seems to break things. > > The unixODBC / libiodbc conflict is from these two: databases/php5-odbc & > databases/php5-pdo_odbc > They both have "OPTIONS_FILE_SET+=IODBC" however, so should nat ask for > unixODBC > > The most serious pkg conflict I am seeing is devel/py27-distribute vs. > devel/py27-setuptools > "pkg set -o devel/py27-distribute:devel/py27-setuptools" has no effect. > Only > emulators/virtualbox-ose is asking for devel/py-distribute. > > > > - > FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS > This might be overly trivial, but ... is py27-setuptools already installed, by chance? Can you try removing it? -- Daniel Nebdal ___ 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: Few missing packages from the new PKG repositories
On Sat, Nov 23, 2013 at 11:34 PM, Mathieu Arnold wrote: > +--On 23 novembre 2013 16:27:12 +0200 Kimmo Paasiala > wrote: > | Were these left out by accident or why aren’t they included? > | > | - x11/gnome2, x11/gnome2-lite is in the repo. > | > | - editors/vim, editors/vim-lite is in the repo as well. > > The packages are built from the ports tree as it is at 1 UTC every > Wednesday, so, if something is broken at that time, like openjpeg was (my > fault) many dependencies are not included. You'll have to wait for next > week. > > -- > Mathieu Arnold > > Right, I guessed it was something like that - thanks. -- Daniel Nebdal ___ 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: Few missing packages from the new PKG repositories
On Sat, Nov 23, 2013 at 7:29 PM, Koop Mast wrote: > On 23-11-2013 18:13, Daniel Nebdal wrote: > >> On Sat, Nov 23, 2013 at 3:27 PM, Kimmo Paasiala >> wrote: >> >> Were these left out by accident or why aren’t they included? >>> >>> - x11/gnome2, x11/gnome2-lite is in the repo. >>> >>> - editors/vim, editors/vim-lite is in the repo as well. >>> >>> -Kimmo >>> >>> Do all the dependencies build with default options? I suspect that's why >> kde4 wasn't packaged last time I checked. >> (I guess we could take a look at the build logs from the new repository; I >> know they're out there somewhere.) >> >> To both of you, on which FreeBSD version and arch are these packages > missing? That will help us narrow down where to look. > > -Koop > > On 10.0-BETA4 / amd64 (with pkg updated right now): > pkg search gnome2 gnome2-office-2.32.1 gnome2-reference-2.20_1 > pkg search kde bmkdep-20131009 kde-xdg-env-1.0_3,1 kde4-icons-oxygen-4.10.5 kde4-shared-mime-info-1.2 kde4-wallpapers-freebsd-1.0 kde4-xdg-env-1.0.1 kdehier4-1.1.1_1 pam_kde-1.0 -- Daniel Nebdal ___ 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: Few missing packages from the new PKG repositories
On Sat, Nov 23, 2013 at 3:27 PM, Kimmo Paasiala wrote: > Were these left out by accident or why aren’t they included? > > - x11/gnome2, x11/gnome2-lite is in the repo. > > - editors/vim, editors/vim-lite is in the repo as well. > > -Kimmo > Do all the dependencies build with default options? I suspect that's why kde4 wasn't packaged last time I checked. (I guess we could take a look at the build logs from the new repository; I know they're out there somewhere.) -- Daniel Nebdal ___ 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: Determining file size of port source
On Fri, Nov 15, 2013 at 8:25 AM, Shane Ambler wrote: > On 15/11/2013 13:15, Joe Nosay wrote: > > On Wed, Nov 13, 2013 at 11:14 PM, Shane Ambler >wrote: > > >> You can use make makesum to create the distinfo for you - once you get > >> the download links right. > >> > >> Thanks. I'm still patching/rewriting files. One of my problems was not > > re-creating the folder properly and then archiving it. > > > > Another helpful command to use is make makepatch. While working on the > port, remember to make a copy of each file you adjust with a .orig > suffix, then you can use make makepatch to generate the patches for you. > > That's rather neat, and I didn't know about it. Thanks. --- Daniel Nebdal ___ 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 index` broken
On Thu, Oct 17, 2013 at 4:32 PM, Shawn Webb wrote:
> I'm on 11-current/amd64. I'm not sure if it's specific to me, but it looks
> like a change to the net/openbgpd port is causing `make index` to fail with
> the following error message:
>
> make[5]: Unknown modifier ')'
> make[5]: Unclosed variable specification (expecting '}') for "PORT_OPTIONS"
> (value "") modifier )
> make[5]: "/usr/ports/net/openbgpd/Makefile" line 31: Malformed conditional
> (${PORT_OPTIONS:MIPV6LLPEER))
> make[5]: Fatal errors encountered -- cannot continue===> net/openbgpd failed
> *** [describe.net] Error code 1
>
> Thanks,
>
> Shawn
It seems to be a typo in the latest commit - a ) that should be a }. I
sent a mail to hrs@ about it an hour or so ago, since he showed up as
the commiter.
--
Daniel Nebdal
___
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 disable staging support in ports tree universally?
On Sat, Oct 12, 2013 at 11:08 AM, Torfinn Ingolfsen wrote: > Hello, > > On Sat, Oct 12, 2013 at 10:15 AM, Matthew Seaman wrote: >> >> Staging is here to stay. There's no way of "turnng it off." If the > > Why? Why can't it be turned off? > What is the technical reason / reasoning behind this design decision? > And why is staging special, compared to all other features that has > been introduced to FreeBSD in the last few years? > > -- > Regards, > Torfinn Ingolfsen As I've understood it, it's not so much a "feature" as an infrastructure *change* - asking to disable it is, from now on, about as meaningful as asking if you could disable the fetch stage. -- Daniel Nebdal ___ 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: Explain staging
On Mon, Oct 7, 2013 at 2:52 PM, Anton Shterenlikht wrote: > >From b...@passap.ru Mon Oct 7 13:36:53 2013 >> >>07.10.2013 13:23, Anton Shterenlikht пишет: >> >>> What about "make fetch"? It puts files by default under >>> ports/distfiles, which, by default, is 755: >>[...] >>> What about "make extract"? Same problem: >> >>I use svn repo owned by a user for ages. When a root rights are needed, >>the ports infrastructure asks for the password. > > I've read a few books on unix security. > The typical advice is to assume the user > passwords are compromised. > If I build and install from a ports tree > owned by a user, I increase the chances of > comromising the system, if an attacker > changes some files in the ports tree, > i.e. the URL in the Makefile and the checksum > in distinfo. I'll then have to add this worry > to my already long list. > > Anton > If that happens to an account used by an admin, don't you have larger worries? Let's say : * You have an account with no special privileges, that you typically log in with. * That account has a ports tree * You typically install ports by compiling them as this user, then installing them with root privileges. If you use sudo, and you haven't used targetpw or something to make it ask for a different password, and you haven't set any strong limits on it, anyone that got your password would also be able to use sudo to do whatever they wanted more directly. So let's assume you're not doing that. An attacker with your password could meddle with your .profile or .cshrc or whatever, and replace your shell with a lookalike that logged all input. From there, they could get hold of whatever commands and passwords you use to install software, and reuse that to install whatever they want directly. If what you use is sudo, somehow restricted to only run make install, and only within that ports tree ... again, what would keep an attacker from just modifying any random port on the fly, installing it there and then, and then reverting the changes to reduce the risk of detection? It just seems like leaving a timebomb in the form of a modified ports directory would be a fairly inefficient thing to do if they'd already gotten that far., and it would run the risk of being overwritten and/or detected next time you updated your ports tree. Of course, if you set the ports tree a+w (or, heaven forbid, 0777), you'd be asking for trouble ... but that's not new. Then again, I might have overlooked something. :) -- Daniel Nebdal ___ 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] Staging, packaging and more
On Fri, Oct 4, 2013 at 3:16 PM, Mathias Picker wrote: > Am Freitag, den 04.10.2013, 06:12 -0500 schrieb Bryan Drewery: >> On Fri, Oct 04, 2013 at 09:01:58AM +0200, Baptiste Daroussin wrote: >> > On Fri, Oct 04, 2013 at 08:57:53AM +0200, Erwin Lansing wrote: >> > > On Fri, Oct 04, 2013 at 08:32:59AM +0200, Baptiste Daroussin wrote: >> > > > > > > > >> > > > > > > > Please no devel packages. >> > > > > > > >> > > > > > > Seconded. >> > > > > > >> > > > > > What's wrong with devel packages? >> > > > > >> > > > > It complicates things for developers and custom software on >> > > > > FreeBSD. The typical situation that I see on most Linux platforms is >> > > > > a >> > > > > lot of confusion by people, why their custom software XYZ does not >> > > > > properly build - the most common answer: they forgot to install a >> > > > > tremendous amount of dev packages, containing headers, build tools >> > > > > and >> > > > > whatnot. >> > > > > On FreeBSD, you can rely on the fact that if you installed e.g. >> > > > > libGL, >> > > > > you can start building your own GL applications without the need to >> > > > > install several libGL-dev, libX11-dev, ... packages first. >> > > > > This is something, which I personally see as a big plus of the >> > > > > FreeBSD >> > > > > ports system and which makes FreeBSD attractive as a development >> > > > > platform. >> > > > > >> > > > >> > > > On the other ends, that makes the package fat for embedded systems, >> > > > that also >> > > > makes some arbitrary runtime conflicts between packages (because they >> > > > both >> > > > provide the same symlink on the .so, while we could live with 2 >> > > > version at >> > > > runtime), that leads to tons of potential issue while building >> > > > locally, and >> > > > that makes having sometime insane issues with dependency tracking. Why >> > > > having >> > > > .a, .la, .h etc in production servers? It could greatly reduce PBI >> > > > size, etc. >> > > > >> > > > Personnaly I do have no strong opinion in one or another direction. >> > > > Should we be >> > > > nicer with developers? with end users? with embedded world? That is >> > > > the question >> > > > to face to decide if -devel packages is where we want to go or not. >> > > > >> > > >> > > If we chose to go down that path, at least we should chose a different >> > > name as we've used the -devel suffix for many years for developmental >> > > versions. >> > > >> > > I must agree that it is one of the things high on my list of things that >> > > irritate me with several Linux distributions but I can see the point for >> > > for embedded systems as well. But can't we have both? Create three >> > > packages, a default full package and split packages of -bin, -lib, >> > > and even -doc. My first though twas to make the full package a >> > > meta-package that would install the split packages in the background, >> > > but that would probably be confusing for users at the end of the day, so >> > > rather just have it be a real package. >> > > >> > I do like that idea very much, and it is easily doable with stage :) >> >> +1 to splitting packages for embedded usage. > > For me, the full packages of FreeBSD where allways one big plus. I > *hate* trying to compile anything and having to (find and) blow up my > package count. Just more things to keep track of. > > Disk space is cheap, and it's getting cheaper, even on embedded systems. > Is this really the time to optimize for a special case that might even > (slowly) fade away as storage even in tiny system grows and grows? > > > Regards, Mathias > > > > >> >> > >> > regards, >> > Bapt >> >> > Given that pkgng has feature flags, it could perhaps be doable to have a "WITH_DEV_FILES" (or whatever) flag, and defaulting to "yes". The embedded people could then set it to "no" and do a poudriere bulk build (or whatever they prefer) and get a nice slim set of packages with very little extra work. Ports could build-depend on a version with the appropriate flag set, and run-depend on versions without ... so if you try to compile something, it might be possible to drag the appropriate dev-enabled package versions in automatically. Depending on how feature flags actually work, of course; I might be optimistic here. :) Also, I wouldn't bet on embedded people getting unlimited amounts of space just yet. It's weird how slowly some fields move. -- Daniel Nebdal ___ 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"
print/cups-image, iconv linking issues
I'm not sure how this ties in with any other iconv issues. Yesterday, I did poudriere jails -u -j 10-amd64 -J 5 poudriere ports -u poudriere bulk -j 10-amd64 -J 5 -c print/cups-image Which should give me a clean and new CURRENT, update ports, and delete all previously built packages before trying to build print/cups-image . Relevant parts of the error log: ===> Installing existing package /packages/All/cups-client-1.5.4_1.txz Installing cups-client-1.5.4_1...Installing libiconv-1.14_1... done done ===> Returning to build of cups-image-1.5.4_1 (...) checking iconv.h usability... yes checking iconv.h presence... yes checking for iconv.h... yes checking for library containing iconv_open... none required (...) cc -L../cgi-bin -L../cups -L../filter -L../ppdc -L../scheduler -L/usr/local/lib -Wl,-rpath=/usr/lib:/usr/local/lib -Wl,-R/usr/local/lib -Wall -Wno-format-y2k -Wunused -fPIC -Os -g -fstack-protector -Wno-tautological-compare -o bannertops bannertops.o pstext.o common.o -lcupsimage \ -lcups -lssl -lcrypto -lz -pthread -lcrypt -lm -lssp_nonshared ../cups/libcups.so: undefined reference to `libiconv' ../cups/libcups.so: undefined reference to `libiconv_close' ../cups/libcups.so: undefined reference to `libiconv_open' cc: error: linker command failed with exit code 1 (use -v to see invocation) Complete error log for cups-image at http://hastebin.com/raw/nuvosimeva , and I have the other build logs at hand if those are interesting. Any ideas? -- Daniel Nebdal ___ 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: [patch]Uses/iconv.mk, devel/getext has no libiconv linkage.
On Sun, Aug 18, 2013 at 6:04 PM, Yamaya Takashi wrote: > On 2013/08/06 07:54, Boris Samorodov wrote: >> (CC to the maintainer: gn...@freebsd.org) >> >> 05.08.2013 20:13, Yamaya Takashi пишет: >>> Some ports, e.g. devel/glib20, cannot build because devel/gettext has no >>> libiconv linkage. >>> msgfmt cannot handle utf-8 and say "invalid multibyte sequence". >>> >>> Patch attached file and rebuild devel/gettext, msgfmt works correctly. >> Confirmed. The fix works. Thanks! >> > Please commit my patch. > It is not only for devel/gettext. > It's for some ports which have USES += iconv. > > This sounds like the underlying problem I have with print/cups-image, as well: It depends on iconv, but fails to add it to LDFLAGS when compiling. -- Daniel Nebdal ___ 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: name of a port that builds on 10-CURRENT but not 9?
On Sat, Jul 13, 2013 at 11:45 PM, Kevin Oberman wrote: > On Sat, Jul 13, 2013 at 2:15 PM, Aryeh Friedman > wrote: > >> I am making a port and need to see a good working example of how to >> make it so it will not compile on less then 10-CURRENT >> > > What exactly do you mean by 10-CURRENT? Head today, head this year, head > since 9 was branched? In any case, check OSVERSION. A great many ports may > be looked at for examples. E.g. graphics/blender. See the FreeBSD Porter's > Handbook 12.6. There is a list of every OSVERSION bump, but I can't > remember exactly where it is, but to check for 10, check if OSVERSION >>100. It's in the handbook as well: http://www.freebsd.org/doc/en/books/porters-handbook/freebsd-versions.html -- Daniel Nebdal ___ 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: kde3 ports expired today
On Tue, Jul 2, 2013 at 9:34 PM, Per olof Ljungmark wrote: > On 2013-07-02 18:31, Daniel Nebdal wrote: >> On Tue, Jul 2, 2013 at 5:55 PM, Jim Pingle wrote: >>> On 07/02/13 07:10, Matthias Apitz wrote: >>>> El día Monday, July 01, 2013 a las 08:05:37PM -0700, Jeffrey Bouquet >>>> escribió: >>>> >>>>> bsdstats.org > ports stats would have that information probably >>>> >>>> http://bsdstats.org/ports.php?category=91 >>>> >>>> says in column 'times in use': >>>> >>>> x11/kde3: 534 >>>> x11/kde4: 86 >>> >>> I feel as though I'm in the happy minority who use and enjoy KDE4. My >>> FreeBSD desktop/workstation is running it well but it does not have >>> limited resource requirements (i7-750, 8G of RAM, Radeon HD 4650). >>> >>> Since Amarok and K3B outgrew their KDE3 dependencies, I've managed to >>> keep my system KDE3/QT3-free for a while now, though that wasn't always >>> easy in the past. >>> >>> The only real hiccup I've had was the recent KDE4 bump that made me have >>> to reconfigure some things, but it ended up working better than ever in >>> the end. The only current complaint I have is about the atrocities they >>> have committed to KMail. >>> >>> Resource usage and philosophical reasons aside, some people who have >>> been burned by KDE4 in the past may want to revisit it now, it's matured >>> a lot from its early days. >>> >>> Personally I won't miss KDE3 at all, and I really haven't missed it for >>> several years now. >>> >>> Jim >> >> >> I was about to write something similar. My work machine has been on >> KDE4 for years, and though it was quite rocky in the earlier versions >> it has kind of quietly disappeared into the background (in a good way) >> now - while I can understand the gnome2 revival projects, I don't >> quite see the point of e.g. Trinity. > > Of course KDE4 works and many people use it daily - but for me who got > used to a fairly stripped desktop with just the basics I work with all > the time KDE4 was just in the way, in fact, it made me work more on > Windows XP. > > My hope now is that xfce grows just a little bit more in functionality > to be roughly a KDE3 successor. > > //per I haven't tried it, but Razor-Qt looks like a reasonable environment as well - though you need to add apps, like, oh, the KDE4 ones. Which might not be quite what you were after. x) ___ 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: kde3 ports expired today
On Tue, Jul 2, 2013 at 5:55 PM, Jim Pingle wrote: > On 07/02/13 07:10, Matthias Apitz wrote: >> El día Monday, July 01, 2013 a las 08:05:37PM -0700, Jeffrey Bouquet >> escribió: >> >>> bsdstats.org > ports stats would have that information probably >> >> http://bsdstats.org/ports.php?category=91 >> >> says in column 'times in use': >> >> x11/kde3: 534 >> x11/kde4: 86 > > I feel as though I'm in the happy minority who use and enjoy KDE4. My > FreeBSD desktop/workstation is running it well but it does not have > limited resource requirements (i7-750, 8G of RAM, Radeon HD 4650). > > Since Amarok and K3B outgrew their KDE3 dependencies, I've managed to > keep my system KDE3/QT3-free for a while now, though that wasn't always > easy in the past. > > The only real hiccup I've had was the recent KDE4 bump that made me have > to reconfigure some things, but it ended up working better than ever in > the end. The only current complaint I have is about the atrocities they > have committed to KMail. > > Resource usage and philosophical reasons aside, some people who have > been burned by KDE4 in the past may want to revisit it now, it's matured > a lot from its early days. > > Personally I won't miss KDE3 at all, and I really haven't missed it for > several years now. > > Jim I was about to write something similar. My work machine has been on KDE4 for years, and though it was quite rocky in the earlier versions it has kind of quietly disappeared into the background (in a good way) now - while I can understand the gnome2 revival projects, I don't quite see the point of e.g. Trinity. -- Daniel Nebdal ___ 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:58 PM, Chris Rees wrote: > On 7 June 2013 18:49, Andrew W. Nosenko wrote: >> On Fri, Jun 7, 2013 at 8:15 PM, Chris Rees 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 Even good translations can be annoying if you're trying to use them together with resources in English. (For values of "resources" that can also include searching for the exact error string online...) -- Daniel Nebdal ___ 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 Tue, May 28, 2013 at 1:05 AM, RW wrote: > On Mon, 27 May 2013 22:33:53 +0200 > John Marino wrote: > >> On 5/27/2013 22:09, RW wrote: >> > On Mon, 27 May 2013 20:38:11 +0200 >> > John Marino wrote: >> > >> > >> > No, that's something you just made up. It is however vague and >> > anecdotal. We have only one data point that we know is from this >> > year and not self-inflicted, even if the others are, for all we >> > know it could still be fast most of the time. >> > >> > Some monitoring would be useful. >> > >> >> However you slice it, a distinfo file with 1000+ entries is >> completely absurd. 95% of the blame goes to Vim developers. >> However, it is within the realm of feasibility to pre-package patches >> in batches of 100 (or conversely 1 tarball of patches rolled for >> every time patch count hits multiple of 100). > > In other words downloading every patch twice. > As a side note: Patches 100-199 (as an example) are 600KB, while a tar.xz of them is 115KB. Data-wise, it's closer to "downloading each patch 1.2 times". -- Daniel "let's poke the fresh paint on this bikeshed" Nebdal ___ 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: cups
Den 23. apr. 2013 17:00 skrev "M Rusli" følgende: > > Hi > > Is there any newer version of cups version 1.6.2 > > Because freebsd only have the older version 1.5.2. > > How do I know whether what usb printers commonly support Freebsd? You could check http://www.openprinting.org . As long as it doesn't require a binary it should be fine, and even if it does it can probably be made to work. At a guess, anything that speaks PCL or postscript should be OK; that includes most cheap lasers, but fewer of the inkjets. (I have no idea how this has changed the last years.) -- Daniel Nebdal ___ 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: Where has all the groupware gone.....
Den 23. apr. 2013 20:06 skrev "Adam Vande More" følgende: > > http://wiki.zimbra.com/wiki/Zimbra_on_FreeBSD#Downloads_.28stable.29 > > Haven't used this. > > Also Horde is as hard as you make it. Personally, I think dealing > with all XML and internal tools stuff on Zimbra is worse than Horde > and it's config files and dependencies. That being said, I haven't > used the new Horde stuff in ports, my install is still a couple of > years old. > > On Sun, Mar 17, 2013 at 2:46 PM, Paul Pathiakis wrote: > > Hi, > > > > I have tried building many pieces of groupware so that I can replace MS at various client sites. > > > > However: > > > > zimbra? No port. (Hardcoded /opt/zimbra) > > kolab? No port.(Hardcoded /kolab - This could work if they got rid of the idiocy of "OpenPKG") > > (A kolab port could easily be done if all the dependencies their rpms were made into a port for it. - It should work fairly easily with ZFS) > > > > Citadel? No port. Got it working and seems pretty decent. > > > > SimpleGroupware - Not DB independent, MySQL only > > Tine? Not DB independent, MySQL only (Who does that in this day and age?) > > > > Horde? Port is cumbersome and very few tips anywhere to get it up and running quickly on FreeBSD (Is there a doc I can't find?) > > Horde > > Web? Same as Horde > > > > Egroupware? Sweet... Works nice and seems very useful. Many compliments from people on how well it works. > > > > > > Phpgroupware? Not really groupware in the form of the others above. > > > > I'm just evaluating. I have no affiliation with any. However, the lack thereof when we could be inserting groupware FreeBSD servers in clients... :-) > > > > Thank you for checking into this and creating real ports and/or documentation. > > > > P. > > ___ > > 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" > > > > -- > Adam Vande More Well, the last time a friend of mine looked at the instructions for installing the current release (which is a version or two ahead of ports, I think), he claimed the instructions for setting up the SQL tables were "use the upgrade script to convert from the old version", with no instructions for new installs . I do hope he merely didn't find them, but that in itself might say something. :) -- Daniel Nebdal ___ 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: Growing list of required(ish) ports
On Tue, Apr 9, 2013 at 3:09 PM, Darren Pilgrim wrote: > On 2013-04-08 10:22, Florent Peterschmitt wrote: >> >> Yep, OpenSSH is tiny enought to keep it in base system. It would be a >> big loss not to have it by default, securely installed in the base >> system. > > > I really wish it wasn't. Having OpenSSH (and thus OpenSSL) in the base > means FreeBSD has an outdated version installed by default. You have to > install openssl from ports in order to have modern cipher support, TLS > v1.1/1.2, DTLS, etc. This puts two sets of openssl libs on the system and > creates recurrent headaches with builds where the autoconfiguration selects > the wrong set of libs. > > I guess it would be possible to rename it to something autoconf misses, so ports have to use the ports-version? It enforces some redundancy, though I won't speculate on how much disk space it works out to. -- Daniel Nebdal ___ 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: Mencoder/mplayer does not build
At a guess, it's a multithreaded build, so the error might be from another file.
It seems to be from this:
mr16613 work/mplayer-export-2013-03-08 # grep -r 'sse_int32_map_factor' .
./libmpcodecs/vf_ass.c:DECLARE_ASM_CONST(16, uint32_t, sse_int32_map_factor[4])
./libmpcodecs/vf_ass.c:"pmulld
"MANGLE(sse_int32_map_factor)", %%xmm0 \n\t"
./libmpcodecs/vf_ass.c:"pmulld
"MANGLE(sse_int32_map_factor)", %%xmm1 \n\t"
./libmpcodecs/vf_ass.c:"pmulld "MANGLE(sse_int32_map_factor)",
%%xmm0 \n\t"\
./libmpcodecs/vf_ass.c:"pmulld "MANGLE(sse_int32_map_factor)",
%%xmm1 \n\t"\
./libmpcodecs/vf_ass.c:"pmulld "MANGLE(sse_int32_map_factor)",
%%xmm2 \n\t"\
./libmpcodecs/vf_ass.c:"pmulld "MANGLE(sse_int32_map_factor)",
%%xmm3 \n\t"\
On Mon, Apr 8, 2013 at 5:34 PM, Lowell Gilbert
wrote:
> Bernt Hansson writes:
>
>> testbox# cd /usr/ports/multimedia/mencoder
>> testbox# make
>> ===> Building for mencoder-1.1.r20130308
>> ./codec-cfg etc/codecs.conf > codecs.conf.h
>> cc -MD -MP -Wundef -Wstrict-prototypes -Wmissing-prototypes
>> -Wdisabled-optimization -Wno-pointer-sign
>> -Wdeclaration-after-statement -std=gnu99 -O2 -pipe -O3
>> -fomit-frame-pointer -ffast-math -fno-strict-aliasing
>> -fno-tree-vectorize -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
>> -D_LARGEFILE64_SOURCE -Ilibdvdread4 -I. -Iffmpeg -I/usr/local/include
>> -I/usr/local/include -I/usr/local/include
>> -I/usr/local/include/freetype2 -I/usr/local/include
>> -I/usr/local/include -I/usr/local/include/dirac
>> -I/usr/local/include/schroedinger-1.0 -I/usr/local/include/orc-0.4
>> -c -o mpcommon.o mpcommon.c
>> Reading optional codecs config file etc/codecs.conf: 203 audio & 422
>> video codecs
>> cc -MD -MP -Wundef -Wstrict-prototypes -Wmissing-prototypes
>> -Wdisabled-optimization -Wno-pointer-sign
>> -Wdeclaration-after-statement -std=gnu99 -O2 -pipe -O3
>> -fomit-frame-pointer -ffast-math -fno-strict-aliasing
>> -fno-tree-vectorize -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
>> -D_LARGEFILE64_SOURCE -Ilibdvdread4 -I. -Iffmpeg -I/usr/local/include
>> -I/usr/local/include -I/usr/local/include
>> -I/usr/local/include/freetype2 -I/usr/local/include
>> -I/usr/local/include -I/usr/local/include/dirac
>> -I/usr/local/include/schroedinger-1.0 -I/usr/local/include/orc-0.4
>> -c -o libmpcodecs/vf_ass.o libmpcodecs/vf_ass.c
>> cc -MD -MP -Wundef -Wstrict-prototypes -Wmissing-prototypes
>> -Wdisabled-optimization -Wno-pointer-sign
>> -Wdeclaration-after-statement -std=gnu99 -O2 -pipe -O3
>> -fomit-frame-pointer -ffast-math -fno-strict-aliasing
>> -fno-tree-vectorize -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
>> -D_LARGEFILE64_SOURCE -Ilibdvdread4 -I. -Iffmpeg -I/usr/local/include
>> -I/usr/local/include -I/usr/local/include
>> -I/usr/local/include/freetype2 -I/usr/local/include
>> -I/usr/local/include -I/usr/local/include/dirac
>> -I/usr/local/include/schroedinger-1.0 -I/usr/local/include/orc-0.4
>> -c -o sub/subassconvert.o sub/subassconvert.c
>> {standard input}: Assembler messages:
>> {standard input}:543: Error: no such instruction: `pmulld
>> sse_int32_map_factor,%xmm0'
>> {standard input}:544: Error: no such instruction: `pmulld
>> sse_int32_map_factor,%xmm1'
>> {standard input}:1155: Error: no such instruction: `pmulld
>> sse_int32_map_factor,%xmm0'
>> {standard input}:1156: Error: no such instruction: `pmulld
>> sse_int32_map_factor,%xmm1'
>> {standard input}:1157: Error: no such instruction: `pmulld
>> sse_int32_map_factor,%xmm2'
>> {standard input}:1158: Error: no such instruction: `pmulld
>> sse_int32_map_factor,%xmm3'
>> {standard input}:1270: Error: no such instruction: `pmulld
>> sse_int32_map_factor,%xmm0'
>> {standard input}:1271: Error: no such instruction: `pmulld
>> sse_int32_map_factor,%xmm1'
>> {standard input}:1272: Error: no such instruction: `pmulld
>> sse_int32_map_factor,%xmm2'
>> {standard input}:1273: Error: no such instruction: `pmulld
>> sse_int32_map_factor,%xmm3'
>> gmake: *** [libmpcodecs/vf_ass.o] Fel 1
>> gmake: *** Inväntar oavslutade jobb...
>> *** Error code 1
>>
>> Stop in /usr/ports/multimedia/mencoder.
>> *** Error code 1
>>
>> Stop in /usr/ports/multimedia/mencoder.
>> testbox#
>
> Strange. sub/subassconvert.c only has 530 lines.
>
> What compiler are you using?
> ___
> 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-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: Growing list of required(ish) ports
On Mon, Apr 8, 2013 at 5:26 PM, Freddie Cash wrote: > Note: I may have messed up the quoting/attribution by snipping things. > > On Sun, Apr 7, 2013 at 10:11 PM, Kevin Oberman wrote: > >> On Sun, Apr 7, 2013 at 8:34 PM, Kimmo Paasiala wrote: >> >> > > On the other hand, there are a number of things that I think should be >> > > pulled out of base. Some already have ports, and others would need >> > > ports created. Examples of things to pull out of base are OpenSSL, >> > > Heimdal, OpenSSH, PF, ntpd, ipfilter, bind, sendmail, and others. >> > > Code that is typically way behind the upstream project basically. >> > > >> > >> > I think Bryan already explained the reasons why pkg should not be in >> > base, it's an external tool that is not strictly required to get a bare >> > bones FreeBSD system up and running. Including it in base you create >> > yet another maintainance burden and would slow down the development of >> > the ports/packages management tools. >> >> What people seem to miss is that putting tools into the base system >> strangles the tools. Look at the difficulty we have seen in updating >> openssl. perl was removed from base for exactly that reason. Once something >> is in base, it usually can only be updated on major releases and even then >> it can be very complicated. That is a problem for any dynamically changing >> tool. >> >> I would love to see BIND removed from base, but most of the things you >> listed really are hard to remove. I know that I don't want to try bringing >> up a new install of FreeBSD on a remote system without OpenSSH and that >> pulls in openssl. In the case of many tools, it really turns into a >> bikeshed. But i can see no reason to add any of the new packaging tools >> simply because it is critical that updates be possible far more often than >> is possible for the base system. >> >> Moving OpenSSH, OpenSSL, etc into the ports tree, but making the pkgs > available on the installation media, and having a final hook at the end to > install "required" pkgs, would solve that. There's already a "do you want > to enable OpenSSH daemon" question in the installed, so adding "pkg add > /path/to/openssh-x.y.z.txz" wouldn't be hard. > > Same for bind, sendmail, kerberos, etc. For instance, just add a "daemon > selection screen" for each bit removed from base, to select which ones you > want installed as part of the OS install. > > The hard part comes in finding stub/clients for each item moved to a pkg, > such that a desktop-oriented install is not hampered (ie, SSH client is > usable, DNS lookups can be done, local mail can be generated/delivered, > etc). > > The really hard part is coming up with a migration path for those who > upgrade via source builds. > -- > Freddie Cash > fjwc...@gmail.com There's also the issue that OpenSSH is used for remote administration - being able to do destructive things with pkg without worrying about continued SSH-access is rather relaxing. With danger of entering bikeshed territory, it's one of the things that makes FreeBSD more relaxing than the Linuxes: You can blast every installed package and still be fine - and a working sshd is a part of "fine" for me, since it's kind of a requirement for doing anything else. Admittedly, my personal worst-case scenario is "drag a monitor and keyboard to the other side of the room", so I will probably survive either way. :) -- Daniel Nebdal ___ 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: Request olvwm
Looking at it, the first problem is that x11-toolkits/xview has ONLY_FOR_ARCHS= i386 . Adding amd64 to it failed early with compilation errors (in some hairy macro definitions, by the look of it). Setting USE_GCC=4.2+ still produced a lot of warnings, but actually compiled and installed. Back in olwm, it then failed with much the same compiler errors; USE_GCC=4.2+ got past that again (I guess it's from the same header files as xview). It then compiled and installed. On trying to start it, it segfaulted. Recompiling with CFLAGS+=-g and starting it in gdb, I get this: mr16613: x11-wm/olvwm > gdb olvwm GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"...(no debugging symbols found)... (gdb) run Starting program: /usr/local/bin/olvwm (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. 0x0040f4bb in ?? () (gdb) bt #0 0x0040f4bb in ?? () #1 0x0042ede8 in olgx_draw_accel_button () #2 0x0043169f in olgx_draw_accel_button () #3 0x00428ded in olgx_draw_accel_button () #4 0x0042959e in olgx_draw_accel_button () #5 0x00421477 in olgx_draw_accel_button () #6 0x0040639f in ?? () #7 0x00080066c000 in ?? () #8 0x in ?? () (gdb) There is probably a good reason xview is marked as i386 - only. I guess I could recompile it with -g as well to see if I can find out what goes wrong, but ... I do have other things to do, and I know nothing about X or xview or olvwm. Maybe later? -- Daniel Nebdal On Mon, Apr 8, 2013 at 2:41 AM, Sergio de Almeida Lenzi wrote: > Em Dom, 2013-04-07 às 10:59 -0400, Lowell Gilbert escreveu: > >> Richard Childers writes: >> >> > I'm not sure if olvwm is getting any attention - I know there are >> > other projects with more users - but I wanted to say, I love that >> > window manager. >> >> Do you have any specific requests? The project hasn't had any releases >> upstream in years, so the fact that the FreeBSD port hasn't changed much >> doesn't seem like a problem... >> ___ >> 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" > > > Olvwm is a good choice for people that wants a small, fast, easy to > configure, and beautiful > look. Now the only problem is that it does not compile under 64bits... > > I tried to fix it but is beyound my knowledge.. > > If some X guru is available, please fix it for 64 bits... > > > Thanks for your attention, > > Sergio > ___ > 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-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 to packages question
On Fri, Mar 22, 2013 at 1:14 PM, David Southwell wrote: > Hi > > On a system with a large number of ports installed and where some have been > installed from binaries and some compiled what is the neatest way to remove > the binary packages and replace them with local compilations. > > Thanks in advance > David > > -- > David Southwell ARPS AFIAP > Photographic Arts > Trained & experienced competition judge, mentor, trainer, lecturer, > Advanced digital techniques, international project photography > > ___ > 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" It might actually be to get a list of all installed packages, deinstall everything, and then use portmaster to reinstall them. Alternatively, you could use poudriere to build packages of everything first, and then deinstall everything / reinstall from those locally built packages. (I believe you need a ZFS pool for poudriere, though?) The poudriere solution has the benefit that you can wait until you're sure everything has compiled successfully before doing anything dramatic, while still being sure everything really did get reinstalled cleanly. Exactly how to do the above depends - are you currently using pkgng? -- Daniel Nebdal ___ 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: [CFT] New dialog for ports
On Wed, Mar 20, 2013 at 1:19 PM, Vitaly Magerya wrote: > Daniel Nebdal wrote: >> I just found a niggle: >> I have LANG=en_US.UTF-8 , NCURSES_NO_UTF8_ACS=1, TERM=xterm, and I'm >> using putty to connect to a FreeBSD-10 machine running a snapshot from >> february with ports from an hour ago. Putty is set to Translation: >> UTF-8, and "use unicode line drawing code points". >> >> With those settings, dialog gives me nice line drawing characters (for >> some reason). If I unset NCURSES_NO_UTF8_ACS, all boxes are drawn >> using random letters instead. (jlmqx, to be exact.) > > They're not actually random; 'jlmqx' is the ASCII rendering of line > drawing characters in ACS (alternative charset), which putty doesn't > support in UTF-8 mode (therefore it shows the ASCII, not the ASC versions). > >> The problem: ports config dialogs are _always_ drawn with the same >> random letters, and I haven't found any setting or combination of >> settings that works. >> >> This is probably more of a mis-configuration on my side > > I'm seeing the same thing too. > > I think I've found what causes it: unlike dialog, dialog4ports does not > call setlocale(3) during startup. Try saving the attached patch as > 'ports-mgmt/dialog4ports/files/patch-dialog4ports.c' and reinstalling > dialog4ports; report back if it'll help. That works perfectly - thanks. ___ 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: [CFT] New dialog for ports
On Thu, Mar 14, 2013 at 10:55 AM, Baptiste Daroussin wrote: > Hi all, > > Ilya A. Arkhipov wrote dialog4ports which has just been added into the ports > tree ports-mgmt/dialog4ports, this is intended to be a replacement for > dialog(1) > designed specifically for the options, in particular for optionsng. > > It uses libdialog (recent version) and extend it with a new widget able to > deal > with both normal and radio options in the same window. > > dialog4ports will live forever in ports so that it can easily be updated and > get > support for new features on all supported arches at the same time. > > It bundles libdialog on FreeBSD versions that doesn't have a recent libdialog > in > base (read 8.x) > > dialog4ports also support a new feature: it has a help dialog to be able to > print a human readable help text if possible. > > Here is a patch to the ports tree that makes it use dialog4ports by default. > What it does is: > When make config is requested and dialog4ports is not installed yet the ports > tree will install dialog4ports first. > > New feature for maintainer, if a pkg-help file is found inside the port > directory then dialog will show to the user a help file is available et > propose > him to hint F1 or ^E to show the said help file > > http://people.freebsd.org/~bapt/d4p.diff > > Please test! > > regards, > Bapt I just found a niggle: I have LANG=en_US.UTF-8 , NCURSES_NO_UTF8_ACS=1, TERM=xterm, and I'm using putty to connect to a FreeBSD-10 machine running a snapshot from february with ports from an hour ago. Putty is set to Translation: UTF-8, and "use unicode line drawing code points". With those settings, dialog gives me nice line drawing characters (for some reason). If I unset NCURSES_NO_UTF8_ACS, all boxes are drawn using random letters instead. (jlmqx, to be exact.) The problem: ports config dialogs are _always_ drawn with the same random letters, and I haven't found any setting or combination of settings that works. This is probably more of a mis-configuration on my side than a dialog4ports problem, but still - it's slightly odd that it acts different than dialog. :) ___ 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: non-WWW calendar/diary software
I have not tried it, but how about the Lightning extension for Thunderbird? (It's an option in make config; I think it's on by default.) -- Daniel Nebdal On Thu, Mar 7, 2013 at 12:42 PM, Wojciech Puchar wrote: > anyone knows such a thing - with polish translation (or translations at all > so i can translate)? preferably integrated with GNOME2, not a must, but > DEFINITELY evolution bloatware. > > Something simple, just like gnote. > > I know davical+web browser and it works, but something that doesn't require > browser would be much better. > > ___ > 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-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: port building in CURRENT (including r247839) BROKEN
On Wed, Mar 6, 2013 at 11:11 AM, Daniel Nebdal wrote: > On Tue, Mar 5, 2013 at 1:10 PM, Hartmann, O. > wrote: >> On all FreeBSD boxes with >> FreeBSD 10.0-CURRENT #1 r247839: Tue Mar 5 12:28:12 CET 2013/amd64 the >> build of ports - or updating/upgrading ports is BROKEN! >> >> Every port which is about to be updated fails with >> >> [...] >> *** [do-extract] Signal 13 >> >> This is common on ALL CURRENT systems so I consider this a BREAKAGE. >> >> The problem is painful due to the fact that several kernel modules need, >> accordung to the entry 20130304: in /usr/src/UPDATING an update. >> >> devel/dbus isn't starting anymore on ALL systems, I couldn't figure out >> why. So X11 doesn't start either. And I can not rebuild those ports to >> accomplish what's suggested/required in UPDATING. >> >> Regards, >> Oliver > > There's a few posts in -current about the same thing, and it does not > appear to be limited to ports. > > Just going by the complaints, I would guess that something recently > committed subtly broke pipes (in certain circumstances). Signal 13 is > defined as "write to a pipe with no reader", so feel free to speculate > or debug. > > -- > Daniel Nebdal Ha, I see you were writing a sensible post to -current while I typed that - never mind me, then. :) -- Daniel Nebdal ___ 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: port building in CURRENT (including r247839) BROKEN
On Tue, Mar 5, 2013 at 1:10 PM, Hartmann, O. wrote: > On all FreeBSD boxes with > FreeBSD 10.0-CURRENT #1 r247839: Tue Mar 5 12:28:12 CET 2013/amd64 the > build of ports - or updating/upgrading ports is BROKEN! > > Every port which is about to be updated fails with > > [...] > *** [do-extract] Signal 13 > > This is common on ALL CURRENT systems so I consider this a BREAKAGE. > > The problem is painful due to the fact that several kernel modules need, > accordung to the entry 20130304: in /usr/src/UPDATING an update. > > devel/dbus isn't starting anymore on ALL systems, I couldn't figure out > why. So X11 doesn't start either. And I can not rebuild those ports to > accomplish what's suggested/required in UPDATING. > > Regards, > Oliver There's a few posts in -current about the same thing, and it does not appear to be limited to ports. Just going by the complaints, I would guess that something recently committed subtly broke pipes (in certain circumstances). Signal 13 is defined as "write to a pipe with no reader", so feel free to speculate or debug. -- Daniel Nebdal ___ 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: compiling thunderbird-esr
Right. Well, as long as the in-program method works I guess that's survivable. It ought to respect LANG as well, but I can't quite find the motivation to explore why it doesn't... -- Daniel Nebdal On Wed, Feb 27, 2013 at 6:55 PM, Wojciech Puchar wrote: >> What happens if you (in some terminal) first set LANG=pl_PL.UTF-8 , >> and then launch thunderbird? > > > i have pl_PL.ISO8859-2 but tested UTF-8 too, thunderbird seems to ignore it. > > >> >> -- >> Daniel Nebdal >> >> On Wed, Feb 27, 2013 at 12:55 PM, Wojciech Puchar >> wrote: >>> >>> compiled thunderbird-esr from ports, as well as thunderbird-esr-i18i and >>> added polish language. >>> >>> Thunderbird works fine in...english. >>> >>> No idea where to switch menu/message texts to polish. any help please? >>> ___ >>> 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-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-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: compiling thunderbird-esr
What happens if you (in some terminal) first set LANG=pl_PL.UTF-8 , and then launch thunderbird? -- Daniel Nebdal On Wed, Feb 27, 2013 at 12:55 PM, Wojciech Puchar wrote: > compiled thunderbird-esr from ports, as well as thunderbird-esr-i18i and > added polish language. > > Thunderbird works fine in...english. > > No idea where to switch menu/message texts to polish. any help please? > ___ > 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-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: Share /var/cache/pkg/ between machines
On Tue, Feb 26, 2013 at 3:57 AM, Aristedes Maniatis wrote: > I'd like to share packages between a couple of nearly identical machines in > a server farm. I think I have the following options: > > 1. Set up apache httpd on one primary machine to serve the packages to the > others by pointing website root to to /var/cache/pkg/ and setting > PACKAGESITE in the other servers. This looks like it might work except that > repo.txz is missing from /var/cache/pkg/ > > 2. rsync /var/cache/pkg/ from the primary machine to the others. Set > PACKAGESITE on all machines to point to some central repository where all > these packages originally were built (we run poudriere in another location). > > 3. Something else > > > How do other people cache/proxy built packages under pkgng? I don't want to > have to pull the same 80Mb JDK package onto 10 machines across the internet. > > > Thanks > > Ari > > One option is to use poudriere, and set WITH_PKGNG=yes in /usr/local/etc/poudriere.d/make.conf (or the appropriate one for one specific jail, if you have multiple). That should make it build pkgng-style packages, including a repo.txz - file. Then host the corresponding package directory with some http server, and set it as a pkgng packagesite on the others. I was playing with this a few weeks ago, and it took a few tries (including more than one "why doesn't it create a repo.txz") before I got it. -- Daniel Nebdal ___ 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-wm/windowmaker fails on undefined reference
Right, so it does find it - it just neglects to set the right flag later. If I manage to both find the time and reproduce it, I can dig a bit - though you're more likely to get a usful answer if someone that actually knows about this chimes in in the meantime. :) -- Daniel Nebdal On Tue, Feb 19, 2013 at 6:20 PM, Joseph A. Nagy, Jr wrote: > On 02/19/13 10:39, Daniel Nebdal wrote: >> >> The obvious issue is apparently that there's not an "-linotify" in >> that argument list (or, alternatively, that is uses inotify functions >> when it shouldn't) - though I'm far from sure why that would happen. >> Do you have devel/libinotify installed? What does "grep inotify >> work/Window*/config.log " say? >> >> >> -- >> Daniel Nebdal > > > configure:12047: checking sys/inotify.h usability > configure:12047: gcc -c -O2 -pipe -fno-strict-aliasing -Wall -Wextra > -Wno-sign-compare -Wno-unused-parameter -D_XOPEN_SOURCE=600 -DFREEBSD > -I/usr/local/include conftest.c >&5 > configure:12047: $? = 0 > configure:12047: result: yes > configure:12047: checking sys/inotify.h presence > configure:12047: gcpp -I/usr/local/include conftest.c > configure:12047: $? = 0 > configure:12047: result: yes > configure:12047: checking for sys/inotify.h > configure:12047: result: yes > ... > ac_cv_header_sys_inotify_h=yes > > > -- > Yours in Christ, > > Joseph A Nagy Jr > "Whoever loves instruction loves knowledge, But he who hates correction > is stupid." -- Proverbs 12:1 > Emails are not formal business letters, whatever businesses may want. > Original content CopyFree (F) under the OWL > http://copyfree.org/licenses/owl/license.txt ___ 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-wm/windowmaker fails on undefined reference
The obvious issue is apparently that there's not an "-linotify" in that argument list (or, alternatively, that is uses inotify functions when it shouldn't) - though I'm far from sure why that would happen. Do you have devel/libinotify installed? What does "grep inotify work/Window*/config.log " say? -- Daniel Nebdal On Tue, Feb 19, 2013 at 5:06 PM, Joseph A. Nagy, Jr wrote: > # uname -a > FreeBSD alex-laptop 9.1-RELEASE FreeBSD 9.1-RELEASE #8: Tue Jan 22 14:00:27 > CST 2013 root@alex-laptop:/usr/obj/usr/src/sys/ALEX-LAPTOP amd64 > > /bin/sh /usr/local/bin/libtool --tag=CC--mode=link gcc -O2 -pipe > -fno-strict-aliasing -Wall -Wextra -Wno-sign-compare -Wno-unused-parameter > -D_XOPEN_SOURCE=600 -DFREEBSD -L/usr/local/lib -o wmaker actions.o > appicon.o application.o appmenu.o balloon.o client.o colormap.o cycling.o > defaults.o dialog.o dock.o dockedapp.o event.o framewin.o geomview.o > icon.o main.o menu.o misc.o osdep_bsd.o monitor.o motif.o moveres.o > pixmap.o placement.o properties.o resources.o rootmenu.o screen.o session.o > shutdown.o switchpanel.o stacking.o startup.o superfluous.o switchmenu.o > texture.o usermenu.o xdnd.o xinerama.o xmodifier.o xutil.o wcore.o > wdefaults.o window.o winmenu.o winspector.o wmspec.o workspace.o > ../WINGs/libWINGs.la ../WINGs/libWUtil.la -lwraster -L/usr/local/lib > -R/usr/local/lib -lXrandr -lXinerama -lXext -lX11 -lm > libtool: link: gcc -O2 -pipe -fno-strict-aliasing -Wall -Wextra > -Wno-sign-compare -Wno-unused-parameter -D_XOPEN_SOURCE=600 -DFREEBSD -o > .libs/wmaker actions.o appicon.o application.o appmenu.o balloon.o client.o > colormap.o cycling.o defaults.o dialog.o dock.o dockedapp.o event.o > framewin.o geomview.o icon.o main.o menu.o misc.o osdep_bsd.o monitor.o > motif.o moveres.o pixmap.o placement.o properties.o resources.o rootmenu.o > screen.o session.o shutdown.o switchpanel.o stacking.o startup.o > superfluous.o switchmenu.o texture.o usermenu.o xdnd.o xinerama.o > xmodifier.o xutil.o wcore.o wdefaults.o window.o winmenu.o winspector.o > wmspec.o workspace.o -L/usr/local/lib ../WINGs/.libs/libWINGs.so > /usr/ports/x11-wm/windowmaker/work/WindowMaker-0.95.4/WINGs/.libs/libWUtil.so > /usr/local/lib/libXft.so /usr/local/lib/libfontconfig.so > /usr/local/lib/libfreetype.so -lbz2 /usr/local/lib/libexpat.so > ../WINGs/.libs/libWUtil.so /usr/local/lib/libwraster.so > /usr/local/lib/libtiff.so -llzma -ljbig -lz /usr/local/lib/libXpm.so -lpng > /usr/local/lib/libjpeg.so /usr/local/lib/libgif.so /usr/local/lib/libXmu.so > /usr/local/lib/libXt.so /usr/local/lib/libSM.so /usr/local/lib/libICE.so > /usr/local/lib/libXrandr.so /usr/local/lib/libXrender.so > /usr/local/lib/libXinerama.so /usr/local/lib/libXext.so > /usr/local/lib/libX11.so /usr/local/lib/libxcb.so /usr/local/lib/libXau.so > /usr/local/lib/libXdmcp.so /usr/local/lib/libpthread-stubs.so -lrpcsvc -lm > -Wl,-rpath -Wl,/usr/local/lib > main.o: In function `main': > main.c:(.text+0x707): undefined reference to `inotify_init' > main.c:(.text+0x73d): undefined reference to `inotify_add_watch' > *** [wmaker] Error code 1 > 1 error > *** [all] Error code 2 > 1 error > *** [all-recursive] Error code 1 > 1 error > *** [all] Error code 2 > 1 error > *** [do-build] Error code 1 > > Stop in /usr/ports/x11-wm/windowmaker. > *** [build] Error code 1 > > Stop in /usr/ports/x11-wm/windowmaker. > -- > Yours in Christ, > > Joseph A Nagy Jr > "Whoever loves instruction loves knowledge, But he who hates correction > is stupid." -- Proverbs 12:1 > Emails are not formal business letters, whatever businesses may want. > Original content CopyFree (F) under the OWL > http://copyfree.org/licenses/owl/license.txt > ___ > 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-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: PDF viewer that can rotate pages
Okular (from KDE4) can also do it ( View:Orientation:Rotate (left|right) ), though that only qualifies as "small" if you've already got KDE 4. -- Daniel Nebdal On Mon, Feb 18, 2013 at 12:16 PM, Andrea Venturoli wrote: > Hello. > > As per subject, I often get rotated PDFs, which are a pain to read. > Neither xpdf, nor kpdf allow me to rotate the page again. > Any suggestion for a reader that can? > Ideally small with few requirements, but, failing that, I'll accept > something big and fat, provided it's not Adobe Reader. > > 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" ___ 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: pkgng - one "ervery day anoying" problem
You might want to look at this: https://github.com/pkgtools/pkgtools/issues/44 In the meantime, could you deinstall/reinstall libreoffice? No guarantees, but maybe it'll clean things up. -- Daniel Nebdal On Mon, Feb 4, 2013 at 3:32 PM, Heino Tiedemann wrote: > Hi there, > > > from time to time I do this > > > , > | portsnap fetch update && portupgrade --fetch-only --all --keep-going > ` > > > Always, realy always(!)comes this message: > > > , > | Stale dependency: de-libreoffice-3.5.7 --> nss-3.14 -- manually run > 'pkgdb -F' to fix, or specify -O to force. > ` > > > I get this every time - again and again. > > > Well, I cannot run 'pkgdb -F' > > and pkg check does not help anyrthing. > > > > > WHAT TO DO? > > > 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" > ___ 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: editors/libreoffice pkg_add error
Out of disk space (in whatever location it decompresses to)? On Fri, Nov 30, 2012 at 8:41 AM, jb wrote: > Hi, > > what is this error about ? > > # pkg_add -r libreoffice > Fetching > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9.0-release/Latest > /libreoffice.tbz...lib/libreoffice/basis3.4/program/libunopkgapp.so: > bzip decompression failed > tar: Error exit delayed from previous errors. > Done. > # > ctl-c to abort > > http://www.freebsd.org/cgi/query-pr.cgi?pr=173965 > > jb > > > ___ > 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-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: Clang as default compiler November 4th
On Wed, Sep 12, 2012 at 10:59 PM, Doug Barton wrote: > On 9/12/2012 1:22 AM, Jerry wrote: >> On Tue, 11 Sep 2012 23:29:27 -1000 >> Doug Barton articulated: >> >>> What we need to do is what I and others have been asking to do for >>> years. We need to designate a modern version of gcc (no less than 4.6) >>> as the official default ports compiler, and rework whatever is needed >>> to support this. Fortunately, that goal is much more easily achieved >>> than fixing ports to build and run with clang. (It's harder than it >>> sounds because there are certain key libs that define some paths >>> depending on what compiler they were built with, but still easier >>> than dealing with clang in the short term.) >> >> That is a well thought out, highly intuitive and completely doable >> idea. Therefore it will be ignored. > > No, it'll be ignored because I suggested it. :) > >> It seems that the FreeBSD authors are more concerned with the >> licensing language of GCC than in getting a fully functioning port's >> compiler into the FreeBSD base system. > > Just to be clear, I'm not suggesting putting the "ports compiler" into > the base. I'm suggesting that it be managed as a port, just like pkg is. > This works fine for the ports that are already hard-coding compiler > dependencies, and mostly worked for me back when I get it a test run > when I made the suggestion years ago. The few glitches I (and others who > have done it since) ran into just need some elbow grease applied. > > By keeping ports-related things in the ports tree we gain a huge amount > of agility, and lose the concerns about licensing in the base. It's a > win/win. > > Doug > Three-ish things: a) Doesn't that remove all incentives for eventually converging on just one compiler (bar some specific exceptions)? a.1) Isn't that bad? b) Doesn't that mean that at some future point, we'll have to jump the ports compiler to a newer (probably much newer) version, with all the maintenance fun of that? c) I guess this still lets me use clang for most ports if I really wish to? (I've compiled most ports with clang for a while, and the speed + useful error messages would be hard to give up...) I'm not sure if those are big or small issues - probably a matter of taste. :) -- Daniel Nebdal ___ 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/mailman install problem python 2.6 import urandom
That's slightly bizarre - urandom should be in the os module. Just to verify: mr16613: > uname -srm FreeBSD 9.0-STABLE amd64 mr16613: > python2.7 --version Python 2.7.3 mr16613: > python2.7 -c 'from os import urandom as _urandom ; print str(_urandom)' Out of curiosity, could you try something in python? Start python2.7 , and enter import os dir(os) That ought to display a long list of things in the os module, including urandom. On Fri, Jun 15, 2012 at 1:50 AM, Gene wrote: > Hi All: > > Running 8.1 AMD64. I had python 2.6.8 installed. After upgrading several > ports, which installed python 2.7.3_2, scripts requiring 2.6 fail due to an > inability to import urandom from os. > > Now I'm not a python person by any means, but I was wondering where its > trying to find urandom. Could it be looking for 'dev/urandom'? Or perhaps > urandom from ports/math/mpc? > > In a few scripts I've changed 2.6 to 2.7 and they seem to work. Did > installing 2.7 alongside 2.6 break something? > > Specifically, right now I'm trying to install mail/mailman port which looks > for python 2.6. It terminates with the following: > > > Compiling /usr/local/mailman/Mailman/versions.py ... > Traceback (most recent call last): > File "bin/update", line 50, in > from Mailman import Utils > File "/usr/local/mailman/Mailman/Utils.py", line 32, in > import cgi > File "/usr/local/lib/python2.6/cgi.py", line 49, in > import mimetools > File "/usr/local/lib/python2.6/mimetools.py", line 6, in > import tempfile > File "/usr/local/lib/python2.6/tempfile.py", line 34, in > from random import Random as _Random > File "/usr/local/lib/python2.6/random.py", line 47, in > from os import urandom as _urandom > ImportError: cannot import name urandom > = > > I've googled and searched archives and all I can find is ubuntu problems > related to a virtual machine. > > Does anyone know what's going on? > > Thanks, > Gene > > -- > > ___ > 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-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: Continual error dialogs since upgrading some ports
On Mon, May 28, 2012 at 12:29 PM, Conrad J. Sabatier wrote: > Since upgrading a number of ports yesterday, I'm now being hounded > continually with error dialogs popping up with the message: > > "An internal system error has occurred > > A problem that we were not expecting has occurred. > Please report this bug in your distribution bugtracker with > the error description." > > The dialog is adorned with that little "lifesaver" image used by the > GNOME help system, as well as a "Show details" button. Unfortunately, > the details provided are a little vague, popping up another dialog > showing the same message as the initial dialog, but with a "More > details" dropdown button. "More details" provides only the following: > > "The backend exited unexpectedly. This is a serious error as the > spawned backend did not complete the pending transaction." > > Nowhere to be seen is any mention of exactly what program is spawning > these error dialogs. Anyone ever seen these and/or have any idea where > they might be coming from? > > Thanks! It seems to be a PackageKit thing - do you have a "check for new updates"-applet running, or something like that? (ref http://forums.freebsd.org/showthread.php?t=23959 ) -- Daniel Nebdal ___ 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: OpenOffice 3.4 fails to build
On Wed, May 9, 2012 at 3:54 PM, Andrea Venturoli wrote: > Hello. > > Sorry to come up with yet another problem... > > My build stops with: > >> Module 'libxmlsec' delivered successfully. 49 files copied, 0 files >> unchanged >> >> 1 module(s): >> bridges >> need(s) to be rebuilt >> >> Reason(s): >> >> ERROR: error 65280 occurred while making >> /usr/local/local/storage/alamartmp/usr/ports/editors/openoffice-3/work/aoo-3.4.0/main/bridges/source/cpp_uno/gcc3_freebsd_intel > > > This is an 8.2/i386 box. > > Any hint? > > bye & Thanks > av. If you cd to the bridges directory (/usr/local/local/storage/alamartmp/usr/ports/editors/openoffice-3/work/aoo-3.4.0/main/bridges , apparently) and run gmake, you might get some more useful error messages. -- Daniel Nebdal ___ 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: Binary packages for LibreOffice 3.5 or 3.4
On Wed, May 9, 2012 at 2:43 PM, Baptiste Daroussin wrote: > On Wed, May 09, 2012 at 07:59:15AM -0400, Robert Huff wrote: >> >> Daniel Nebdal writes: >> > > >> > > In the case of gcc46, when I execute the previous six lines, >> > > return to >> > > >> > /data/port-work/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2, >> > > and run "make", I get: >> > > >> > > it says: >> > > >> > > Error expanding embedded variable. >> > > >> > > (Per a previous message, I have re-compiled libcmis with >> > > gcc42.) >> > > >> > > Any ideas? >> > > >> > > >> > > Robert Huff >> > >> > >> > Try with gmake instead? >> >> After fishing in different directoroes, I did so and got: >> >> Entering >> /data/port-work/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/sal/textenc >> >> Entering >> /data/port-work/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/sal/util >> >> Making: libuno_sal.so.3 >> : ERROR: /usr/lib/libstdc++.so.6: version GLIBCXX_3.4.15 required by >> ../unxfbsd.pro/lib/check_libuno_sal.so.3 not found >> dmake: Error code 1, while making '../unxfbsd.pro/lib/libuno_sal.so.3' >> >> >> Robert Huff >> > > That was the problem I was speaking about mixing different libstdc++ the one > from base and the one from gcc46. > > I don't know how to fix this. > > regards, > Bapt Does this also happen when building libreoffice with clang? I just built it on 8.2 using clang, and that worked fine (apart from a failure in vcl, but that was caused by some leftover qt3 headers in /usr/local/include ). Daniel Nebdal ___ 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: Binary packages for LibreOffice 3.5 or 3.4
> > In the case of gcc46, when I execute the previous six lines, > return to > /data/port-work/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2, > and run "make", I get: > > it says: > > Error expanding embedded variable. > > (Per a previous message, I have re-compiled libcmis with > gcc42.) > > Any ideas? > > > Robert Huff Try with gmake instead? -- Daniel Nebdal ___ 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: Linux compatibility with more than one Linux installed?
On Wed, Nov 30, 2011 at 10:05 AM, Lars Engels wrote: > On Tue, Nov 29, 2011 at 03:27:15PM +0100, Alexander Leidinger wrote: >> Hi, >> >> you can install the gentoo linux-dist in parallel to the default >> linux-base. Gentoo will be in /usr/local, not in /compat/linux. As >> such you have to manually start programs there via chroot. This means >> you do not have access to you FreeBSD files like normally, except you >> do null-mounts into the gentoo area. It also means your experience >> will not be as "integrated" as with the defaut linux-base (the >> linux-base port does some effort to integrate FreeBSD config files and >> installed resources like fonts). >> >> Just switching between them, like changing a symlink, is theoretically >> possible, but the gentoo linux-dist port is not designed for this kind >> of integration. It's a linux-"dist" port, not a linux-"base" port. > > What is it good for, then? I'd guess it's useful if you want to build or install some more complicated linux software, since you can use portage to handle the installed software on the linux side independent of the FreeBSD side (and you get to use portage to install linux packages). Much the same idea as the debootstrap one, I guess. :) -- Daniel Nebdal ___ 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: Strange issues while upgrading ports
On Fri, Nov 25, 2011 at 2:12 PM, Marco Beishuizen wrote: > On Fri, 25 Nov 2011, the wise Kaya Saman wrote: > >> Then ran portupgrade -a >> >> for some weird reason the packages listed below didn't get upgraded; upon >> the error output 'portupgrade' was trying to replace the port with the same >> version: eg. apache-2.2.13 error came up with the fact that apache-2.2.13 >> was to be installed again but was already installed so I needed to run: make >> deinstall; make install; make clean in order to re-install apache22.. > > Did you csup your portstree first? > He used portsnap, which does the same thing. By the way: "portsnap fetch extract update" is pointless: "extract" gives you a clean copy of the last fetched version, and "update" extracts only what has changed since the last extract or update. Use "portsnap fetch extract" once, then "portsnap fetch update" from then on. (Or replace "fetch" with "cron" if you're doing this automatically - it adds a random delay to not overload the servers at popular times of the day.) -- Daniel Nebdal ___ 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: Strange issues while upgrading ports
On Fri, Nov 25, 2011 at 2:56 PM, Kaya Saman wrote: > On 11/25/2011 03:44 PM, Daniel Nebdal wrote: >> >> On Fri, Nov 25, 2011 at 2:12 PM, Marco Beishuizen wrote: >>> >>> On Fri, 25 Nov 2011, the wise Kaya Saman wrote: >>> >>>> Then ran portupgrade -a >>>> >>>> for some weird reason the packages listed below didn't get upgraded; >>>> upon >>>> the error output 'portupgrade' was trying to replace the port with the >>>> same >>>> version: eg. apache-2.2.13 error came up with the fact that >>>> apache-2.2.13 >>>> was to be installed again but was already installed so I needed to run: >>>> make >>>> deinstall; make install; make clean in order to re-install >>>> apache22.. >>> >>> Did you csup your portstree first? >>> >> He used portsnap, which does the same thing. >> By the way: "portsnap fetch extract update" is pointless: "extract" >> gives you a clean copy of the last fetched version, and "update" >> extracts only what has changed since the last extract or update. Use >> "portsnap fetch extract" once, then "portsnap fetch update" from then >> on. (Or replace "fetch" with "cron" if you're doing this automatically >> - it adds a random delay to not overload the servers at popular times >> of the day.) >> > Thanks for the tip! > > It's my first time updating/upgrading a FreeBSD system so any 'experienced' > advice is always valid and welcome :-) > Ah, right. :) The nice thing with "update" is that it's much faster than "extract" - as I'm sure you'll notice. -- Daniel Nebdal ___ 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: cvs checkout ./. csup
On Tue, Nov 15, 2011 at 12:00 PM, Matthew Seaman wrote: > On 15/11/2011 09:48, Matthias Apitz wrote: >> Since many years I'm fetching or updating /usr/ports with >> >> # cd /usr >> # setenv CVSROOT :pserver:anon...@anoncvs.fr.freebsd.org:/home/ncvs >> # cvs checkout ports >> >> and later do the updating just with: >> >> # cd /usr/ports >> # cvs update >> # portupgrade -ai >> >> The FreeBSD handbook describes (or recommends?) using 'csup' for >> updating ports tree... What is the advantage (or reason, if any)? > > Efficiency, basically. csup should require less bandwidth and put less > load on servers than using cvs directly. It works like rsync, only > transferring the parts of the files that changed but exploiting the cvs > revision history to produce more specific and minimal deltas than you > can get just by using the standard rsync algorithm. > > However csup(1) doesn't give you any of the VCS features you'ld get by > doing a cvs checkout -- so no simple way to diff a local copy against > the repo, etc. etc. 'cvs checkout' of all or parts of the ports is still > frequently preferable for developing rather than just using the ports. > > There are also many more cvsup servers worldwide than there are anon-cvs > servers. > There's also portsnap, which has been in the base system for a while now. It has some of the same drawbacks as csup/cvsup (no VCS features), but is in my experience faster than them. In short, you can use "portsnap fetch extract" to download a complete compressed tarball of current ports and extract it, and after doing that you can use "portsnap fetch update" to update to the current state. Read the manpage; there are some important details. It uses a binary patch system that's quite efficient, so if you just want an updated /usr/ports , it's probably the fastest solution. (I think the exact method is that "fetch" grabs a tarball if it doesn't exist. If it does exist, it gets the binary patches required to update it to the current state. With it in place, "extract" unpacks the entire thing, and "update" only extracts the files touched by the last "fetch"-command.) It has a handbook page: http://www.freebsd.org/doc/handbook/portsnap.html -- Daniel Nebdal ___ 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: Perl is non-threaded. Building ImageMagick without threads.
On Sun, May 29, 2011 at 3:27 PM, Robert Huff wrote: > > Helmut Schneider writes: > >> While updating ImageMagick from 6.6.7.10 to 6.7.0-2 the build process >> says: >> >> ===> Configuring for ImageMagick-nox11-6.7.0.2 >> ### >> NOTICE: Perl is non-threaded. Building ImageMagick without threads. >> ### >> >> But: >> >> [helmut@BSDHelmut832 ~]$ pkg_info | grep perl >> perl-threaded-5.10.1_3 Practical Extraction and Report Language >> [helmut@BSDHelmut832 ~]$ uname -rms >> FreeBSD 8.2-RELEASE-p1 i386 >> [helmut@BSDHelmut832 ~]$ > > I have a similar issue: > > huff@> portupgrade InageMagick-6 > ** Port marked as IGNORE: graphics/ImageMagick: > OpenEXR requires threads. . Perl is non-threaded. Reinstall Perl with > threads or undefine WITH_IMAGEMAGICK_PERL > ** Listing the failed packages (-:ignored / *:skipped / !:failed) > - graphics/ImageMagick (marked as IGNORE) > huff@> dir /var/db/pkg | grep perl > drwxr-xr-x 2 root wheel 512 May 27 08:09 perl-threaded-5.14.0 > > System info: > > FreeBSD 9.0-CURRENT #0: Mon Apr 18 11:59:37 EDT 2011 amd64 > > > Robert Huff Try enabling threading in the ImageMagic port - I ran into this earlier, and if I remember it correctly, the error message is a bit misleading. -- Daniel Nebdal ___ 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: Firefox 4 with PGO compile error
On Thu, May 26, 2011 at 4:31 AM, Neko Chang wrote: > 2011/5/25 Daniel Nebdal : >> On Wed, May 25, 2011 at 5:22 AM, Neko Chang wrote: >>> Hi FreeBSD team :D >>> >>> I tried build firefox 4 with PGO support via ports under GNOME >>> 2.32.1(ordinary user, but build firefox by root), but build fail. >>> Later I posted the problem to FreeBSD support >>> forums,(http://forums.freebsd.org/showthread.php?t=23827) >>> But can't solve it. >>> >>> So I write the mail :D >>> Please help me >>> >>> * Output from 'uname -a'. >>> FreeBSD epopen.com 8.2-STABLE FreeBSD 8.2-STABLE #0: Sat Apr 23 >>> 16:23:23 CST 2011 localhost:/usr/obj/usr/src/sys/Kernel amd64 >>> >>> * Output from 'ident /usr/ports/www/firefox/Makefile' >>> /usr/ports/www/firefox/Makefile: >>> $FreeBSD: ports/www/firefox/Makefile,v 1.240 2011/04/29 06:31:39 flo >>> Exp $ >>> >>> * Where/when did the problem occur: configuring, building, or running >>> firefox >>> Build. >>> >>> * How can you reproduce the problem? >>> If turn-on PGO in "make config" >>> >>> Under is error message >>> >>> if test -d ../../../../dist/bin ; then touch >>> ../../../../dist/bin/.purgecaches ; fi >>> gmake[5]: Leaving directory >>> `/usr/ports/www/firefox/work/mozilla-2.0/obj-amd64-unknown-freebsd8.2/other-licenses/branding/firefox/locales' >>> hg: not found >>> Making langpack >>> /usr/ports/www/firefox/work/mozilla-2.0/obj-amd64-unknown-freebsd8.2/browser/locales/../../dist/install/firefox-4.0.1.en-US.langpack.xpi >>> /usr/ports/www/firefox/work/mozilla-2.0/obj-amd64-unknown-freebsd8.2/config/nsinstall >>> -D ../../dist/install/ >>> /usr/local/bin/perl5.12.3 >>> /usr/ports/www/firefox/work/mozilla-2.0/config/preprocessor.pl >>> -DOSTYPE=\"FreeBSD8\" -DOSARCH=FreeBSD -DAB_CD=en-US >>> -DMOZ_LANGPACK_EID=langpack-en...@firefox.mozilla.org >>> -DMOZ_APP_VERSION=4.0.1 >>> -DLOCALE_SRCDIR=/usr/ports/www/firefox/work/mozilla-2.0/browser/locales/en-US >>> -DPKG_BASENAME="firefox-4.0.1.en-US.freebsd8.2-amd64" >>> -DPKG_INST_BASENAME="firefox-4.0.1.en-US.freebsd8.2-amd64.installer" >>> -DDLL_PREFIX=lib -DDLL_SUFFIX=.so -DBIN_SUFFIX= -DHAVE_64BIT_OS=1 >>> -DMOZILLA_VERSION=\"2.0.1\" -DMOZILLA_VERSION_U=2.0.1 -DD_INO=d_ino >>> -DSTDC_HEADERS=1 -DHAVE_SSIZE_T=1 -DHAVE_ST_BLKSIZE=1 >>> -DHAVE_SIGINFO_T=1 -DHAVE_INT16_T=1 -DHAVE_INT32_T=1 -DHAVE_INT64_T=1 >>> -DHAVE_UINT=1 -DHAVE_UINT16_T=1 -DHAVE_VISIBILITY_HIDDEN_ATTRIBUTE=1 >>> -DHAVE_VISIBILITY_ATTRIBUTE=1 -DHAVE_DIRENT_H=1 -DHAVE_GETOPT_H=1 >>> -DHAVE_MEMORY_H=1 -DHAVE_UNISTD_H=1 -DHAVE_NL_TYPES_H=1 >>> -DHAVE_X11_XKBLIB_H=1 -DHAVE_SYS_STATVFS_H=1 -DHAVE_MMINTRIN_H=1 >>> -DHAVE_SYS_CDEFS_H=1 -DHAVE_DLOPEN=1 -DHAVE_DLADDR=1 -DFUNCPROTO=15 >>> -DHAVE_XSHM=1 -DHAVE_LIBXSS=1 -DHAVE_FT_BITMAP_SIZE_Y_PPEM=1 >>> -DHAVE_FT_GLYPHSLOT_EMBOLDEN=1 -DHAVE_FT_LOAD_SFNT_TABLE=1 >>> -DHAVE_FT_SELECT_SIZE=1 -D_REENTRANT=1 -D_THREAD_SAFE=1 >>> -DHAVE_RANDOM=1 -DHAVE_STRERROR=1 -DHAVE_LCHOWN=1 -DHAVE_FCHMOD=1 >>> -DHAVE_SNPRINTF=1 -DHAVE_MEMMOVE=1 -DHAVE_SETBUF=1 -DHAVE_ISATTY=1 >>> -DHAVE_FLOCKFILE=1 -DHAVE_LOCALTIME_R=1 -DHAVE_STRTOK_R=1 >>> -DHAVE_CLOCK_MONOTONIC=1 -DHAVE_LANGINFO_CODESET=1 -DVA_COPY=va_copy >>> -DHAVE_VA_COPY=1 -DHAVE_VA_LIST_AS_ARRAY=1 -DHAVE_THREAD_TLS_KEYWORD=1 >>> -DMALLOC_H=\ -DHAVE_STRNDUP=1 -DHAVE_POSIX_MEMALIGN=1 >>> -DHAVE_VALLOC=1 -DHAVE_I18N_LC_MESSAGES=1 -DHAVE_LOCALECONV=1 >>> -DNS_ALWAYS_INLINE=__attribute__\(\(always_inline\)\) >>> -DNS_ATTR_MALLOC=__attribute__\(\(malloc\)\) >>> -DNS_WARN_UNUSED_RESULT=__attribute__\(\(warn_unused_result\)\) >>> -DNS_NORETURN=__attribute__\(\(noreturn\)\) -DMOZ_PHOENIX=1 >>> -DMOZ_BUILD_APP=browser -DMOZ_X11=1 -DMOZ_WIDGET_GTK2=1 >>> -DMOZ_PDF_PRINTING=1 -DMOZ_ENABLE_XREMOTE=1 -DMOZ_OFFICIAL_BRANDING=1 >>> -DMOZ_DISTRIBUTION_ID=\"org.mozilla\" -DMOZ_PANGO=1 >>> -DMOZ_ENABLE_GNOMEVFS=1 -DMOZ_ENABLE_GCONF=1 -DMOZ_ENABLE_LIBNOTIFY=1 >>> -DMOZ_ENABLE_GNOMEUI=1 -DMOZ_ENABLE_DBUS=1 -DIBMBIDI=1 >>> -DMOZ_VIEW_SOURCE=1 -DACCESSIBILITY=1 -DMOZ_JSLOADER=1 -DNS_PRINTING=1 >>> -DNS_PRINT_PREVIEW=1 -DMOZ_OGG=1 -DATTRIBUTE_ALIGNED_MAX=64 >>> -DMOZ_WEBM=1 -DVPX_X86_ASM=1 -DMOZ_WAVE=1 -DMOZ_SYDNEYAUDIO=1 >>> -DMOZ_MEDIA=1 -DMOZ_VORBIS=1 -DMOZ_XTF=1 >>> -DMOZ_CRASHREPORTER_E
Re: Firefox 4 with PGO compile error
ID=\"20100101\" -DMOZ_DLL_SUFFIX=\".so\" > -DHAVE_FONTCONFIG_FCFREETYPE_H=1 -DXP_UNIX=1 -DUNIX_ASYNC_DNS=1 > -DMOZ_ACCESSIBILITY_ATK=1 -DATK_MAJOR_VERSION=1 -DATK_MINOR_VERSION=32 > -DATK_REV_VERSION=0 > -I/usr/ports/www/firefox/work/mozilla-2.0/toolkit/locales/en-US/defines.inc > -I/usr/ports/www/firefox/work/mozilla-2.0/browser/locales/en-US/defines.inc > /usr/ports/www/firefox/work/mozilla-2.0/browser/locales/generic/install.rdf >> ../../dist/xpi-stage/locale-en-US/install.rdf > cd ../../dist/xpi-stage/locale-en-US && \ > /usr/local/bin/zip -r9D > /usr/ports/www/firefox/work/mozilla-2.0/obj-amd64-unknown-freebsd8.2/browser/locales/../../dist/install/firefox-4.0.1.en-US.langpack.xpi > install.rdf chrome chrome.manifest -x chrome/en-US.manifest > adding: install.rdf (deflated 50%) > adding: chrome/en-US.jar (deflated 75%) > adding: chrome.manifest (deflated 78%) > gmake[4]: Leaving directory > `/usr/ports/www/firefox/work/mozilla-2.0/obj-amd64-unknown-freebsd8.2/browser/locales' > gmake[3]: Leaving directory > `/usr/ports/www/firefox/work/mozilla-2.0/obj-amd64-unknown-freebsd8.2/browser/installer' > gmake tools > gmake[3]: Entering directory > `/usr/ports/www/firefox/work/mozilla-2.0/obj-amd64-unknown-freebsd8.2/browser/installer' > gmake[3]: Nothing to be done for `tools'. > gmake[3]: Leaving directory > `/usr/ports/www/firefox/work/mozilla-2.0/obj-amd64-unknown-freebsd8.2/browser/installer' > if test -d ../../dist/bin ; then touch ../../dist/bin/.purgecaches ; fi > hg: not found > gmake[2]: Leaving directory > `/usr/ports/www/firefox/work/mozilla-2.0/obj-amd64-unknown-freebsd8.2/browser/installer' > gmake[1]: Leaving directory > `/usr/ports/www/firefox/work/mozilla-2.0/obj-amd64-unknown-freebsd8.2' > OBJDIR=obj-amd64-unknown-freebsd8.2 /usr/local/bin/python2.7 > obj-amd64-unknown-freebsd8.2/_profile/pgo/profileserver.py > args: > ['/usr/ports/www/firefox/work/mozilla-2.0/obj-amd64-unknown-freebsd8.2/dist/firefox/firefox-bin', > '-no-remote', '-profile', > '/usr/ports/www/firefox/work/mozilla-2.0/obj-amd64-unknown-freebsd8.2/_profile/pgo/pgoprofile/', > 'http://127.0.0.1:/index.html'] > INFO | automation.py | Application pid: 95151 > > (firefox-bin:95151): GnomeUI-WARNING **: While connecting to session manager: > None of the authentication protocols specified are supported. > ** > GLib-GIO:ERROR:gdbusconnection.c:2270:initable_init: assertion failed: > (connection->initialization_error == NULL) > TEST-UNEXPECTED-FAIL | automation.py | Exited with code -6 during test run > INFO | automation.py | Application ran for: 0:00:03.279356 > INFO | automation.py | Reading PID log: /tmp/tmpJZSM19pidlog > gmake: *** [profiledbuild] Error 250 > *** Error code 1 > > Stop in /usr/ports/www/firefox. > *** Error code 1 > > Stop in /usr/ports/www/firefox. > [/usr/ports/www/firefox]# > > > Make start, System print-out under message > To build Firefox with PGO support you need a running X server and > build this port with an user who could access the X server! > > During the build a Firefox instance will start and run some test. > Do not interrupt or close Firefox during this tests! > > The message and error log, I think firefox need connect a daemon > (localhost:) if PGO support ON when build. > But I don't know what daemon need, even Google. > > If I help to debug, Please tell me. > Thanks your hard work, Let us good firefox :D > I *think* that error is because it expects a gnome session (or at least a dbus server) to be available. If you used plain "su" to become root, it won't have the right environment. Could you try either sudo or su -m ? As for the : , I think that's just a build-internal thing: To profile, it starts firefox and displays a bunch of web pages, and I think it runs a small python web-server on localhost: to serve them. -- Daniel Nebdal ___ 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: gnome-translate-0.99_14 problem
On Tue, Mar 15, 2011 at 3:19 PM, Alexey Zaivenko - Vysochin wrote: > Hello! > > I was trying to install the port textproc/gnome-translate > (gnome-translate-0.99_14), but a problem occurred. > And I have upgraded perl to 5.12.3 version earlier. > > [root@lucky /usr/ports/textproc/gnome-translate]# make install clean (...) > checking for XML::Parser... configure: error: XML::Parser perl module is > required for intltool (...) It sounds like you're missing textproc/p5-XML-Parser , which is listed in RUN_DEPENDS for textproc/intltool . Could you check if both are indeed installed? If you just want a workaround, I suggest you try (re)installing textproc/p5-XML-Parser - but it'd probably be useful to track down what has happened. -- Daniel Nebdal ___ 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"
