Circular dependency in devel/doxygen?
I tried to build swfdec and gnash and failed with === pulseaudio-0.9.22_1 depends on shared library: ck-connector.0 - found === pulseaudio-0.9.22_1 depends on shared library: jack.0 - not found ===Verifying install for jack.0 in /BETA1/usr/ports/audio/jack === jackit-0.118.0_4 depends on executable: doxygen - not found ===Verifying install for doxygen in /BETA1/usr/ports/devel/doxygen make: Max recursion level (500) exceeded. *** Error code 2 Stop in /BETA1/usr/ports/audio/jack. *** Error code 1 Stop in /BETA1/usr/ports/audio/pulseaudio. *** Error code 1 Stop in /BETA1/usr/ports/audio/libcanberra. *** Error code 1 Stop in /BETA1/usr/ports/x11/libgnome. *** Error code 1 Stop in /BETA1/usr/ports/x11-toolkits/libbonoboui. *** Error code 1 Stop in /BETA1/usr/ports/graphics/graphviz. *** Error code 1 Stop in /BETA1/usr/ports/devel/doxygen. *** Error code 1 and about 500 more lines with these Stop in ... messages. It looks like the build process got caught in a loop. It also happened repeatedly, even after I ran make clean and tried to build devel/doxygen. I ran make missing | tee makemissing.log in /BETA1/usr/ports/devel/doxygen directory and got graphics/graphviz print/dvipsk-tetex print/teTeX devel/qt4-corelib x11-toolkits/qt4-gui devel/qt4-moc devel/qmake4 devel/qt4-rcc textproc/qt4-xml x11-toolkits/libbonoboui x11/libgnome graphics/libgnomecanvas x11-toolkits/libgnomeui print/tex-texmflocal print/teTeX-texmf print/teTeX-base www/libwww print/cm-super print/xdvik devel/qt4-uic net/openldap24-sasl-client audio/libcanberra security/gnome-keyring devel/gvfs misc/gnome-icon-theme print/font-amsfonts textproc/texi2html x11-fonts/p5-type1inst devel/libgee audio/pulseaudio security/libgnome-keyring devel/libsoup-gnome sysutils/libcdio graphics/libgphoto2 sysutils/gnome-mount x11-themes/icon-naming-utils audio/jack security/libtasn1 databases/sqlite3 audio/libcddb audio/cdparanoia graphics/libexif sysutils/policykit-gnome textproc/p5-XML-Simple textproc/docbook-420 textproc/docbook-430 textproc/docbook-440 textproc/docbook-450 textproc/docbook-xml-430 textproc/docbook-xml-440 textproc/docbook-500 textproc/xmlcharent devel/doxygen audio/portaudio audio/celt textproc/gnome-doc-utils textproc/p5-XML-SAX-Expat textproc/py-libxml2 lang/gawk textproc/p5-XML-SAX textproc/p5-XML-NamespaceSupport I noticed the line /devel/doxygen, meaning that /devel/doxygen depends on itself with many intermediate steps. Or it could be one of the list of dependencies in turn having /devel/doxygen as a dependency. So I am at an impasse here on my intended multimedia installation. Sorry if message is long, but I need to include the evidence. Or is it possible that I have something incompatible in the configuration (make config-recursive)? I wish I could run make config-recursive again and make changes to something less ambitious. Tom ___ 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
Substitute dependencies?
Is there any way to substitute dependencies, in cases where the substitute would work as well or better? First case I think of is the misc/freebsd-doc-* ports which want links1, which would be redundant if I already have lynx installed, or lynx and seamonkey too. I don't really like links1, prefer links with graphic capability though links with graphics is still a lame horse compared to Firefox or Seamonkey. I have viewed the FreeBSD Handbook quite successfully with Seamonkey, even Lynx. Another case I think of is mysql as a dependency when the user might prefer MariaDB or PostgreSQL. I think I saw something but can't find it any more. Tom ___ 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: Circular dependency in devel/doxygen?
From Scot Hetzel swhet...@gmail.com: The circular dependancy is being caused by audio/jack, graphics/graphviz and devel/sdl12: audio/pulseaudio - audio/jack -- devel/doxygen --- graphics/graphviz graphics/devil - devel/sdl12 -- audio/pulseaudio There are several ways to break the circular dependancy: 1. Turn the DOC option OFF for audio/jack. 2. define NOPORTDOCS when installing devel/doxygen (breaks dependancy on graphics/graphviz) 3. Turn the DEVIL option OFF for graphics/graphviz 4. Turn the PULSEAUDIO option OFF for devel/sdl12 I already had DEVIL off for graphics/graphviz. Browsing http://www.freshports.org/commits.php shortly after midnight UTC, I found an update to audio/jack, so I later ran portsnap fetch update How do you define NOPORTDOCS, do you insert -D NOPORTDOCS in 'make' command, like make -D NOPORTDOCS package-recursive | tee build.log which would save packages in addition to installing? What does NOPORTDOCS do in devel/doxygen? Do I lose a lot of important documentation? What is doxywizard? Having DOCS option on in audio/jack adds an intimidating load of dependencies, as I found through make missing | more maybe more than the ports framework can handle? Tom ___ 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
Status of cups-base and avahi-app?
What is the current status of print/cups-base? I get a BROKEN message when trying to build that port with DNSSD which is in net/avahi-libdns. This is for FreeBSD 9.0-BETA2. I didn't get this message in BETA1, but building print/cups-base failed because of something missing. My purpose for building cups-base is as a dependency of print/hplip, needed so I can print with the HP LaserJet n1212mf, using either the USB or ethernet connection. Is there any substitute for cups, or what is the function of avahi for this application (print/hplip)? Do I lose anything by turning off this option (DNSSD)? Tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Status of cups-base and avahi-app?
From Chris Rees cr...@freebsd.org: Well... you lose avahi, which is a zeroconf implementation, but you're probably just better off with samba. The BROKEN message references http://www.avahi.org/ticket/303 -- look there for more information on why it's marked as such. Chris I found that avahi bug ticket, noticed some Linuxes, including Ubuntu, manage to work around the bug. I guess I'll turn off the avahi option. What counts is getting the printer to work with hplip. I might also try to build wine and see if the MS-Windows driver for the printer works that way. Tom ___ 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: Circular dependency in devel/doxygen?
time for my dime's worth of questions. is there any way of building that audio/video app or plugin that works with linux? it is from adobe and works with pc-bsd. we've got a free version. is it flash? this is the main reason i switched to ubuntu for my desktop. so i can watch sites like pbs.org and npr.org. stream igages with sound. in my opinion, it is this that stalls the broader use of all of the berkeley distributions. Gary Kline kl...@thought.org http://www.thought.org Public Service Unix I was successful with doxygen in FreeBSD 9.0-BETA1; trouble came in BETA2. Do you mean Adobe (formerly Macromedia) Flash? There's gnash and swfdec with swfdec-gnome. I'm not sure how to select swfdec(-gnome). Gnash is good on YouTube but dead on many other sites, such as Yahoo. Then there are some web sites that use Adobe Flash apparently just to annoy the user: no YouTube-style movie, nothing that looks like a Flash video. Examples are freefilefillableforms.com and online ads on shoplocal.com, though shoplocal.com also offers html (dialup mode). Can mplayer or vlc, or maybe other multimedia ports, play .flv files, or be used as a Flash plugin? Tom ___ 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
Options for emulators/wine?
I see seven options for emulators/wine port, all turned off by default: OPTIONS=CUPSUse CUPS (Common UNIX Printing System)Off \ GNUTLS Use GnuTLSOff \ HAL Use HAL (Hardware Abstraction Layer) Off \ LDAPUse LDAP Off \ LIBXSLT Use libxslt (only used by msxml3.dll) Off \ OPENAL Use OpenAL (3D audio library) Off \ WINEMAKER Fully support winemaker (requires Perl) Off I want to know which ones I need in order to print and get other functionality. Do I need CUPS to print with wine, or will printing work the MS-Windows way without cups? I also want fax and scanning for my multifunction laser printer, HP n1212mf. I don't even know what winemaker is, and don't know if HAL would be desirable or would get in the way. Tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Options for emulators/wine?
from Michael Holmes holmesm...@gmail.com: HAL shouldn't be necessary, but you might need to manually set up CUPS. Winemaker is just a tool for building open-source Windows apps on Wine with ease. There are a few GUI tools to set up CUPS, but if I recall correctly, the web interface to CUPS is pretty self-explanatory. HP do have a nice GUI called HPLIP for utilising their printers on Linux (and ported to FreeBSD) available on ports as print/hplip, but it doesn't work with the GENERIC console config, and seems to be quite awkward to set up (you apparently cannot load USB mass storage until the printer is 'adopted' by the generic USB stack). I don't know what you mean by adopted (by the generic USB stack): seems mystic to me. CUPS would be necessary to setup printing for BSD and Linux, but would it be necessary when using Wine and going the MS-Windows way? Package message said that ulpt had to be turned off in kernel config and not loaded as a module. On the older computer, I tried unsuccessfully to setup the printer last June 29 from both NetBSD and FreeBSD, using hplip in both cases. Predominant message was No devices found. NetBSD pkgsrc had only an outdated hpijs, but pkgsrc-wip (http://pkgsrc-wip.sourceforge.net/) had hplip. Message said also to disable umass, but that was too harsh, and prevented recognizing USB sticks. Would Linux offer a better chance with hplip than BSD? I tried also with Linux (Slackware 13.0), but hplip version was behind, and that failed. There is also the Ethernet option with the printer, but I need an Ethernet switch or additional router for that, which I intend to order. First attempt to build hplip on the new computer failed due to libieee1284 dependency being for i386 only. Subsequently I turned off that option after finding it was for parallel-port scanners only, not USB. Tom ___ 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: Current unassigned ports problem reports
Is the cups-base problem on the assigned list, being incompatible with the optional avahi (DNSSD)? The BROKEN message references http://www.avahi.org/ticket/303 -- look there for more information on why it's marked as such. Tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Options for emulators/wine?
from Chris Rees cr...@freebsd.org: Some rather strange printers will be recognised by umass before ugen recognises them; you have to plug it in before umass is loaded or it becomes a mass storage device. I'm not sure that the Windows printer stack is included in Wine, why would you rather do that than use CUPS? The gutenprint drivers are often of a higher quality than the manufacturer's provided ones, and they install less trash. I need umass, otherwise USB sticks and other USB disks are inaccessible. Should the printer be plugged in and powered on at boot time? I am already trying unsuccessfully to build hplip to access the printer in the Unix way, without wine. With wine, I might want to try another way, using MS-Windows drivers if possible. Building hplip failed due to a broken dependency, py-reportlab2 BROKEN= does not package (quoting from the Makefile) Tom ___ 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
environment variables for portupgrade: /etc/make.conf or /usr/local/etc/pkgtools.conf?
How do I make environment variables used by portupgrade visible to portupgrade? Portupgrade evidently ignores /etc/make.conf, and editing /usr/local/etc/pkgtools.conf also fails to help. I want portupgrade to recognize PORTSDIR=/BETA1/usr/ports and PACKAGES=/usr/packages but continue to get cd: /usr/ports: No such file or directory cd: /usr/ports/ports-mgmt/portupgrade: No such file or directory when it should be looking for /BETA1/usr/ports I was in directory /BETA1/usr/ports/print/py-reportlab2 ; offending command was portupgrade -o py-reportlab2 py-reportlab | tee portupg.log I think that should have been portupgrade -o print/py-reportlab2 print/py-reportlab | tee portupg.log That failed because print/py-reportlab had already been built and installed, so I had to pkg_delete it, then build py-reportlab2 without portupgrade. Problem arose because py-reportlab2, a dependency of print/hplip, was broken (did not package), and I subsequently built and installed py-reportlab . after a later portsnap fetch update, I decided to go back to print/py-reportlab2 . But I still want to know where portupgrade gets environment variables: /etc/make.conf, /usr/local/etc/pkgtools.conf (in Ruby?), or other. Tom ___ 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
More trouble with wine: won't build for amd64
Now I find I can't build emulators/wine on my new computer because wine is for i386 only. Any way I can get an i386 compatibility mode? I could try, perhaps when FreeBSD 9.0 is released, installing and building ports on a 16 GB USB stick to run on the older computer (i386), but capable also of running on the new computer. Then I could hopefully build wine. Ports tree and work directories would be on the new computer hard drive rather than the USB stick. I think wine can be built for either i386 or amd64 in Linux. Tom ___ 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: environment variables for portupgrade: /etc/make.conf or /usr/local/etc/pkgtools.conf?
But I still want to know where portupgrade gets environment variables: /etc/make.conf, /usr/local/etc/pkgtools.conf (in Ruby?), or other. Tom Set them in your shell's environment: export PORTSDIR=/BETA1/usr/ports export PACKAGES=/usr/packages -- Conrad J. Sabatier conr...@cox.net Do I have to do this for every portupgrade command, or can I put these environment variable settings in a file, like /etc/make.conf or /usr/local/etc/pkgtools.conf ? I left /usr/local/etc/pkgtools.conf in the modified state, modified lines being ENV['PORTSDIR'] = '/BETA1/usr/ports' ENV['PACKAGES'] = '/usr/packages' # ENV['PORTSDIR'] ||= '/usr/ports' # ENV['PACKAGES'] ||= ENV['PORTSDIR'] + '/packages' I suppose I could do a portupgrade with -n flag to see if my setup looks workable? Tom ___ 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: More trouble with wine: won't build for amd64
From arrowdodger 6year...@gmail.com: These links may be helpful for you: http://wiki.freebsd.org/Wine http://www.mediafire.com/wine_fbsd64 Thanks for suggestions. It looks like I essentially have to do a full installation of FreeBSD, now 9.0-BETA3, into /compat/i386 . I was planning to install FreeBSD 9.0 i386 onto a 16 GB USB stick to be able to run on the older computer; build ports using the new computer hard drive. Then I wouldn't have to install the ports tree redundantly on the USB stick. I would boot USB stick on the old computer using Plop (http://www.plop.at/). The USB-stick installation ought to boot on the new computer, or I could mount its root directory to /compat/i386. Building ports on a USB stick on the old computer would be prohibitively slow: 256 MB RAM, USB 1.1 on motherboard. I don't really want to freebsd-update my FreeBSD 8.2 installation on the old computer for fear of running out of disk space; also portupgrading everything would be too cumbersome even on the hard drive, and then 256 MB RAM might not be enough. Tom ___ 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
Swfdec and gnash for playing Adobe Flash?
I built and installed both graphics/swfdec and swfdec-gnome, and graphics/gnash, and would like to know how to use swfdec to play some Flash content. Some Flash videos run with gnash, including those on YouTube, but others just show a blank rectangle. I wonder if swfdec-gnome can play anything that gnash can't, also see that swfdec-mozilla is not in ports. I also get a blank rectangle on Flash content that is not a video, such as on meijer.shoplocal.com ads and freefilefillableforms.com . I don't see why those sites use Flash, it seems like an unnecessary and useless annoyance. Tom ___ 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
devel/cross-gcc and cross-binutils: how to set TGTARCH and TGTABI
From $PORTSDIR/devel/cross-binutils: GNU binutils for cross-target application development. Prerequisite for the GCC cross-compiling environment. Use TGTARCH switch to select target architecture, and TGTABI to select ABI. E.g. the following command will build binutils for rtems on sparc: % make TGTARCH=sparc TGTABI=rtems If you encounter any problems building/using/installing this port, please make me know. It would help to improve this port in feature. -- Stanislav Sedov s...@freebsd.org My question is how to set TGTARCH and TGTABI, that is not documented; I looked at the web sites. Would TGTARCH be i386 or amd64, if I want to build for those platforms? What about TGTABI? I don't know the proper code words, would want to compile for Linux and possibly NetBSD. Maybe I need to make fetch followed by make extract and look inside? Tom ___ 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]: ports feature freeze starts soon
from Erwin Lansing er...@freebsd.org: In preparation for 9.0 the ports tree will be in feature freeze after release candidate 1 (RC2)is released, currently planned for October 17. Was there a typo here? Did you mean release candidate 1 or 2? RC1 seems more logical, since RC1 has not been released yet, and October 17 is only nine days away. Tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: devel/cross-gcc and cross-binutils: how to set TGTARCH and TGTABI
You cannot use this port to build toolchaing for compiling Linux and NetBSD applications. This port creates toolchain using the newlib libc library, which is used by some embedded operating systems (e.g. rtems, ecos). It can also be used to build bare-metal standalone applications. Linux on the other hand is using glibc and NetBSD their own libc implementation, so this toolchain would not work. Stanislav Sedov Thanks for clarification. What you say was not obvious from the pkg-descr. Now I will know one blind alley to avoid in cross-compiling for Linux and NetBSD. Tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: devel/cross-gcc and cross-binutils: how to set TGTARCH and TGTABI
What is your target? Do you just want to cross-build the Linux and NetBSD kernels, or userland applications? For Linux we can probably try to add a port that uses glibc instead of newlib. Stanislav Sedov In the case of NetBSD, I would want to build the kernel and base system not including X. Then I would install pkgsrc and build Xorg from that. There is a NetBSD Guide online that tells how to do those things, question being whether it would work from FreeBSD. Getting a productive NetBSD system on my hardware is already a long shot, no USB 3.0 support among other things. For Linux, I would want to build kernel plus tools to get to a bootable minimal system, then go from there Linux-native. I would want a package manager such as pacman or Conary for Linux rather than build packages one at a time and have to keep track of dependencies. Tom ___ 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: Problem with package-recursive target
Even when I have a clean ports tree (I mean no work under any port) make package-recursive always make some garbage like this : rmdir: /usr/ports/textproc/raptor/work: Directory not empty *** Error code 1 (ignored) rmdir: /usr/ports/textproc/rasqal/work: Directory not empty *** Error code 1 (ignored) [... snipped for a lot of ports ...] That does not appears all the time but in my case it appeared when doing make package-recursive in www/firefox and editors/libreoffice. It is a little bit annoying. Do you have any clue? Cheers, -- David Demelier I have the same problem, thought it might be something with 9.0-BETA1 and 2, mentioned it on freebsd-current list, but no responses there. Nothing is disrupted, I run 'make clean' afterward, but it is unaesthetic, and scary at first in that an error message usually indicates something went awry. Tom ___ 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: which ports require dialog during update
from kron24 kro...@gmail.com: OP may want to look on 'make config-recursive'. Sometimes, perhaps when selecting options results in subsequent dialogs, 'make config-recursive' doesn't do all the first time, meaning I get subsequent dialogs. I run 'make config-recursive' repeatedly until it just returns to the command prompt with no more dialogs. I like to make package-recursive | tee build.log so as to have a record especially if not all goes well; this applies equally for 'make install clean' I like to have all config dialogs done and out of the way. Tom ___ 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
fldiff fails to start after updating fltk to 1.3.0
After upgrading x11-toolkits/fltk from 1.1.10_1 to 1.3.0 textproc/fldiff fails to start: $ fldiff Shared object libfltk_images.so.1.1 not found, required by fldiff A rebuild of textproc/fldiff fixes that problem. Perhaps ports depending on fltk should have their revision bumped or an appropriate note on how to upgrade fltk should be added to UPDATING. -- Thomas Mueller ___ 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: seamonkey w.o. MAILNEWS
when configuring w.o. MAILNEWS it fails to patch... Regards Christian Jachmann If you don't want MAILNEWS, maybe you should build firefox instead of seamonkey? Tom ___ 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
Linux compatibility with more than one Linux installed?
I noticed on http://www.freshports.org/commits.php an update to the Gentoo Linux distribution. I know there are other Linux compatibility ports in the emulators category. Is it possible to install more than one Linux compatibility package or actual Linux installation and switch from one to the other? I might want to install a Linux compatibility package and still be able to run Linux software through an actual Linux installation, separate from the FreeBSD Linux compatibility package. Or possibly be able to compare one Linux compatibility package to another. Tom ___ 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?
The linux-base port is supposed to provide good integration into FreeBSD. Ideally the integration is seamless. The linux-dist ports provide a complete linux environment. You chroot into it and you have a complete linux system. You can compile linux binaries inside the +linux-dist. You can not do this with the linux-base. Bye, Alexander. So I guess that's the fundamental difference between linux-base installed to /compat/linux, and linux-dist? So when I build my Linux installation, then I suppose I can mount that partition and chroot into it? Even as nonroot? Even run X Window applications? I think on some platforms, chroot is root-only, but running ls -l /usr/sbin/chroot in FreeBSD 9.0-RC2 -r-xr-xr-x 1 root wheel 7736 Nov 22 11:08 /usr/sbin/chroot Tom ___ 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 Thu, 1 Dec 2011 11:06:19 + (GMT) Thomas Mueller mueller6...@bellsouth.net wrote: The linux-base port is supposed to provide good integration into FreeBSD. Ideally the integration is seamless. The linux-dist ports provide a complete linux environment. You chroot into it and you have a complete linux system. You can compile linux binaries inside the +linux-dist. You can not do this with the linux-base. So I guess that's the fundamental difference between linux-base installed to /compat/linux, and linux-dist? So when I build my Linux installation, then I suppose I can mount that partition and chroot into it? Yes, you just have to mount some FS into the linux-env (devfs, linprocfs, linsysfs, just like with the linux-base). This assumes your linux env does not use some linux syscalls which the linuxulator part in the FreeBSD kernel does not understand. It also assumes you have a similar setup for important things like DNS servers and such. Even as nonroot? Even run X Window applications? If you have the same UIDs/GIDs in the linux env (for users), it should work. Even with X (you can do a hardlink of the X socket in the FS into the linux env, or you accept a little bit more overhead and go via TCP - DISPLAY=hostname:0.0). I don't think I really understand this part. I think on some platforms, chroot is root-only, but running ls -l /usr/sbin/chroot in FreeBSD 9.0-RC2 -r-xr-xr-x 1 root wheel 7736 Nov 22 11:08 /usr/sbin/chroot Chroot should only depend on FS access rights. Bye, Alexander. So I guess it's possible at least in theory to run Linux by chroot from FreeBSD, but there are stumbling blocks. One would be limited as to Linux file system, it might not work with ext4 or btrfs. Also, I'd be running with one of the newer Linux kernels, meaning possibly ahead of FreeBSD's linuxulator. I noticed FreeBSD's Linux emulation was some versions behind current Linux. Tom ___ 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?
The X server has a unix socket somewhere in /tmp. Normally this is used instead of a TCP connection to the localhost. You need to change the DISPLAY env-variable to use a TCP connection, or you need o make the unix socket available to the chrooted linux-env. The linuxulator in FreeBSD is nearly linux 2.6.16 compatible. We lack inotify and epoll support which the 2.6.16 kernel normally supports. If your system does not depend upon inotify, epoll and anything newer than 2.6.16, it should work. If you give it a try, please report success or failure to emulat...@freebsd.org. Bye, Alexander. Now I might have something to try, but it is very unlikely that I would build a Linux kernel = 2.6.16, especially with new hardware that might need the latest drivers. I will primarily want to run Linux natively rather than under FreeBSD. I think emulators/linux_dist-gentoo-stage3 and emulators/linux_base-gentoo-stage3 must use kernel far beyond 2.6.16. But I think, when chrooting into Linux from FreeBSD, FreeBSD kernel is the one in effect. Tom ___ 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?
Too much to quote here without making a mess, and I want to get to bed, but thanks for all the ideas. I noticed the advice with emulators/wine that running programs on an actual MS-Windows partition can make a mess of said partition; wonder if there would be such a hazard with Linux instead of MS-Windows. But it was safe to run programs on a DOS partition when I had OS/2 Warp 3 and 4, which could run many DOS programs even without using an actual DOS installed. OS/2 Warp 4 could also boot a specific version of DOS, but there were still limitations on what DOS programs could do when running under OS/2. Tom ___ 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, 7 Dec 2011 11:56:49 + (GMT) Thomas Mueller mueller6...@bellsouth.net wrote: Too much to quote here without making a mess, and I want to get to bed, but thanks for all the ideas. I noticed the advice with emulators/wine that running programs on an actual MS-Windows partition can make a mess of said partition; wonder if there would be such a hazard with Linux instead of MS-Windows. It depends. I can not comment upon the quality of the ext2fs part of FreeBSD, but the linuxulator itself will not destroy anything. Theoretically it can be the case that a sloppy programmed (linux-)tool may destroy some data if it wants to use something which does not work, but in this case I would say it is the fault of the tool to not check for errors... Or let's say it differently: if it destroys something, you should have played Lotto instead of doing whatever you did... ;-) Bye, Alexander. -- http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7 So I guess it's worth a try after I get my Linux built and installed, am busy now with FreeBSD 9.0-RC3. Also, I want to see if I can cross-build NetBSD from FreeBSD, partly as a dress rehearsal for building Linux, partly to see how and if cdrtools/cdrecord works in NetBSD compared to FreeBSD. So it looks like the linuxulator does not have the hazards associated with MS-Windows and wine. Tom ___ 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: lang/gcc46
--- On Mon, 12/12/11, Kevin Oberman kob6...@gmail.com wrote: Hi Gerald, As a request once again similiar to one I have made in the past... Would it be possible yet to slow down the update process for the gcc46 port ? This is turning out to be quite the pain in the U-Know-What with version flapping and rebuilding because a port depends on it. If I am correct it is updated weekly. I caught the tail end of the previous update and the day after it was bumped to the next snapshot version by the time both of those were finished the port had once again been bumped to _1. Is there anything that could be done to stabalize this ... ? At this point I am left for the manual intervention of using +IGNOREME files or excluding by whatever means neccesary as weekly updates seem completely unneccesary now that alot of ports are shifting to depend on gcc46. Can a gcc46-devel port be branched for those that absolutely need the weekly updates ? +1 gcc46 is used by so many ports that I am continually re-building it and on slow machines, this takes a while. How about a gcc46-devel port that gets the regular updates and let gcc46 stay stable when there are not major fixes? - R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com Now I see I accidentally sent my reply only to Kevin Oberman and not the list. Composing a message with vi editor is easier than webmail! I have to recompose this message since I failed to save. I wondered why the ports collection used development snapshots of gcc rather than stable releases. On my older computer, dating to 2001, with 256 MB RAM, building ports and portupgrades that depended on gcc-4.5.3 snapshot would bog down after about four hours due to exhausting virtual memory. It seems to make more sense to use stable gcc releases when needed as build dependencies, and keep the current weekly snapshots for testing and development purposes. Tom ___ 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
Can't get hplip to work on HP LaserJet 1212nf MFP
I built hplip from the ports on both the old and new computer, FreeBSD 8.2 i386 and 9.0 amd64 respectively, and can't get either of them to work, either on USB or Ethernet. I commented out device ulpt in the kernel config file, but got No devices found in the USB setup, even though the printer was recognized by system messages and usbconfig. When I connected the printer on the new computer via USB, ulpt.ko automatically loaded (how to prevent that?), but I got the same No devices found even when ulpt.ko was renamed to ulpt2.ko so it would not be found and loaded (a kludge). The printer was found when connected by Ethernet, but the binary plugin installation failed consistently, some complaint of /etc/issue or hp-plugin-install not found. By way of comparison, I also built hplip3 from pkgsrc in NetBSD 5.1_STABLE amd64; this was actually pkgsrc-wip (http://pkgsrc-wip.sourceforge.net). That was version 3.11.1. I got No devices found both with USB and Ethernet; could still try again with Ethernet, getting the printer IP address from either dmesg.boot or logging in to wireless router, though this is a slender chance. hplip versions for FreeBSD are 3.11.1 on the old computer and 3.11.5 on the new computer. I do intend to update my 9.0-STABLE installation on the new computer and then portupgrade or portmaster this and other ports, but fear more of the same frustration. Would I need to exclude ulpt module as well as kernel config device ulpt line, or can ulpt.ko be prevented from automatically loading, or would that make no difference? Are HP printers especially recalcitrant to setting up, or especially USB-quirky, as opposed to other brands such as Lexmark, Samsung, Brother, Xerox and Canon? Other things I intend to try are with Wine; I also intend to try on Linux, possibly on NetBSD if I can get that to install and run on the new computer. Linux is home base for hplip and much or most other open-source (quasi-)Unix software. Tom ___ 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: Can't get hplip to work on HP LaserJet 1212nf MFP
from Edwin L. Culp W. edwinlc...@gmail.com: I have the exact same model sitting here with me and have been trying to get it to work again. I can't really understand why it doesn't. It did work for me perfectly for a couple of months and then my computer's motherboard died and after the change, I haven't been able to get it to work again. It finds its IP through dhcp and but I can't get it to react. My previous email to the list is at: http://lists.freebsd.org/pipermail/freebsd-questions/2012-April/240116.html We should be able to get it going. I haven't looked at it for a couple of weeks (Just long enough to have forgotten what I have done) so I'll try again from zero and let you know if I have any luck. ed I rebuilt everything and still can't get it to work. I even tried USB for configuration and it says that HP LaserJet Professional m1212nf MFP, hpcups 3.12.2, requires proprietary plugin so I'm going back to IP and try again from scratch. Thanks for your effort. So you managed to get the printer recognized by hp-setup with USB, but it couldn't download and/or install the proprietary plugin? I've read recent reviews of various printer brands in PC World, and HP and Lexmark got low ratings for reliability. Now I have a strong aversion to buying anything in the future of HP brand, except toner if I can get the printer to work. Their tech support was offshored to India, and they had a difficult time communicating in English. Also, their free tech support, either by phone or email, is only for one year, while Lexmark allowed five years. Some things I can try include: Building new version of the port for both amd64 and i386; I will want to build i386 distribution from source to install on a USB stick both for wine and for the old computer. Old computer can't boot directly from USB but can with Plop Boot Manager (http://www.plop.at/). I could also try the MS-Windows software with wine. NetBSD with pkgsrc-wip; also retry the old build with Ethernet, but getting IP address from wireless router if not from dmesg.boot . Linux with a package manager like pacman or conary. OpenIndiana: I saw a reference to hplip, so worth a try with USB sticks even if OpenIndiana can't access my hard drive due to GPT. I actually downloaded and wrote the image to a USB stick. Tom ___ 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: Can't get hplip to work on HP LaserJet 1212nf MFP
from Edwin L. Culp W. edwinlc...@gmail.com: I have the exact same model sitting here with me and have been trying to get it to work again. I can't really understand why it doesn't. It did work for me perfectly for a couple of months and then my computer's motherboard died and after the change, I haven't been able to get it to work again. It finds its IP through dhcp and but I can't get it to react. My previous email to the list is at: http://lists.freebsd.org/pipermail/freebsd-questions/2012-April/240116.html We should be able to get it going. I haven't looked at it for a couple of weeks (Just long enough to have forgotten what I have done) so I'll try again from zero and let you know if I have any luck. ed I rebuilt everything and still can't get it to work. I even tried USB for configuration and it says that HP LaserJet Professional m1212nf MFP, hpcups 3.12.2, requires proprietary plugin so I'm going back to IP and try again from scratch. Thanks for your effort. So you managed to get the printer recognized by hp-setup with USB, but it couldn't download and/or install the proprietary plugin? I've read recent reviews of various printer brands in PC World, and HP and Lexmark got low ratings for reliability. Now I have a strong aversion to buying anything in the future of HP brand, except toner if I can get the printer to work. Their tech support was offshored to India, and they had a difficult time communicating in English. Also, their free tech support, either by phone or email, is only for one year, while Lexmark allowed five years. Some things I can try include: Building new version of the port for both amd64 and i386; I will want to build i386 distribution from source to install on a USB stick both for wine and for the old computer. Old computer can't boot directly from USB but can with Plop Boot Manager (http://www.plop.at/). I could also try the MS-Windows software with wine. NetBSD with pkgsrc-wip; also retry the old build with Ethernet, but getting IP address from wireless router if not from dmesg.boot . Linux with a package manager like pacman or conary. OpenIndiana: I saw a reference to hplip, so worth a try with USB sticks even if OpenIndiana can't access my hard drive due to GPT. I actually downloaded and wrote the image to a USB stick. Tom ___ 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: Can't get hplip to work on HP LaserJet 1212nf MFP: accidently resent message
from Edwin L. Culp W. edwinlc...@gmail.com: I have the exact same model sitting here with me and have been trying to get it to work again. I can't really understand why it doesn't. It did work for me perfectly for a couple of months and then my computer's I accidently resent a message in this thread that I already sent a day ago. Sorry for duplicate message! Tom ___ 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: Build ports in chroot for i386 when booted with amd64 kernel?
From Alexander V. Ribchansky trios...@triosoft.com.ua: May be /usr/ports/ports-mgmt/poudriere + /usr/ports/ports-mgmt/pkg is what you really need? I took a look at the descriptions for these packages, but don't really think I would need these. Ports would be built to run on the i386 chroot or system. On 5/24/12 6:47 AM, Thomas Mueller wrote: Is it feasible to chroot into an i386 environment when booted to FreeBSD amd64 for the purpose of building and installing ports for i386? this is basically what tinderbox does. Michael Scheidell, CTO I am only vaguely familiar with tinderbox as such, would likely be guided by the model at http://wiki.freebsd.org/Wine From Doug Barton do...@freebsd.org: You need a proper jail with an i386 system installed, not just a chroot. The intent was to build and install a full i386 base system, since I would want to run it on an i386 computer as well as in a chroot on amd64. I think it is possible to cross-build a FreeBSD system, userland and kernel, but this might not apply for ports in general on all FreeBSD-supported architectures. Yes. I have built i386 code (both world ports) using both chroot and jail. The only caveat is that the i386 world should be no newer than the host kernel. Assuming /tank/m3 has an i386 world installed: On the host: # mount -r -t nullfs /usr/src /tank/m3/usr/src # mount -r -t nullfs /usr/ports /tank/m3/usr/ports # mount -t devfs devfs /tank/m3/dev # chroot /tank/m3 bin/sh Inside the chroot: # export MACHINE=i386 UNAME_p=i386 UNAME_m=i386 # cd /usr/src make buildworld # cd /usr/ports/.../... make install etc So far, I've only had this fail when building MPIR (which isn't a port and seems to have broken CPU detection code). Peter Jeremy I would likely use the same source tree that I used for the latest system update, FreeBSD 9.0-STABLE #9. Tom ___ 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: Build ports in chroot for i386 when booted with amd64 kernel?
On 5/24/2012 6:47 AM, Alexander V. Ribchansky wrote: Hello! May be /usr/ports/ports-mgmt/poudriere + /usr/ports/ports-mgmt/pkg is what you really need? Yes you can run a 32bit jail on a 64bit machine. Poudriere works really well for building packages like this. Regards, Bryan Drewery I overlooked your message when I sent a post in this thread several minutes ago. Now I might give ports-mgmt/poudriere another, closer look. I remember getting bogged down on the older computer on some of the heavier ports, due to shortage of RAM (256 MB) and disk space. Tom ___ 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
How to start wine?
I built wine from ports on a USB-stick installation of FreeBSD 9.1-STABLE i386, but it won't start. I tried to start from hard-drive installation of (from uname -a) FreeBSD amelia2 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #17 r254196: Sun Aug 11 00:36:49 UTC 2013 root@amelia2:/usr/obj/usr/src/sys/SANDY amd64 I get Shared object libwine.so.1 not found, required by wine I was able to find libwine.so and libwine.so.1 in directory /usr/local/lib, or as it is mounted, /compat/i386/usr/local/lib I tried as nonroot user. Kernel config includes the line options COMPAT_FREEBSD32# Compatible with i386 binaries What is the trick? Should I try to boot the USB stick with FreeBSD 9.1-STABLE i386? I did not build Xorg on this USB stick. Should I have? What is the requirement of FreeBSD versions matching? Although I keep the source tree, ports tree and work directories on the hard drive, installing to this Kingston Data Traveler 16 GB USB 2.0 stick is very slow, slower than NetBSD and slower than FreeBSD on other USB sticks. I could try with a Kingston Data Traveler 16 GB or 32 GB USB 3.0 drive. Tom ___ 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 start wine?
from dgmm: You can't do that See https://wiki.freebsd.org/i386-Wine For a workaround, see https://people.freebsd.org/~ivoras/wine/ I saw https://wiki.freebsd.org/i386-Wine Other page seems outdated. Can't do what? I built i386 Wine from i386. But it won't run without X. I could build an i386 installation to install on Kingston Data Traveler 16 GB or 32 GB USB 3.0, or install to a partition on a USB 3.0 hard drive. That USB 3.0 hard drive is not bootable, so I would have to put a boot image (giant floppy?) where I could boot from GRUB and mount root on the USB 3.0 hard drive partition. Problem with USB stick installation is frequent updates. So if I want installation to be portable, I might install to USB 3.0 hard drive partition. I have installed NetBSD (5-STABLE, 6-STABLE and HEAD, both i386 and amd64) to USB 2.0 sticks, and modular Xorg from pkgsrc too. NetBSD source trees, pkgsrc tree and work directories are on SATA hard drive. NetBSD is rather unstable on my hardware. Tom ___ 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 start wine?
What are LD_LIBRARY_PATH and LD_32_LIBRARY_PATH supposed to be? I see neither of these environment variables defined. I tried to add /compat/i386... binary directories to the path, but that was insufficient. I see /lib /libexec /usr/lib /usr/lib32 /usr/libdata /usr/libexec /usr/local/lib /usr/local/libdata /usr/local/libexec with the FreeBSD i386 installation not mounted. I have seen LD_LIBRARY_PATH before from building packages from source. I thought maybe wineboot would set up the environment, but it looks like I have to set up the environment beforehand. What is the difference between the various wine ports in $PORTSDIR/emulators? I used wine-devel, newer but less tested than wine. Upstream latest release is 1.6 as far as I can see. Building X for FreeBSD i386 before wine would be necessary for running from i386 boot even if not runnable from amd64. My i386 version was/is somewhat behind amd64 version. Tom ___ 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 start wine?
What are LD_LIBRARY_PATH and LD_32_LIBRARY_PATH supposed to be? I see neither of these environment variables defined. And what about PATH? I am trying #!/bin/sh set PATH=/compat/i386/usr/local/bin:/compat/i386/usr/local/sbin:/compat/i386/usr/bin:/compat/i386/usr/sbin:/compat/i386/bin:/compat/i386/sbin:$PATH export LD_32_LIBRARY_PATH=/compat/i386/usr/local/lib:/compat/i386/usr/lib:/compat/i386/lib:$LD_32_LIBRARY_PATH export LD_LIBRARY_PATH=/compat/i386/usr/local/lib:/compat/i386/usr/lib:/compat/i386/lib:$LD_LIBRARY_PATH but I feel like I'm just thrashing here, will run into trouble trying to execute 32-bit binaries when not appropriate. I see /lib /libexec /usr/lib /usr/lib32 /usr/libdata /usr/libexec /usr/local/lib /usr/local/libdata /usr/local/libexec and then there are some subdirectories of these directories with the FreeBSD i386 installation not mounted. I have seen LD_LIBRARY_PATH before from building packages from source. I thought maybe wineboot would set up the environment, but it looks like I have to set up the environment beforehand. What is the difference between the various wine ports in $PORTSDIR/emulators? I used wine-devel, newer but less tested than wine. Upstream latest release is 1.6 as far as I can see. Building X for FreeBSD i386 before wine would be necessary for running from i386 boot even if not runnable from amd64. My i386 version was/is somewhat behind amd64 version. Tom ___ 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 start wine?
The bootstrap code from i386-wine does the following: if [ -z $__BINBOUNCE_BOOTSTRAP ] then export LIBGL_DRIVERS_PATH=$LOCALBASE/lib32/dri if [ `uname -p` = i386 ] then export LD_LIBRARY_PATH=$LOCALBASE/lib32:$LOCALBASE/lib32/wine:$LD_LIBRARY_PATH else export LD_32_LIBRARY_PATH=$LOCALBASE/lib32:$LOCALBASE/lib32/wine:$LD_32_LIBRARY_PATH:/usr/lib32 fi export PATH=$LOCALBASE/bin32:$PATH fi I see no /usr/local/lib32 directories; just /usr/lib32, and much bigger for amd64 than for i386. I see /compat/i386/usr/local/lib/wine so I guess that needs to be included in LD_32_LIBRARY_PATH? The only lib directory dri was in /usr/local/lib/dri and only for amd64 because I didn't build X for i386 (not yet). So now my winepath.sh is (to be run before any wine binaries, and avoiding nonexistent directories) #!/bin/sh export LIBGL_DRIVERS_PATH=/usr/local/lib/dri export PATH=/compat/i386/usr/local/bin:$PATH export LD_32_LIBRARY_PATH=/compat/i386/usr/local/lib:/compat/i386/usr/local/lib/wine:/compat/i386/usr/lib32:$LD_32_LIBRARY_PATH:/usr/lib32 # export LD_LIBRARY_PATH=/compat/i386/usr/local/lib:/compat/i386/usr/lib:/compat/i386/lib:$LD_LIBRARY_PATH Is it necessary to set environment variables like this when running wine on i386? I'd like to try from both amd64 and i386. Tom ___ 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: distfiles changed to new path
from Fbsd8: I just did a portsnap run that updated the base port system. Now I see a port's distfile going to /var/ports/distfiles instead of /usr/ports/distfiles. Is this a error in the newly updated base port system which contains the default port make environment? I have no directory /var/ports nor /BETA1/var/ports. My PORTSDIR is /BETA1/usr/ports because I kept this location from FreeBSD 9.0-BETA1 after installing BETA2 in another GPT partition. My distfiles directory is ?BETA1/usr/ports/distfiles . But a portsnap run should not download distfiles. Distfiles are downloaded when you build a port. Tom ___ 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
What is MAKE_JOBS_UNSAFE?
In some ports that failto build/upgrade, with portmaster in this case, I get a message like gmake[1]: Leaving directory `/BETA1/usr/ports/multimedia/vlc/work9amd64/vlc-2.0.7' gmake: *** [all] Error 2 === Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** [do-build] Error code 1 I also got this with mplayer and graphics/gstreamer-plugins-gl, resulting from the instructions in UPDATING 20130731. I looked in man pages (portmaster, ports, make.conf, make) and online Porters' Handbook without finding anything. So I want to know what MAKE_JOBS_UNSAFE=yes is supposed to do, and do I set it by env MAKE_JOBS_UNSAFE=yes portmaster multimedia/vlc (or whatever other port it applies to)? Tom ___ 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: What is MAKE_JOBS_UNSAFE?
Thomas, It prevents parallel (make -j 4) build of ports, and your assumption about how to set it is correct; alternatively, it can be given on the make command line: portmaster -mMAKE_JOBS_UNSAFE=yes multimedia/vlc. URL: http://www.freebsd.org/doc/en/books/porters-handbook/building.html It's described in Section 6.3.1 Building Ports in Parallel of the porter's handbook, and apparently a bit out of date, because MAKE_JOBS_SAFE=yes is now the default, and this feature must explicitly be _disabled_. Can someone from among the doc committers team please reflect the new default in the Porter's Handbook? (I was looking at r42618.) HTH Matthias If MAKE_JOBS_UNSAFE=yes is already the default, then presumably trying to build or upgrade a port will fail just the same with this part specified? Now pkg info -r gio-fam-backend shows gio-fam-backend-2.34.3: mplayer-1.1.r20130308 gstreamer-plugins-gl-0.10.3_1 vlc-2.0.6_3,3 So to go to the last step (portmaster -a) in this UPDATING 20130731, I have to somehow upgrade or get rid of those three reverse dependencies, or possibly pkg delete -f gio-fam-backend I see in other posts that vlc has had a further update/commit, and I could switch from mplayer to mplayer2, but what about gstreamer-plugins-gl, or is this not critical? Tom ___ 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: What is MAKE_JOBS_UNSAFE?
Thomas, It prevents parallel (make -j 4) build of ports, and your assumption about how to set it is correct; alternatively, it can be given on the make command line: portmaster -mMAKE_JOBS_UNSAFE=yes multimedia/vlc. URL: http://www.freebsd.org/doc/en/books/porters-handbook/building.html It's described in Section 6.3.1 Building Ports in Parallel of the porter's handbook, and apparently a bit out of date, because MAKE_JOBS_SAFE=yes is now the default, and this feature must explicitly be _disabled_. Can someone from among the doc committers team please reflect the new default in the Porter's Handbook? (I was looking at r42618.) HTH Matthias If MAKE_JOBS_UNSAFE=yes is already the default, then presumably trying to build or upgrade a port will fail just the same with this part specified? Now pkg info -r gio-fam-backend shows gio-fam-backend-2.34.3: mplayer-1.1.r20130308 gstreamer-plugins-gl-0.10.3_1 vlc-2.0.6_3,3 So to go to the last step (portmaster -a) in this UPDATING 20130731, I have to somehow upgrade or get rid of those three reverse dependencies, or possibly pkg delete -f gio-fam-backend I see in other posts that vlc has had a further update/commit, and I could switch from mplayer to mplayer2, but what about gstreamer-plugins-gl, or is this not critical? Update: I did portmaster -o multimedia/mplayer2 multimedia/mplayer successfully, but failed with vlc and gstreamer-plugins-gl. Can I safely pkg delete -f gio-fam-backend since its function is (?) presumably filled by glib 2.36 ? Tom ___ 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: What is MAKE_JOBS_UNSAFE?
Can I safely pkg delete -f gio-fam-backend since its function is (?) presumably filled by glib 2.36 ? Yes, providing that you've rebuilt all ports that did previously require gio-fam-backend. I had three that failed, and MAKE_JOBS_UNSAFE=yes apparently had no effect: multimedia/mplayer, graphics/gstreamer-plugins-gl, multimedia/vlc I successfully upgraded mplayer to mplayer2. I tried make deinstall install on graphics/gstreamer-plugins-gl: deinstalled but was unable to rebuild and reinstall. multimedia/vlc failed even with MAKE_JOBS_UNSAFE=yes. My guess is that pkg delete -f gio-fam-backend would not adversely affect vlc 2.0.6_3,3 because glib 2.36 might serve the function of gio-fam-backend. Anyway, I don't want to let this stop me from the last step (portmaster -a). I will want to source-upgrade to the upcoming FreeBSD 9.2-RELEASE, and build sysutils/grub2, see if I can create my own Super Grub2 Disk. Even if vlc is messed up, I can hope to rebuild in the near future. Tom ___ 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: What is MAKE_JOBS_UNSAFE?
In most cases MAKE_JOBS_UNSAFE=yes will not help. The message is an artifact from when the defaults were reversed and a precaution for the days after it was changed. IMHO it should be removed now. Eitan Adler I'm inclined to agree with you. I guess my best choice on what to do about gio-fam-backend and multimedia/vlc is pkg delete vlc pkg delete gio-fam-backend or pkg delete -f gio-fam-backend and let multimedia/vlc sink or swim for the time being, so I can go to the next step portmaster -a -x multimedia/vlc and then do multimedia/vlc later. I think multimedia/vlc gets fairly frequent updates, so I won't have to wait too long. It is possible that vlc functionality won't be impaired by having gio-fam-backend taken out from under. I have to remember FreeBSD 9.2-RELEASE may be in the very near future. Tom ___ 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: SVN RELEASE_9_2_0
# Is FreeBSD doing something new? I don't see an SVN tag for ports for # the 9.2 release. Historically the ports tree was tagged and built a # little before -stable got tagged for release. # Thanks, # Jason Ports don't belong to a specific FreeBSD version. It's the built packages that are prepared shortly before release. For the ports and doc trees, you would go for head (current). Tom ___ 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 apps replacements?
from Per olof Ljungmark: I am finally in the process of removing KDE3 completely, switched to Xfce some time ago, and wonder if any of you could recommend suitable replacements for some of the apps: kpdfpdf viewer with the ability to copy text from kWrite simple text editor with some filetype and highlighting features + easy to switch encoding (vim/gvim?) kPatience Card game, Freecell in particular kColorChooser pick html color names kRuler Pixel screen ruler kSnapshot Screen dump to jpg and/or png I use xpdf, found it much better than kpdf but that was some years ago when I used KDE in Slackware Linux. I see there are other open-source pdf viewers. System Rescue CD uses epdfview. I didn't like kWrite or kspread (spreadsheet that came with KDE). Abiword is much better than kWrite, and gnumeric is much better than the spreadsheet that came with KDE. I am not familiar with the other KDE apps. Tom ___ 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
Ports via svn, make fetchindex and make compatibility with NetBSD
Is it necessary to make fetchindex after downloading or updating the ports tree using svn? I have new installations of head and 10-stable where I so far can't connect to the Internet, though I can from Linux and NetBSD-current amd64. So I use subversion, built on NetBSD from pkgsrc, to checkout and update ports tree as well as system source tree. But I believe I can't run make fetchindex without Internet connection. Now I read that FreeBSD make has switched to bmake in the 10-stable and head branches. So could I run make fetchindex from NetBSD even if I don't attempt to actually build ports from NetBSD? I would have to point the MAKECONF to FreeBSD's /etc/make.conf rather than use NetBSD's /etc/mk.conf which is specific to NetBSD. Or is it safe to skip make fetchindex entirely? Tom ___ 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 via svn, make fetchindex and make compatibility with NetBSD
Building ports on NetBSD is a whole other kettle of fish. It's not going to work without a lot of effort to add compatibility changes. (Getting the ports working on DFly which is much more closely related to FBSD has been a fairly recent achievement, and that took quite a lot of local patches.) Cheers, Matthew I noticed on the DFly site that Dfly was switching from NetBSD pkgsrc to dports, which is a port of FreeBSD ports. I guess they like FreeBSD ports better than NetBSD pkgsrc. NetBSD pkgsrc has been ported to many other OSes including some non-Unixoid, but I don't really want to use pkgsrc for Linux. DFly is rather incompatible with my system; I tried their live USB including the latest release 3.6.0 amd64 and i386. So is OpenBSD. Tom ___ 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 via svn, make fetchindex and make compatibility with NetBSD
So could I run make fetchindex from NetBSD even if I don't attempt to actually build ports from NetBSD? I would have to point the MAKECONF to FreeBSD's /etc/make.conf rather than use NetBSD's /etc/mk.conf which is specific to NetBSD. Or is it safe to skip make fetchindex entirely? It is safe :) regards, Bapt Now I can feel more comfortable, I trust your insider knowledge. I still would have to make fetchlist from FreeBSD, then fetch from NetBSD, then boot back to FreeBSD to compile/build. Sort of cloak-and-dagger. Better would be if I could get Hiro H50191 USB wireless adapter to work with driver rsu, could even try ndis as fallback and to see if that works. I haven't yet tried with my new TP-Link wireless router that replaced a failing Netgear router. Tom ___ 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: phpMyAdmin-4.1.0
I have an update to phpMyAdmin in the works -- but version 4.1.0 now requires at least PHP 5.3 and MySQL 5.5. Currently I'm minded to fork a phpMyAdmin-4.0 port to allow support for people still using MySQL 5.1 or older versions of PHP, but... this isn't considered a major version change by the phpMyAdmin development team, so there won't be any support for the 4.0 series going forwards. Hence the putative phpMyAdmin40 port would be an unchanging snapshot of version 4.0.10. Knowing the history of phpMyAdmin with respect to security holes this phpMyAdmin40 port would likely have to be removed within a few months anyhow. What do people think? Is it worth forking the port? Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. I don't see the point in forking to maintain compatibility with outdated versions of PHP and MySQL. But what about compatibility with MariaDB in place of MySQL? Tom ___ 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
Build/install failure of devel/subversion
I tried to build devel/subversion on FreeBSD 10 prerelease amd64 (SVN revision 259409), and installation failed due to missing files. All dependencies built and installed successfully. First attempt quickly failed because of dependency databases/db42: DEPRECATED= Please migrate to databases/db5 but I got past that by installing databases/db6. Maybe I was overambitious enabling some options, like tests and tools? === The following configuration options are available for subversion-1.8.5: BDB=on: Berkeley DB support DOCS=on: Build and/or install documentation FREEBSD_TEMPLATE=on: FreeBSD Project log template GNOME_KEYRING=off: Build with GNOME Keyring auth support KDE_KWALLET=off: Build with KDE KWallet auth support MAINTAINER_DEBUG=off: Build debug version MOD_DAV_SVN=off: mod_dav_svn module for Apache 2.X NLS=on: Native Language Support P4_STYLE_MARKERS=on: Perforce-style conflict markers SASL=off: SASL support SERF=on: WebDAV/Delta-V (HTTP/HTTPS) repo access module STATIC=off: Build static version (no shared libs) SVNSERVE_WRAPPER=on: Enable svnserve wrapper (umask setter) TEST=on: Run subversion test suite TOOLS=on: Install several tools (svnauthz-validate and mod_dontdothat are among them) === Use 'make config' to modify these settings Earlier I failed, for a different error, to build devel/subversion on FreeBSD-HEAD amd64. Most relevant part of build log was: Compressing man pages (compress-man) === Staging rc.d startup script(s) === Installing for subversion-1.8.5 === Checking if devel/subversion already installed === Registering installation for subversion-1.8.5 pkg-static: lstat(/BETA1/usr/ports/devel/subversion/work10/stage/usr/local/lib/libsvn_fs_base-1.a): No such file or directory pkg-static: lstat(/BETA1/usr/ports/devel/subversion/work10/stage/usr/local/lib/libsvn_fs_base-1.la): No such file or directory pkg-static: lstat(/BETA1/usr/ports/devel/subversion/work10/stage/usr/local/lib/libsvn_fs_base-1.so): No such file or directory pkg-static: lstat(/BETA1/usr/ports/devel/subversion/work10/stage/usr/local/lib/libsvn_fs_base-1.so.0): No such file or directory *** Error code 74 Stop. make[1]: stopped in /BETA1/usr/ports/devel/subversion *** Error code 1 Stop. make: stopped in /BETA1/usr/ports/devel/subversion === Installation of subversion-1.8.5 (devel/subversion) failed === Aborting update ___ 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: If ports@ list continues to be used as substitute for GNATS, I'm unsubscribing
There are many messages on this thread, and I don't know which or what to quote, but I agree on send-pr being user-unfriendly. One problem is setting up mail with outbound SMTP server: sendmail is too mysterious/mystic to be useful. I think most email clients set up to use POP3 and SMTP server without using sendmail at all. I use mpop and msmtp. Many users with problems might be just getting started on FreeBSD installation and not have graphic interface yet and might thereby not be able to use WWW interface (lynx, maybe?). I have that problem on FreeBSD 10-stable and HEAD. Or maybe they have X installed but it won't start or is crippled. I have that problem on NetBSD. It helps if one also has NetBSD installed, and/or Linux with a pkgsrc-like or FreeBSD-ports-like package manager (such as Gentoo with portage) so as to compare notes/problems/options when something goes wrong, as happened to me recently with devel/subversion. This is not to bad-mouth FreeBSD, just to have a model for comparison, and more help than I've got so far from this list. Primary reason why I built devel/subversion on my USB stick installation of NetBSD-current amd64 was that re(4) driver works in NetBSD and Linux and fails on FreeBSD, OpenBSD and DragonFlyBSD latest releases. Tom ___ 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: If ports@ list continues to be used as substitute for GNATS, I'm unsubscribing
On Thu, Dec 19, 2013 at 01:44:57AM -0800, Anton Shterenlikht wrote: From: Thomas Mueller There are many messages on this thread, and I don't know which or what to quote, but I agree on send-pr being user-unfriendly. I disagree. I use only send-pr to send PRs. I use sendmail. I disagree with you. For new users, send-pr is a fucking usability train wreck, and insufficiently well documented. Sendmail is legendary for its obtuse configuration. I suppose you should be proud of the fact you find these tools easy to use, but that does not mean you should dismiss others' concerns over how difficult some people find them. The fact many people find these tools very difficult to use is in fact kind of a big problem, and I'm glad something is being done about it with regard to the bugzilla system. I wouldn't have chosen bugzilla if it was up to me, but it's not up to me and it's sure to be a huge improvement over the system currently in place, so I'm grateful for the work being done. Hopefully the command line send-pr tool will also be replaced with something that actually provides a low-friction way for people with problem reports to contribute to the FreeBSD project. In conclusion, I agree with Thomas (though I much prefer fdm over mpop, personally), and believe that send-pr (or its replacement, whenever that happens) desperately needs some better documentation. I rather suspect that a lot of people with problems to report simply give up and leave us with no clue there's anything wrong. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] I think train wreck applies more to sendmail than send-pr. Sendmail dates back to long-ago pre-Internet days where computer users didn't send email to other computer users. Now a computer user needs to be able to send through ISP's SMTP server. I see in FreeBSD 10-prerelease, certificates in /etc/mail, suspect that might be related to sendmail, but looks useful even to a sendmail nonuser. Otherwise I'd put WITHOUT_SENDMAIL=yes in /etc/src.conf . There needs to be documentation on how to use send-pr for sending through ISP's SMTP server, and computer's hostname should not have to match email address. Nowadays, computer users may have multiple email accounts. When I had OS/2 Warp 4, I sent mail by sendmail -t outgoing-message-with-all-headers but figuring what to add to sendmail.cf took many hours. Tom ___ 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: If ports@ list continues to be used as substitute for GNATS, I'm unsubscribing
At the beginning of the thread, I used the gcc developer list as an actual example. If anyone posst an inappropriate topic to the list, it may get answered, but it will always get a this is not appropriate for this list, please don't do it again, use the list for this next time. I can imagine it's a slight put-off for brand new users but it is effective. People make a mistake once, and after that they do the right thing. Since they are publicly corrected, you can imagine they educate dozens of people *before* they can make the same mistake. So I'm talking about policing the list consistently. If you don't feel up to taking on that role, then maybe unsubscribing is the way to go, though I hope its not as you have a lot of value to add. I had to try, but I suspected this thread would go the way of NetBSD (Much discussion, zero net effect) and so far it has. I expect this topic to die down soon and I'll unsubscribe around new years eve, since two weeks seems to be the ports grace period. :) John The GCC developer list was very gentle compared to Arch Linux lists. I asked the question, is there a way to build or rebuild the Arch base system from source code, as can be done with FreeBSD and NetBSD. Moderator rejected that post, saying I could find the answer in less than a minute in the wiki; I still haven't. When I asked for explanation, and if all Arch mailing lists were so moderated, I got no answer or just garbage. Rejected post was from last May 8; I quickly became an infant mortality on the Arch mailing lists: rather unsubscribe than be hopelessly tongue-tied. I am also on some NetBSD lists (pkgsrc-users, port-i386, port-and64, netbsd-users, current-users), and don't see how there is much discussion with zero net effect. NetBSD is much less stable on my hardware than FreeBSD. Reason for my recent surge in interest was that re(4) works on MSI Z77 MPOWER motherboard in NetBSD and Linux but not in FreeBSD, OpenBSD and DragonFlyBSD; I used downloadable USB-stick images in the case of OpenBSD and DragonFlyBSD. I was successful building subversion on NetBSD-current amd64, and use that to checkout and update src, doc and ports trees. Tom ___ 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
e: Build/install failure of devel/subversion
Same here on 9.2-STABLE. Looking at the logs, I saw strange libtool lines saying that the libs mentioned by pkg-static were not installed in /usr/local/lib, and a preamble about Berkeley DB 6 that had not been tested by Subversion developers and the fact that subversion's Berkeley DB backend was deprecated. So I switched the DBD option to off and install worked. YMMV of course. Regards, Olivier Thanks for response; I thought nobody was going to respond. I had successfully built subversion for FreeBSD 9.1_STABLE, subsequently upgraded to 9.2 postrelease. I also built devel/subversion successfully from pkgsrc on NetBSD-current amd64. So I looked at the options available and selected, and I was going to try again with BDB dropped. You typed DBD, I assume you meant BDB but mistyped. Then I won't have to boot the NetBSD-current amd64 16 GB USB stick every time I want to update the src (stable-10 and HEAD), ports and doc trees. Tom ___ 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: Build/install failure of devel/subversion
On Tue, Dec 24, 2013 at 3:11 AM, Thomas Mueller mueller6...@bellsouth.net wrote: Then I won't have to boot the NetBSD-current amd64 16 GB USB stick every time I want to update the src (stable-10 and HEAD), ports and doc trees. Scot Hetzel responded: Stable-10 and HEAD has svnlite, so you won't need to install the subversion port to update/download src, ports or doc trees. I am sort of put off by lite versions in general, even have WITHOUT_SVNLITE=yes in /etc/src.conf . I'd put WITHOUT_SENDMAIL=yes in /etc/src.conf as well but am attracted by having certs in /etc/mail. I originally partitioned hard disk using gdisk on a USB 2.0 stick installation of FreeBSD 9.2_STABLE. This installation includes subversion from ports, but then I found re(4) didn't work with Ethernet on new motherboard. I just had a thought, now that I have wi-fi working, Hiro 50191 USB adapter with rsu(4). Maybe I could chroot to FreeBSD 9.2-STABLE on USB stick after doing a null mount of /usr/src (also ports and doc) and establishing Internet connection? Presumably this would then use rsu(4) driver which is only on FreeBSD 10-stable and HEAD and not in GENERIC kernel config? Tom ___ 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: Qpopper Port
I am going to have to give up maintaining qpopper. Not because I don't have the interest or time, but because I simply cannot update any port. The old port system may have had issues, but it worked!!! The new one does not. I am completely unable to upgrade or install any ports on a 9.1 or higher system. I have a number of those in production and will have to now resort to obtaining ports from the original sources and making them work on my systems. Its a colossal pain in the *^*^. I tried portmaster qpopper to get the latest source. That failed with lots of errors in other ports. Too many to try to do individually. I then used pkg_delete to delete all ports. Repeated portmaster qpopper. Portmaster no longer exists. Tried pkg_add -r portmaster. Message to setsomething in /etc/make.conf. Did that and then tried to run pkg2ng as it requested. pkg2ng does not exist. Its not a port either. Dead end. Went to /usr/ports/port-mgmt/portmaster and did a make. Get errors that file names are misspelled. Perhaps the new port system can be used by those who spend their day using it, but for those of us who have real work to do and only use it when needed, its just not viable. I was able to build ports and upgrade with portmaster on FreeBSD 9.1 and 9.2-STABLE, and more recently, 10.0 prerelease and 11-HEAD. With 10.0 prerelease and 11-HEAD, I haven't got very far yet, not because of failures, but newness and maintaining four installations: 10.0 prerelease and 11-HEAD for both amd64 and i386. But I was able to use portmaster successfully. Tom ___ 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: What is the problem with ports PR reaction delays?
There have been some messages in this thread about users volunteering to check port PRs. What would this involve as to time and software setup on one's own computer? I have some limited time, but am not using poudriere. I don't want to be too disruptive to existing FreeBSD installation. With so many messages in this thread, I don't know what to quote or what to cite in References: header so am skipping these extras. Thomas Mueller ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: net/avahi-app core dumps signal 11
On Tue, 21 Jan 2014 23:37:08 -0200, Sergio de Almeida Lenzi wrote: avahi-daemon dumps core, and I am unable to determinw why because it aborts core just before reaching the main() procedure.. = #0 0x000801304604 in pthread_testcancel () from /lib/libthr.so.3 #1 0x0008012fc706 in open () from /lib/libthr.so.3 #2 0x000801517227 in __gets_chk () from /lib/libssp.so.0 #3 0x0008015173d2 in __chk_fail () from /lib/libssp.so.0 #4 0x000801516ace in .init () from /lib/libssp.so.0 #5 0x7fffd130 in ?? () #6 0x00080061e6d1 in r_debug_state () from /libexec/ld-elf.so.1 #7 0x00080061dd57 in __tls_get_addr () from /libexec/ld-elf.so.1 #8 0x00080061c099 in .text () from /libexec/ld-elf.so.1 #9 0x in ?? () = any ideas??? Seems like a bad interaction with stack protector (libssp). I managed to get working binaries (10.0-STABLE, amd64) by adding --disable-stack-protector to CONFIGURE_ARGS -- Thomas Mueller ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: net/avahi-app core dumps signal 11
On Fri, 31 Jan 2014 14:15:13 +0100, Dimitry Andric wrote: On 29 Jan 2014, at 11:54, Thomas Mueller tmuel...@sysgo.com wrote: On Tue, 21 Jan 2014 23:37:08 -0200, Sergio de Almeida Lenzi wrote: avahi-daemon dumps core, and I am unable to determinw why because it aborts core just before reaching the main() procedure.. = #0 0x000801304604 in pthread_testcancel () from /lib/libthr.so.3 #1 0x0008012fc706 in open () from /lib/libthr.so.3 #2 0x000801517227 in __gets_chk () from /lib/libssp.so.0 #3 0x0008015173d2 in __chk_fail () from /lib/libssp.so.0 #4 0x000801516ace in .init () from /lib/libssp.so.0 #5 0x7fffd130 in ?? () #6 0x00080061e6d1 in r_debug_state () from /libexec/ld-elf.so.1 #7 0x00080061dd57 in __tls_get_addr () from /libexec/ld-elf.so.1 #8 0x00080061c099 in .text () from /libexec/ld-elf.so.1 #9 0x in ?? () = any ideas??? Seems like a bad interaction with stack protector (libssp). I managed to get working binaries (10.0-STABLE, amd64) by adding --disable-stack-protector to CONFIGURE_ARGS Don't you think the stack protector code is trying to tell you the stack got smashed? :-) That may well be. Then there is still the quesiotn why executables built on 9 appear to work while those built on 10 do no work. E.g. this is most likely a real buffer overflow or something, and it should be properly fixed, instead of removing the seat belts. Sure. -- Thomas Mueller ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: net/avahi-app core dumps signal 11
[replying to my own message, oh my] On Fri, 31 Jan 2014 14:41:11 +0100, Thomas Mueller wrote: On Fri, 31 Jan 2014 14:15:13 +0100, Dimitry Andric wrote: On 29 Jan 2014, at 11:54, Thomas Mueller tmuel...@sysgo.com wrote: On Tue, 21 Jan 2014 23:37:08 -0200, Sergio de Almeida Lenzi wrote: avahi-daemon dumps core, and I am unable to determinw why because it aborts core just before reaching the main() procedure.. = #0 0x000801304604 in pthread_testcancel () from /lib/libthr.so.3 #1 0x0008012fc706 in open () from /lib/libthr.so.3 #2 0x000801517227 in __gets_chk () from /lib/libssp.so.0 #3 0x0008015173d2 in __chk_fail () from /lib/libssp.so.0 #4 0x000801516ace in .init () from /lib/libssp.so.0 #5 0x7fffd130 in ?? () #6 0x00080061e6d1 in r_debug_state () from /libexec/ld-elf.so.1 #7 0x00080061dd57 in __tls_get_addr () from /libexec/ld-elf.so.1 #8 0x00080061c099 in .text () from /libexec/ld-elf.so.1 #9 0x in ?? () = any ideas??? Seems like a bad interaction with stack protector (libssp). I managed to get working binaries (10.0-STABLE, amd64) by adding --disable-stack-protector to CONFIGURE_ARGS Don't you think the stack protector code is trying to tell you the stack got smashed? :-) That may well be. Then there is still the quesiotn why executables built on 9 appear to work while those built on 10 do no work. I had an older avahi build lying around on a 10-STABLE box (built December 19, 2013) and that does not show the problem. Now, when I build net/avahi-app from from current ports on that box, resulting binaries crash. [old build, December 19, 2013] nomad:/usr/ports/net/avahi-app# /usr/local/bin/avahi-browse Too few arguments [current build] nomad:/usr/ports/net/avahi-app# ./work/avahi-0.6.31/avahi-utils/.libs/avahi-browse Segmentation fault (core dumped) nomad:/usr/ports/net/avahi-app# size /usr/local/bin/avahi-browse work/avahi-0.6.31/avahi-utils/.libs/avahi-browse textdata bss dec hex filename 1958411764488 2524862a0 /usr/local/bin/avahi-browse 1958411764488 2524862a0 work/avahi-0.6.31/avahi-utils/.libs/avahi-browse Then there's a difference in the order of libraries in the ldd output, but I don't know if that is relevant: nomad:/usr/ports/net/avahi-app# ldd /usr/local/bin/avahi-browse work/avahi-0.6.31/avahi-utils/.libs/avahi-browse /usr/local/bin/avahi-browse: libavahi-client.so.3 = /usr/local/lib/libavahi-client.so.3 (0x80082) libdbus-1.so.3 = /usr/local/lib/libdbus-1.so.3 (0x800a2f000) libavahi-common.so.3 = /usr/local/lib/libavahi-common.so.3 (0x800c82000) libgdbm.so.4 = /usr/local/lib/libgdbm.so.4 (0x800e8e000) libssp.so.0 = /lib/libssp.so.0 (0x801098000) libintl.so.9 = /usr/local/lib/libintl.so.9 (0x80129a000) libthr.so.3 = /lib/libthr.so.3 (0x8014a3000) libc.so.7 = /lib/libc.so.7 (0x8016c8000) work/avahi-0.6.31/avahi-utils/.libs/avahi-browse: libavahi-client.so.3 = /usr/local/lib/libavahi-client.so.3 (0x80082) libdbus-1.so.3 = /usr/local/lib/libdbus-1.so.3 (0x800a2f000) libthr.so.3 = /lib/libthr.so.3 (0x800c82000) libavahi-common.so.3 = /usr/local/lib/libavahi-common.so.3 (0x800ea7000) libgdbm.so.4 = /usr/local/lib/libgdbm.so.4 (0x8010b3000) libssp.so.0 = /lib/libssp.so.0 (0x8012bd000) libintl.so.9 = /usr/local/lib/libintl.so.9 (0x8014bf000) libc.so.7 = /lib/libc.so.7 (0x8016c8000) On a hunch, I downgraded devel/dbus back from 1.6.18 to 1.6.12, now the resulting avahi programs no longer dump core. -- Thomas Mueller ___ 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
portmaster -w -r (pcre icu): how to avoid redundant rebuilding?
I see in the UPDATING file that I need to rebuild all ports that depend on pcre and icu: portmaster -w -r pcre and portmaster -w -r icu (I don't need -f ?) How do I do this without rebuilding the same ports twice? I am on pkgng, so I can use pkg info -r icu and same for pcre to list ports depending on icu and pcre (long lists). I just updated, from source, to: FreeBSD amelia2 9.1-STABLE FreeBSD 9.1-STABLE #14 r245542: Tue Jan 22 03:00:31 UTC 2013 root@amelia2:/usr/obj/usr/src/sys/SANDY amd64 Tom ___ 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: portsnap and the imminent demise of svn-cvs ports tree export
(current time: Wed 23 Jan 2013 02:43:43 AM UTC) --] [-- End of PGP output --] [-- The following data is signed --] We are on notice that the current ports tree will be soon no longer available via CVSup and friends. General consumers of the FreeBSD ports tree are being encouraged to switch to portsnap. http://lists.freebsd.org/pipermail/freebsd-ports-announce/2013-January/49.html The presence of the file LASTCOMMIT.txt, and the content of the $FreeBSD$ lines, in a portsnap-generated ports tree indicate that portsnap sources its data from a CVS export of the tree. Are there plans to migrate the portsnap source to the subversion tree before the end of February? # cd /usr/ports # make update -- Running portsnap -- Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found. Fetching snapshot tag from your-org.portsnap.freebsd.org... done. Fetching snapshot metadata... done. Updating from Sun Jan 20 16:00:15 PST 2013 to Sun Jan 20 16:05:39 PST 2013. Fetching 4 metadata patches... done. Applying metadata patches... done. Fetching 0 metadata files... done. Fetching 5 patches... done. Applying patches... done. Fetching 1 new ports or files... done. Removing old files and directories... done. Extracting new files: /usr/ports/LASTCOMMIT.txt /usr/ports/lang/basic256/ /usr/ports/sysutils/less/ /usr/ports/textproc/mifluz/ /usr/ports/www/Makefile /usr/ports/www/p5-LWP-Protocol-PSGI/ Building new INDEX files... done. # ident /usr/ports/www/Makefile /usr/ports/www/Makefile: $FreeBSD: ports/www/Makefile,v 1.3300 2013/01/20 23:49:48 svnexp Exp $ Thank you. -- John Marshall [-- End of signed data --] Your date is ahead of what the headers of your message say: From owner-freebsd-po...@freebsd.org Mon Jan 21 09:53:34 2013 Received: from pop.att.yahoo.com (pop2.sbc.mail.vip.ne1.yahoo.com [98.138.197.207]) by mueller6722.bellsouth.net (mpop-1.0.23) with POP3 for arlene; Mon, 21 Jan 2013 09:53:34 + X-Apparently-To: mueller6...@bellsouth.net via 98.139.172.126; Sun, 20 Jan 2013 17:01:32 -0800 ... Date: Mon, 21 Jan 2013 12:01:05 +1100 Anyway, my latest LASTCOMMIT.txt shows ## SVN ## Exported commit - http://svnweb.freebsd.org/changeset/base/310745 ## SVN ## CVS IS DEPRECATED: http://wiki.freebsd.org/CvsIsDeprecated ## SVN ## ## SVN ## r310745 | araujo | 2013-01-21 03:39:17 + (Mon, 21 Jan 2013) | 8 lines ## SVN ## Changed paths: ## SVN ##M /head/sysutils/syslinux/Makefile ## SVN ##M /head/sysutils/syslinux/distinfo ## SVN ##M /head/sysutils/syslinux/files/patch-Makefile ## SVN ##M /head/sysutils/syslinux/files/patch-libinstaller-syslxopt.c ## SVN ##M /head/sysutils/syslinux/pkg-descr ## SVN ##M /head/sysutils/syslinux/pkg-plist ## SVN ## ## SVN ## - Update to 5.00. ## SVN ## - Update MASTER_SITES. ## SVN ## - Add MAKE_JOBS_SAFE. ## SVN ## - Trim header. ## SVN ## ## SVN ## PR: ports/174180 ## SVN ## Submitted by: KATO Tsuguru tkato...@yahoo.com ## SVN ## ## SVN ## Tom ___ 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: portmaster -w -r (pcre icu): how to avoid redundant rebuilding?
On 01/22/13 06:26, Thomas Mueller wrote: I see in the UPDATING file that I need to rebuild all ports that depend on pcre and icu: portmaster -w -r pcre and portmaster -w -r icu (I don't need -f ?) How do I do this without rebuilding the same ports twice? I am on pkgng, so I can use pkg info -r icu and same for pcre to list ports depending on icu and pcre (long lists). I just updated, from source, to: FreeBSD amelia2 9.1-STABLE FreeBSD 9.1-STABLE #14 r245542: Tue Jan 22 03:00:31 UTC 2013 root@amelia2:/usr/obj/usr/src/sys/SANDY amd64 Tom I've not had any luck with avoiding redundant rebuilding as pcre and icu updates aren't sent out at the same time. Perhaps someone can say if I'm off my rocker, has anyone tried issuing 'portmaster -w -r icu pcre'? Perhaps that would avoid the redundant rebuilds? Of course that would only work if one waits for both updates to come out. -- Yours in Christ, Joseph A Nagy Jr I could possibly make lists of ports that depend on pcre and icu using pkg info -r icu (and also pcre, redirecting to files) Then I could try portmaster -w -r icu -r pcre or do I need to use -w twice? Then I could see what ports it would build, say n when asked if I wanted to rebuild those ports, assuming there would be config dialogs along the line. Then I would run the portmaster command again with | tee portm.log at the right end, see if I like what would be built before answering y. I would be able to login to another virtual terminal to examine portm.log file at the early stage when asked whether to rebuild the ports. Tom ___ 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: svn - but smaller?
To get started regarding svn with only the base system, as in a fresh install, what about the suggestion to download the ports tarball from the FreeBSD server? That can be done using ftp, I believe, or am I wrong? Then svn and its dependencies can be built. Not sure about the compatibility of this extracted tarball regarding subsequent portsnap fetch update or svn up /usr/src (in this case there is no .svn data directory, so it would be necessary to do a fresh svn checkout). Tom ___ 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
sysutils/pacman: use in FreeBSD?
I see to my surprise, in http://www.freshports.org/commits.php , that pacman from Archlinux has just been ported to FreeBSD. But how would pacman be used in FreeBSD, considering we already have ports and pkgng? Would pacman in FreeBSD be only for binary packages, or would it be used with Arch Build System to build packages from source as is done with FreeBSD ports and NetBSD pkgsrc? Tom ___ 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: portsnap and the imminent demise of svn-cvs ports tree export
Date: Mon, 21 Jan 2013 12:01:05 +1100 How do you work that out? None of the headers you've included show any problem. John sent his mail at 010105UT on 21st, and your headers say you received it at 095334UT on 21st - nearly 9 hours later. The X-Apparently-To header is 010132UT on the 21st (about 3s after FreeBSD forwarded it to me, se quite realistic). -- Peter Jeremy I think I might have misread something mentally transferring 3 at the end of 2013 to make Jan 21 into Jan 23: maybe the wrong time of day, too late going to bed. Tom ___ 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
sysutils/pacman: use in FreeBSD?
From my previous message: I see to my surprise, in http://www.freshports.org/commits.php , that pacman from Archlinux has just been ported to FreeBSD. But how would pacman be used in FreeBSD, considering we already have ports and pkgng? Would pacman in FreeBSD be only for binary packages, or would it be used with Arch Build System to build packages from source as is done with FreeBSD ports and NetBSD pkgsrc? Dmitry Marakasov amd...@amdmi3.ru responded: First, it can install ArchBSD (http://www.archbsd.net/) packages. These are created from FreeBSD ports, so it may be used as another binary package manager for FreeBSD. That seems quite useful to me for setting up jails, as world is just a package there and thus the installation is much simpler. Second, it may be used to install original Arch linux packages, letting you setup and manage another kind of linux environement on FreeBSD. Hower on practice because of our outdated linuxulator it won't work as it won't run recent linux binaries. I hope this will be fixed in future. I browsed http://www.archbsd.net/ . It looks like that web site and the ArchBSD project are in an early stage, not yet suitable to download and install. No Arch Build System, at least not yet. I didn't have much luck running anything Linux from either FreeBSD or NetBSD. OpenBSD can't read anything on my hard drive, neither can DragonFlyBSD, although DragonFlyBSD can see my hard drive partition structure, which OpenBSD can't. Tom ___ 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: Cronjob Cvsup - What?
W. D. w...@us-webmasters.com writes: According to: http://www.freebsd.org/news/2012-compromise.html Cvsup is deprecated. If I have a Cron entry like: #- #Min HrDOM Mnth DOW Command # At 3:46 in the morning, everyday, as root, update the ports tree: 46 3 * * * /usr/local/bin/cvsup -h cvsup12.FreeBSD.org /usr/share/examples/cvsup/ports-supfile #- What should I use: freebsd-update, Subversion, portsnap, or what? What would be the best Cron command to keep ports updated on a daily basis? Lowell Gilbert freebsd-questions-lo...@be-well.ilk.org responds: portsnap is almost certainly the best answer for you. freebsd-update is for the base system, not ports. If you needed version control features on your ports tree (especially if you were regularly contributing changes to ports), getting and updating your tree through subversion would have some extra features you might want, but it doesn't sound as if that is the case for you. Unless you have a specific reason why portsnap doesn't fit your use case, it's definitely the way to go for just keeping a ports tree updated regularly. I've always used portsnap fetch update after the initial portsnap fetch and portsnap extract. What would be the adverse side effect of using svn instead? Tom ___ 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: Cronjob Cvsup - What?
On Sun, 27 Jan 2013 08:22:02 -0500 Thomas Mueller wrote: I've always used portsnap fetch update after the initial portsnap fetch and portsnap extract. What would be the adverse side effect of using svn instead? RW rwmailli...@googlemail.com responded: In general it's best to avoid mixing update tools unless you fully understand all the corner cases and know it's safe. The most significant problem is they can lose track of what files need to be deleted, which can lead to obsolete patch files being left in the tree. One of the functions of portsnap extract is to eliminate extra files in port directories to avoid this problem. You miss my point. The intent was not to mix portsnap and svn but to use svn in a separate location, /usr/ports as opposed to the present /BETA1/usr/ports, with the intent to switch to svn. Of course, I realize I'd have to update at least three etc/make.conf files: hard drive installation, USB stick amd64 and USB stick i386. Tom ___ 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
Status of devel/icu, or icu4c
What is the status of devel/icu? I see on http://site.icu-project.org that ICU4J 50.1.1 released on 2012-Dec-17 ICU4C 50.1.2 released on 2013-Jan-16 I keep following http://www.freshports.org/commits.php daily, generally somewhat after midnight UTC, and nothing on devel/icu since I saw the update for NetBSD pkgsrc, whose updates I also follow daily somewhat after midnight UTC. I checked devel/icu/distinfo, and the icu4c distfile is still on 50.1.1. I'm concerned because the usr/ports/UPDATING file says all ports that depend on devel/icu need to be rebuilt/updated. Or is that due to a bump in the .so.49 - .so.50 file that would not be affected by a minor version update such as 50.1.1 to 50.1.2? Tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Status of devel/icu, or icu4c
What is the status of devel/icu? I see on http://site.icu-project.org that ICU4J 50.1.1 released on 2012-Dec-17 ICU4C 50.1.2 released on 2013-Jan-16 I keep following http://www.freshports.org/commits.php daily, generally somewhat after midnight UTC, and nothing on devel/icu since I saw the update for NetBSD pkgsrc, whose updates I also follow daily somewhat after midnight UTC. I checked devel/icu/distinfo, and the icu4c distfile is still on 50.1.1. I'm concerned because the usr/ports/UPDATING file says all ports that depend on devel/icu need to be rebuilt/updated. Or is that due to a bump in the .so.49 - .so.50 file that would not be affected by a minor version update such as 50.1.1 to 50.1.2? devel/icu has been updated to 50.1.2. Yes the updating entry concerned the switch from .so.49 - .so.50 regards, Bapt Thanks for letting me know, but I had already checked http://www.freshports.org/commits.php before downloading my email, though I could have looked at the web version of the most recent posts to po...@freebsd.org . I suppose failing to update all ports/packages that depend on a recently updated port/package could result in shared-library versions out of sync. Now I can have fun with a massive portmaster run. Tom ___ 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: security/gnupg
Many users have reported in the past that one of the problems with the ports system is that OPTIONS are not properly documented. Usually, if I spend some time, I can locate it but it is a PIA. However, with the security/gnupg port, I cannot find out specifically what this option does: [ ] STD_SOCKET Use standard socket for agent This is off by default. Is there any advantage to activating it and why isn't it using a standard socket to begin with? Maybe if a port had a file name options-descr or some such thing and it listed each available option in the port and specifically what it did or how it effected the operation of the application, it would prove beneficial to the end use. Just my 2ยข on the matter. Jerry I too have the problem of options being poorly documented. I've configured a port with two options that conflicted and only found out from the error message when the port failed to build. NetBSD pkgsrc documents the options better and notes when two options are incompatible with each other, or when exactly one of several options can or must be chosen. I also find the dialog to be a nuisance because of messing the screen especially when creating a log file. I'd like a better way of knowing what options are available and being able to choose separately from building the port. With NetBSD pkgsrc, options are placed in /etc/mk.conf for NetBSD and, I believe, /usr/pkg/etc/mk.conf for other OSes. Tom ___ 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: security/gnupg
/etc/make.conf, use OPTIONS_SET=list of options. You can also use UNSET in the same way for the converse. Setting BATCH=yes stops the dialogs appearing. Chris I want to know what ports have settable options, and might miss some. I guess I could make showconfig-recursive | tee showconfig.log , NetBSD pkgsrc has something that serves the same function. It's also possible to set an options for one or more but not all ports. I suppose, in the case of portmaster, I could run the command without a log file, answer n when prompted whether to do the build, then immediately run the same portmaster command again, but this time with a log file. I wish dialog could run on a separate screen and/or without the color. With NetBSD pkgsrc, I don't feel at all deprived for not having the dialog. Tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Why the port build log file has terminal escape sequences?
On 3 February 2013 04:14, Yuri y...@rawbw.com wrote: I redirect the log into the file: portupgrade -a 21 | tee portupgrade.log However, log still has escape sequences as if it was printed to the terminal: ^[[0m^[[34m^[[1mGenerating moc_mainwindow.cpp^M ^[[0m^[[34m^[[1mGenerating subscriptionlistdelegate.moc^M ^[[0m^[[34m^[[1mGenerating knconfigwidgets.moc^M ^[[0m^[[34m^[[1mGenerating previewdialog.moc^M ^[[34m^[[1mGenerating entriescountdialog.moc^M I believe this started not long ago. What is wrong? I guess this is a cmake/clang port? Cmake, clang and several other tools give colorised output. This is achieved with escape sequences. Chris A config dialog could also cause something like this but would normally be more severe. Tom ___ 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: Xorg totally unusable with KMS and new Xorg on Sandy Bridge system: how to undo
Thomas Mueller writes: I built the newer Xorg and it falls flat: goes to a nongraphic screen that is blank except for a rectangular cursor in the upper left corner, and now I want to get back to the earlier Xorg. System is Intel Sandy Bridge with i7 CPU. Robert Huff responds: You don't mention your graphics chip explicitly, but building libdrm with the KMS option was enough to prevent X from starting on a Radeon HD 3300. (Experimental, indeed! :-) Other will be able to help more if you could post the contents of /var/log/Xorg.0.log and your xorg.conf file. My /var/log/Xorg.0.log has 0 bytes! To Andrey Fesenko f0and...@gmail.com: Were you able to start X with # cat /etc/make.conf WITH_NEW_XORG=true WITH_KMS=true X.Org X Server 1.10.6 Release Date: 2012-02-10 intel(0): Integrated Graphics Chipset: Intel(R) Sandybridge Mobile (GT2+) (end of quote from Andrey Fesenko) Xorg -configure (by root) produced an error message, failed but left a file Xorg.conf.new Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 Screen 1 Screen1 RightOf Screen0 Screen 2 Screen2 RightOf Screen1 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section Files ModulePath /usr/local/lib/xorg/modules FontPath /usr/local/lib/X11/fonts/misc/ FontPath /usr/local/lib/X11/fonts/TTF/ FontPath /usr/local/lib/X11/fonts/OTF/ FontPath /usr/local/lib/X11/fonts/Type1/ FontPath /usr/local/lib/X11/fonts/100dpi/ FontPath /usr/local/lib/X11/fonts/75dpi/ EndSection Section Module Load extmod Load record Load dbe Load dri Load dri2 Load glx EndSection Section InputDevice Identifier Keyboard0 Driver kbd EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 6 7 EndSection Section Monitor Identifier Monitor0 VendorName Monitor Vendor ModelNameMonitor Model EndSection Section Monitor Identifier Monitor1 VendorName Monitor Vendor ModelNameMonitor Model EndSection Section Monitor Identifier Monitor2 VendorName Monitor Vendor ModelNameMonitor Model EndSection Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz, ### percent: f% ### [arg]: arg optional #Option DRI # [bool] #Option ColorKey # i #Option VideoKey # i #Option FallbackDebug # [bool] #Option Tiling# [bool] #Option LinearFramebuffer # [bool] #Option Shadow# [bool] #Option SwapbuffersWait # [bool] #Option TripleBuffer # [bool] #Option XvMC # [bool] #Option XvPreferOverlay # [bool] #Option DebugFlushBatches # [bool] #Option DebugFlushCaches # [bool] #Option DebugWait # [bool] #Option HotPlug # [bool] #Option RelaxedFencing# [bool] Identifier Card0 Driver intel BusID PCI:0:2:0 EndSection Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz, ### percent: f% ### [arg]: arg optional #Option ShadowFB # [bool] #Option Rotate# str #Option fbdev # str #Option debug # [bool] Identifier Card1 Driver fbdev BusID PCI:0:2:0 EndSection Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz, ### percent: f% ### [arg]: arg optional #Option ShadowFB # [bool] #Option DefaultRefresh# [bool] #Option ModeSetClearScreen# [bool] Identifier Card2 Driver vesa BusID PCI:0:2:0 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 SubSection Display Viewport 0 0 Depth 1 EndSubSection SubSection Display Viewport 0 0 Depth 4
Re: Xorg totally unusable with KMS and new Xorg on Sandy Bridge system: how to undo
From Warren Block wbl...@wonkity.com: After adding those, graphics/libdrm must be rebuilt, and x11-drivers/xf86-video-intel must have the KMS option enabled and be rebuilt. If you just added WITH_NEW_XORG, there will be other xorg components that need to be updated. O no, I'm getting rid of KMS and WITH_NEW_XORG because they produce an unusable Xorg installation that just crashes the system and requires Reset button. I guess I need to use portmaster with --force-config on x11/xorg ? Tom ___ 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: Bug in mail/mpop options list: only NLS appears in dialog
We also do support the same kind of things :)
First set NO_DIALOG=yes in make.conf and you are done with the dialog thing :)
second you can do the follow:
OPTIONS_SET=NLS NCURSES GTK2 X11
OPTIONS_UNSET= QT4
msmtp_SET= IDN
msmtp is the ${UNIQUENAME} obtained from make -VUNIQUENAME in the
/usr/ports/mail/msmtp
make showconfig should show you all the opitons
Concerning the mail/mpop is was a bug in options conversion which is fixed now
regards,
BApt
Does that mean I can set an individual port option by
${UNIQUENAME}_SET= option(s)-to-set
and unset by using UNSET in place of SET?
I fixed the Makefile bug in mpop even before I got your message, and rebuilt
mpop successfully.
Then portsnap fetch update did not get the fixed version.
Does that mean I should switch to svn from portsnap for ports?
That would provide one-stop shopping for ports, doc and src.
In the Makefile,
# New ports collection makefile for:mpop
# Date created: 2009-10-24
# Whom: Sylvio Cesar syl...@freebsd.org
#
# $FreeBSD: ports/mail/mpop/Makefile,v 1.13 2013/02/05 16:54:23 svnexp Exp $
#
PORTNAME= mpop
PORTVERSION=1.0.27
PORTREVISION= 1
CATEGORIES= mail
MASTER_SITES= SF
MAINTAINER= syl...@freebsd.org
COMMENT=MPOP is a small and fast POP3 client
LIB_DEPENDS=idn.17:${PORTSDIR}/dns/libidn
OPTIONS_DEFINE= GNUTLS GSASL
GNUTLS_DESC=GNUTLS Enable gnuTLS support
GSASL_DESC= GSASL GNU SASL authentication support
OPTIONS_DEFINE= NLS
USE_BZIP2= yes
GNU_CONFIGURE= yes
CONFIGURE_ARGS+=--with-libidn
MAN1= mpop.1
INFO= mpop
.include bsd.port.options.mk
.if ${PORT_OPTIONS:MGNUTLS}
LIB_DEPENDS+= gnutls.26:${PORTSDIR}/security/gnutls
CONFIGURE_ARGS+=--with-ssl=gnutls
.else
USE_OPENSSL=yes
CONFIGURE_ARGS+=--with-ssl=openssl
.endif
.if ${PORT_OPTIONS:MGSASL}
LIB_DEPENDS+= gsasl.16:${PORTSDIR}/security/gsasl
.else
CONFIGURE_ARGS+=--without-libgsasl-prefix
.endif
.if ${PORT_OPTIONS:MNLS}
USE_GETTEXT=yes
CONFIGURE_ARGS+=--enable-nls
PLIST_SUB= NLS=
.else
CONFIGURE_ARGS+=--disable-nls
PLIST_SUB= NLS=@comment
.endif
.include bsd.port.mk
(end of Makefile)
I figured the line
OPTIONS_DEFINE= NLS
wiped out the previous
OPTIONS_DEFINE= GNUTLS GSASL
and changed = to +=
That worked.
Tom
___
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 upgrade fails
On Thu, 21 Feb 2013 12:44:16 +0100, Andrea Venturoli wrote: # uname -a FreeBSD xx.x 9.0-RELEASE-p5 FreeBSD 9.0-RELEASE-p5 #2: Sat Dec 1 14:43:22 CET 2012 root@xx.x:/usr/obj/usr/src/sys/XX i386 portupgrade -R firefox ... /usr/local/local/storage/alamartmp/usr/ports/www/firefox/work/mozilla-release/obj-i386-portbld-fla-release/config/pythonpath.py -I../../config /usr/local/local/storage/alamartmp/usr/ports/www/mozalloc.so --uselist -- clang++ -Qunused-arguments -isystem/usr/local/include -Qunused-argumetor-dtor-privacy -Wno-overlength-strings -Wno-invalid-offsetof -Wno-variadic-macros -Wno-c++0x-ech=athlon-mp -fno-strict-aliasing -fno-exceptions -fno-strict-aliasing -fno-rtti -ffunction-sectfomit-frame-pointer -fPIC -shared -Wl,-z,defs -Wl,-h,libmozalloc.so -o libmozalloc.so mozalloc.GIN -Wl,-z,noexecstack -fprofile-generate -Wl,-rpath-link,/usr/local/local/storage/alamartmp/usocal/local/storage/alamartmp/usr/ports/www/firefox/work/fake/lib /usr/bin/ld: /usr/bin/../lib/libprofile_rt.a: No such file: No such file or directory clang++: error: linker command failed with exit code 1 (use -v to see invocation) gmake[5]: *** [libmozalloc.so] Error 1 ... Any hint? Disable PGO or build with GCC (I used make USE_GCC=4.6+). -- Thomas Mueller ___ 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
Status/version of graphics/png?
What is the status of graphics/png? I noticed NetBSD pkgsrc was prompt in updating to 1.6 (or was it 1.6.0?), even though they are behind in some other packages. I'm concerned with the prospect of having to rebuild all ports that depend on png when 1.5.x - 1.6. Tom ___ 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
Status of math/gnumeric unable to keep up with upstream releases?
What is the status of gnumeric being stuck at 1.10.17 when upstream has released 1.12.0 ? I think gnumeric = 1.11.x has gtk+ = 3.0.0 as a dependency? I checked gnumeric web site www.gnumeric.org . I see this is the same snag that prevents transmission 2.5 from building, though possibly one could do portmaster -o transmission-cli transmission ? So what is the status now of gtk+ 3.x ? Tom ___ 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
Status/version of graphics/png?
What is the status of graphics/png? I noticed NetBSD pkgsrc was prompt in updating to 1.6 (or was it 1.6.0?), even though they are behind in some other packages. I'm concerned with the prospect of having to rebuild all ports that depend on png when 1.5.x - 1.6. The status is that I wait for the availibility of an exp-run, to see the regressions in directly 5500 dependendent ports. This might not happen before the 8.4 release. kind regards Dirk - Dirk Meyer, Im Grund 4, 34317 Habichtswald, Germany - [dirk.me...@dinoex.sub.org],[dirk.me...@guug.de],[din...@freebsd.org] Thanks for letting me know, I guess it will be a long time. I haven't seen anything about FreeBSD 8.4, assume it's not in the immediate future. But then I wonder how pkgsrc was not bothered by having to see regressions in many dependent ports. I assume Linux source package systems such as Gentoo portage and Arch Build System are not taking so long but can't verify that. New packages are much easier to see on freshports (FreeBSD) and NetBSD pkgsrc than anywhere else I know. Tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Status/version of graphics/png?
from Dirk Meyer: Hallo Thomas Mueller, What is the status of graphics/png, now that FreeBSD 8.4_RC2 has been released and the ports tree has been unfrozen? Will it get the long overdue update to 1.6.x; how much regression testing needs to be done? 1.6.1 ist still fresh. The API has removed all backwards comatibility. From the 5500 ports we have about 500 that can build with png 1.6.x. The impact on the ports is still to much. We would have to patch 1000 autoconf scripts. For now the FreeBSD port stay with 1.5.x. It was discussed with mmembers from portmgs@ to wait with the update. kind regards Dirk Any idea of when or if png will be updated, or what has to happen regarding FreeBSD releases? There is also png 1.5.15 . I didn't know the API change was so radical; wonder how NetBSD pkgsrc was able to update to 1.6.x so fast. It may be easier in Linux, since Linux is the primary platform of many open-source software developers, and much such software is Linux-centric, but I didn't think NetBSD would have an easier time than FreeBSD. But then I didn't try the update on NetBSD, so I don't know if it really works right. One could use NetBSD pkgsrc on FreeBSD, but it would be a shotgun marriage, rough and not really designed for FreeBSD. NetBSD is unstable on my computer, Intel Sandy Bridge, often does not even boot, hangs at the login prompt. Tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Status/version of graphics/png?
from Chris Rees: What new features are you trying to take advantage of with png? I went to the libpng website and couldn't find the desired changelog, but found libpng 1.4.x and 1.5.x were still in active development, and there was also a beta 1.7.0 . 1.6.2 is the latest release. I notice that, since I sent my last message, FreeBSD ports upgraded to png 1.5.15 . So I don't really know about the differences in features between the various releases. I follow changes to both FreeBSD ports and NetBSD pkgsrc daily, some time after midnight UTC, notice there are usually many more additions to FreeBSD ports than to NetBSD pkgsrc. Tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Any way to keep two versions of Xorg?
Is there any way to keep two versions of Xorg-server, using no more than one at a time? Reason is the newer but unstable version with KMS, permitting full use of the newer Intel graphics chips. I switched to the new version but then couldn't run X at all, immediately crashing the system and requiring Reset button. I had a hard time but finally succeeded switching back, but would like if possible to see if anything can be done to make the newer Xorg work but without leaving myself entirely without a usable X. Sort of like China and Hong Kong: one country, two systems. Portupgrading/portmastering from the older Xorg to the newer Xorg only to have to switch back is too much trouble! Would I have to have a second installation, on a separate partition, with FreeBSD current (HEAD), to try the new Xorg, while keeping the older Xorg on 9-STABLE? I have enough hard drive space and use GPT, so no problem running short of partitions. Tom ___ 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: Proposal: do not show up the dialog(1) by default?
A lot of people seems to be complaining about the configuration dialog popping up all the time. What if we change the default behaviour to not pop up the dialog each time there is a changed option but only when the user explicitly type make config? Just a proposal, please give your opinion. Of course make config-recursive behaviour won't change. regards, Bapt The new dialog4ports has made the dialog much less disruptive than before, especially when teeing to a log file. So now I don't dread the dialog as I used to. But it would still be good to be able to set options through make.conf, comparable to what pkgsrc (NetBSD and ported to other mostly Unix-like OSes) and portage (Gentoo Linux) do. I have noticed how DOCS with docbook can be very cumbersome and overdone, how many different formats do we need? And hopefully docbook wouldn't have to be rebuilt every time for different ports that might require it. Tom ___ 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: Proper way to access executable's environment?
On Sun, 26 May 2013 11:06:29 -0700, David Wolfskill wrote: On Sun, May 26, 2013 at 07:55:03PM +0200, Stefan Ehmann wrote: ... So I have a couple of questions related to the above: * Is the patch correct?... Should be fine. See environ(7) or http://pubs.opengroup.org/onlinepubs/9699919799/functions/environ.html: In addition, the following variable, which must be declared by the user if it is to be used directly: extern char **environ; Cool; thanks. (Aside: I'd be happy to hear of plausible reasons the earlier approach does not appear to fail in i386. I'm suspecting some sort of compatibilty shim -- which was jettisoned for amd64, probably quite intentionally.) On AMD64 sizeof(void *)!=sizeof(int), thus warnings such as twm.c:250: warning: assignment makes pointer from integer without a cast should trigger alarms. === GDB session Program received signal SIGSEGV, Segmentation fault. 0x000801b60697 in strlen () from /lib/libc.so.7 (gdb) bt #0 0x000801b60697 in strlen () from /lib/libc.so.7 #1 0x0040b397 in main (argc=value optimized out, argv=value optimized out, environ=value optimized out) at twm.c:254 (gdb) frame 1 #1 0x0040b397 in main (argc=value optimized out, argv=value optimized out, environ=value optimized out) at twm.c:254 254 HomeLen = strlen(Home); (gdb) l 249 250 Home = getenv(HOME); 251 if (Home == NULL) 252 Home = ./; 253 254 HomeLen = strlen(Home); (gdb) p Home $1 = 0xdf3a Error reading address 0xdf3a: Bad address = Similarly, twm.c:306: warning: incompatible implicit declaration of built-in function 'calloc' including stdlib.h provides a proper declaration for calloc(). -- Thomas Mueller ___ 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: Announce: Unofficial binary package builds for old releases
cross posting this from hackers by request) Thanks to poudriere making this easy, we're now making public our (unofficial!) constantly being rebuilt repository of binary packages for old FreeBSD +releases and less popular architectures. See http://ftpmirror.your.org/pub/FreeBSD-Unofficial-Packages for instructions on how to use this. How do these differ from the official packages? 1) We're building packages for 9.1 all the way back to 7.2. 2) We're constantly grabbing new versions of ports and rebuilding as fast as the builders can go. Our goal is to rebuild the latest version (9.1 right now) in both amd64 and i386 every 24 hours, and all other versions every 7 days. 3) We're leaving up old versions (in the All directory) of everything, so you can grab older versions if we have them. 4) We're building everything twice, one by default and one a special internal-use version that has X11, examples, debugging and a few other features shut off. If the port can't be built without those features, it just gets skipped. (This may not be of use to anyone other than us) 5) We're building packages for i386, amd64, ia64, and have the hardware in house to build for PPC, ARM and sparc64 if anyone asks for it. (As of this writing, our ia64 box just started building things, and looks like it'll take another 5+ days to finish. If you need ia64, give it a few days.) Feel free to contact me with any questions, or suggestions for how this might be more useful to you. If you could actually use this on any other release or architecture that isn't currently listed, please let me know. If there's anyone out there that would prefer pkgng instead of the old style packages, we might be able to get those going too. This is primarily for our own internal use so I don't want to add support for a ton of things if nobody is going to use this, so speak up if you want something! -- Kevin Currently building ports from the source, I don't know if I would use these binary packages, but for pkgng, since FreeBSD is pushing users to switch from old-style packages, it might be good to provide pkgng packages for the newer releases of FreeBSD, = 9.0, maybe not worthwhile on 8.x and earlier. Tom ___ 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
Rebuild all ports for perl minor version update?
I see in the $PORTSDIR/UPDATING file that perl has been updated. perl5.16 has been updated from 5.16.2 to 5.16.3 . Since this is only (?) a minor-version update, why should it be necessary to upgrade all ports that depend on perl? portmaster -r perl In that case, why didn't they go to perl 5.18? Since so many ports depend on perl, and png too, maybe they should have updated perl and png (to 1.6.x) at the same time, then two massive portmaster or portupgrade runs could have been done together, as one even bigger portmaster or portupgrade run? Tom ___ 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
Rebuild all ports for perl minor version update?
from my priginal post: I see in the $PORTSDIR/UPDATING file that perl has been updated. perl5.16 has been updated from 5.16.2 to 5.16.3 . Since this is only (?) a minor-version update, why should it be necessary to upgrade all ports that depend on perl? portmaster -r perl In that case, why didn't they go to perl 5.18? Since so many ports depend on perl, and png too, maybe they should have updated perl and png (to 1.6.x) at the same time, then two massive portmaster or portupgrade runs could have been done together, as one even bigger portmaster or portupgrade run? John Marino responded: According to OpenBSD's Marc Espie on a pkgsrc list, a lot of established scripts will break on perl 5.18. Apparently it is not highly backwards compatible. A large % of the perl packages would cease to build if they just moved to 5.18. A minor upgrade is definitely better. But then why must all FreeBSD ports that depend on perl be rebuilt for a minor-version upgrade, 5.16.2 to 5.16.3? Tom ___ 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
Rebuild all ports for perl minor version update?
They don't really need to be re-built, but it is the safest way to go. I never go that way as he risk is EXTREMELY low and the time savings are HUGE. I just posted a much quicker way in the thread on Broken SNMP::Info. Start with portmaster p5-. Then go check on the remaining files (not directories) under /usr/local/lib/perl5/site_perl/OLD_PERL_VERSION and re-build the ports that installed them (pkg_info -W FILENAME to find them). Also, the changes to the perl ports were for the exact purpose of eliminating the future need to do these rebuilds for minor version updates. -- R. Kevin Oberman, Network Engineer Reading UPDATING again showed that there was a modification in direcctory structure. Maybe that's the reason for upgrading all ports that depend on perl. But then why not go further and upgrade to perl 5.18? So now I do the massive portmaster upgrade and am stopped by silly little things, like a conflict between the old transmission-gtk2 and the newer version, and later gcc can't make clean because of checksum errors. It didn't know to deinstall the old transmission-gtk2? So I ran pkg delete transmission-gtk2, knowing it was to be rebuilt to a newer version. Also, the gcc-4.6.4 upgrade was apparently successful, and no work directory remains for that port. A long operation can be done while the user is doing other things, like bed, food preparation, eating, outside errands, work on another computer, etc. Tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
graphics/gegl won't build, was Re: Rebuild all ports for perl minor version update?
I finished what I could of portmaster -r perl Last snag is graaphics/gegl and three ports that depend on graphics/gegl graphics/gegl graphics/gimp-app graphics/xsane print/hplip Last part of the log for portmaster graphics/gegl was gmake[4]: Leaving directory `/BETA1/usr/ports/graphics/gegl/work9amd64/gegl-0.2.0/docs/gallery' gmake[3]: Leaving directory `/BETA1/usr/ports/graphics/gegl/work9amd64/gegl-0.2.0/docs/gallery' gmake[3]: Entering directory `/BETA1/usr/ports/graphics/gegl/work9amd64/gegl-0.2.0/docs' GEGL_SWAP=RAM GEGL_PATH=../operations \ ../tools/operation_reference --ops-html operations.html ../tools/create-reference.rb\ ../gegl/gegl.h \ ../gegl/gegl-version.h \ ../gegl/buffer/gegl-buffer.h\ ../gegl/gegl-utils.h \ ../gegl/property-types/gegl-color.h\ ../gegl/gegl-matrix.h \ ../gegl/property-types/gegl-path.h\ ../gegl/property-types/gegl-curve.h\ api.html ../tools/create-reference.rb:331:in `block (2 levels) in main': invalid byte sequence in US-ASCII (ArgumentError) from ../tools/create-reference.rb:325:in `foreach' from ../tools/create-reference.rb:325:in `block in main' from ../tools/create-reference.rb:318:in `times' from ../tools/create-reference.rb:318:in `main' ../gegl/gegl.h gmake[3]: *** [api.html] Error 1 gmake[3]: Leaving directory `/BETA1/usr/ports/graphics/gegl/work9amd64/gegl-0.2.0/docs' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/BETA1/usr/ports/graphics/gegl/work9amd64/gegl-0.2.0/docs' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/BETA1/usr/ports/graphics/gegl/work9amd64/gegl-0.2.0' gmake: *** [all] Error 2 *** [do-build] Error code 1 Stop in /BETA1/usr/ports/graphics/gegl. *** [build] Error code 1 Stop in /BETA1/usr/ports/graphics/gegl. === make failed for graphics/gegl === Aborting update === Killing background jobs Terminated === You can restart from the point of failure with this command line: portmaster flags graphics/gegl === Exiting Tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: graphics/gegl won't build, was Re: Rebuild all ports for perl minor version update?
Same thing happened to me. I fixed it with: LC_ALL=en_US.UTF-8 LANG=en_US.UTF-8 portmaster -r perl I did not use both of them but I can't remember which one did the trick. Andrei Vrincianu Thanks for help, but the real answer came from my subsequent daily visit to http://www.freshports.org/commits.php I noticed an update in graphics/gegl, didn't know if it would fix the bug, but figured I'd try, starting with portsnap fetch update I ran portmaster first on gegl, then on the three ports that depend on gegl: successful. No need to run portmaster -r perl again, since most of the ports in question had already been rebuilt (all but four). Tom ___ 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: [HEADS UP] switch default xorg version in 9.1 and later
Hi! It is time to switch the default version of xorg on FreeBSD 9.1 and later, including CURRENT. In general this means better support for modern hardware, especially intel hardware, at the cost of support for some legacy hardware. The old version will still be around, and be the default for FreeBSD releases prior to 9.1, it is also possible to get the old version by setting WITHOUT_NEW_XORG= in /etc/make.conf. The attached patch will make the switch, and I intend to commit it ASAP unless something major shows up. The patch is also available at http://people.freebsd.org/~zeising/xorg-switch.diff Regards! -- Niclas Zeising FreeBSD x11 team PS. Please respect reply-to, to avoid too much cross posting. Now I am a bit confused, should it be x...@freebsd.org or freebsd-...@freebsd.org, or is one an alias for the other? Anyway, my concern was some complications in running the newer Xorg with Intel graphics. There was the danger that it might not be possible to go to text console after going into X, so I have questions on how to stay with the graphical interface and not go back to text console. If this belongs on another thread, feel free to change the subject to Xorg acrobatics. My question is how to go into X in such a way that there can be multiple users simultaneously logged in, root and nonroot, and all users have access to graphic applications (Mozilla Seamonkey for instance). I also want to be able to switch to or restart with a different window manager without going to a text console in between; this might require closing all applications and logging out. I don't really want to use gdm, kdm or xdm if I can help it. I don't think xdm would work anyway. My previous attempt with the new Xorg and KMS produced a completely nonrunnable X, immediately crashed, requiring Reset button, and I had a dilly of a time going back to the older Xorg. I might this time have an alternate xorg.conf with Driver=vesa for fallback so as to retain access to Xorg if the new Xorg bombs out with Intel driver: haven't tested this but hope it would work. Tom ___ 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
Bugs in print/hplip assuming Linux file structure
I am trying to configure an HP LaserJet m1212nf MFP and failing possibly because the setup can't find files normal for Linux but different in FreeBSD. I get error messages such as (running as root): Searching... (bus=usb, search=(None), desc=0) error: Failed to find the lsusb command cat: /etc/issue: No such file or directory warning: distro is not found in AUTH_TYPES cat: /etc/issue: No such file or directory I also get warning: distro is not found in AUTH_TYPES Now it seems to be just hanging. I just get |/-\|/-\ ... apparently ad infinitum. Next step is to try with Ethernet conection, since this multifunction printer supports both USB and Ethernet. I tried that, no luck. If I run hp-setup -i and provide path to .ppd file, it ends with error: Printer queue setup failed. Please restart CUPS and try again. No success with FreeBSD with this printer. If that fails, then I try on my USB-stick installation of NetBSD 6.1 with pkgsrc; pkgsrc and compiling work is done on SATA hard drive. If that fails, both USB and Ethernet, then on to Linux (Gentoo?). I can also try with the installation CD (for MS-Windows) with wine-devel in FreeBSD, to see if that works. If all that fails, then, O Brother, I might get another printer, certainly won't be HP. I have felt for quite some time now that I don't want to ever again buy anything HP. I will also want a printer that does not require a proprietary plugin. Brother? Tom ___ 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
Use of sysutils/pacman in FreeBSD?
I recognize pacman as a package manager for Arch Linux along with Arch Build System, but how would pacman be used in FreeBSD? Binary-only package manager or build from source for FreeBSD, or would it be used to add packages to an Arch Linux installation while running from FreeBSD? I notice pacman has also been ported to other Linux distributions, in some cases with substantial modifications. Tom ___ 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: Use of sysutils/pacman in FreeBSD?
Well, there's ArchBSD project (http://archbsd.net/), and pacman may be used to install packages from it (to quickly set up a jail, for example, as FreeBSD world is just another package there). However, the original reason I've ported it was to be able to install a genuine linux distribution into a chroot, as linux_base* from ports are outdated to complete uselessness. Unfortunately, that didn't work because our linuxulator is outdated as well: recent linux binaries either demand higher kernel version or (if compat.linux.osrelease is bumped) segfault. If that issue is resolved (I've heard there's some work on linuxulator ongoing), pacman will be ready for installing ArchLinux into jail/chroot. would it be used to add packages to an Arch Linux installation while running from FreeBSD? That too, but it's currently impossible, as it needs to run linux binaries in the chroot, while they doesn't really run. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru Thanks for response. So I guess it can't be used for its intended purpose unless one wants to use an outdated Linux kernel. I also looked for Gentoo portage in the ports but didn't find it. But again, Gentoo portage wouldn't be useful unless one wants to use an outdated Linux kernel. With rather new computer hardware, I don't really want anything outdated. I am curious to see how pacman and the Arch Build System work, though I am held back by hostile Arch Linux emailing lists and fora. Tom ___ 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
