Re: graphics/opengl-man usefulness
Peter Jeremy wrote on Mon, May 02, 2011 at 06:54:11PM +1000: Hi Martin, Whilst looking for OpenGL stuff in ports, I found graphics/opengl-man. On first glance, it seems quite useful but when I looked closer, I saw that it hasn't been updated for nearly 7 years and refers to a long obsolete version of OpenGL. Is it still worth having this port? Depends on what the manpages in the actual OpenGL package do. Problem is there is no one official OpenGL package. The package could use an update for sure either way. Martin -- %%% Martin Cracauer craca...@cons.org http://www.cons.org/cracauer/ ___ 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/cmucl broken on amd64?
Douglas Thrift wrote on Thu, Jun 10, 2010 at 02:27:25PM -0700: Hello, I've run into this before and it seems to me like the port should actually depend on misc/compat6x. I emailed Martin about this a while back, but never received any reply. Apparently there is even an open bug for this: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/146680 Oops. Sorry I'll fix it. Right now I think there's a general lack of people building CMUCL binaries, BTW. Martin Hope this helps! -- Douglas William Thrift douglas...@gmail.com http://douglasthrift.net/ On 6/10/2010 1:43 PM, C. P. Ghost wrote: Hello Martin, *, the port lang/cmucl has a dependency on a very old libutil, libc and libm: % lisp /libexec/ld-elf.so.1: Shared object libutil.so.5 not found, required by lisp % which lisp /usr/local/bin/lisp % ldd `which lisp` /usr/local/bin/lisp: libutil.so.5 = not found (0x0) libm.so.4 = not found (0x0) libc.so.6 = not found (0x0) % pkg_info -W /usr/local/bin/lisp /usr/local/bin/lisp was installed by package cmucl-19f_1 I've reinstalled the port, but still the same problem. misc/compat4x (compat4x-i386-5.3_9) is installed (and updated) too. Still, no joy. Any other way to get cmucl on amd64? Thanks, -cpghost. -- %%% Martin Cracauer craca...@cons.org http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: HEADS UP: utmp.h gone. All welcome utmpx.h.
editors/emacs21 and emacs22 are still broken with this. Changing utmp to utmpx in #include and in the struct declares I still get: filelock.c:297: error: 'struct utmpx' has no member named 'ut_time' filelock.c:299: error: 'struct utmpx' has no member named 'ut_time' Any suggestions? The manpage is still for utmp, not utmpx, unless my -current got hopelessly out of sync. Martin -- %%% Martin Cracauer craca...@cons.org http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: HEADS UP: utmp.h gone. All welcome utmpx.h.
Martin Cracauer wrote on Fri, Feb 12, 2010 at 05:24:06PM -0500: editors/emacs21 and emacs22 are still broken with this. Changing utmp to utmpx in #include and in the struct declares I still get: filelock.c:297: error: 'struct utmpx' has no member named 'ut_time' filelock.c:299: error: 'struct utmpx' has no member named 'ut_time' Any suggestions? The manpage is still for utmp, not utmpx, unless my -current got hopelessly out of sync. Never mind. Suggested patch sent to port maintainer. Thanks Martin -- %%% Martin Cracauer craca...@cons.org http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Binary packages for releases and portupgrade
Gary Jennejohn wrote on Wed, Jan 06, 2010 at 04:31:48PM +0100: On Tue, 05 Jan 2010 14:45:05 -0800 Doug Barton do...@freebsd.org wrote: Martin Cracauer wrote: RELENG_8 will lift be out of binary ports, at least as far as portupgrade is concerned. Sorry, I don't understand that sentence. I would guess this should read will be left out of... Follows logically from his concern that there are no binary packages for -STABLE. Right. I meant going -stable will lift me out of binary ports [support]. So the verdict is to hunt down OpenOffice packages manually and install them so that portupgrade ignores them, then go from there. ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/ seems to have what `portupgrade -P` should expect, right? So I wouldn't have to move from stable to release+sec. Martin -- %%% Martin Cracauer craca...@cons.org http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Binary packages for releases and portupgrade
Peter Ulrich Kruppa wrote on Wed, Jan 06, 2010 at 08:46:38PM +0100: On Wed, 6 Jan 2010, Martin Cracauer wrote: So the verdict is to hunt down OpenOffice packages manually and install them so that portupgrade ignores them, then go from there. ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/ seems to have what `portupgrade -P` should expect, right? So I wouldn't have to move from stable to release+sec. I wonder if people who succeed in building OOo (happens about twice a year to me) could put their packages on some kind of ftp server. From their mailing list I get the impression OOo-porting team could need all kind of help. Might be easier to just slam a Debian into a chroot. How do chroot and Linuxulator play together, anyway? Can I have a random-Linux in /compat/linux and then have a different one in /compat/linux/var/chroot/debian ? Alternatively I could just leave this poor notebook alone WRT building and run the same FreeBSD on one of my beefier machines to build binary packages and share the successes. Would probably involve two complete installations, one with a ports tree that only ever builds OO (and pulls in it's dependencies but nothing else). Martin -- %%% Martin Cracauer craca...@cons.org http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Binary packages for releases and portupgrade
Peter Ulrich Kruppa wrote on Wed, Jan 06, 2010 at 09:43:21PM +0100: On Wed, 6 Jan 2010, Martin Cracauer wrote: Peter Ulrich Kruppa wrote on Wed, Jan 06, 2010 at 08:46:38PM +0100: On Wed, 6 Jan 2010, Martin Cracauer wrote: So the verdict is to hunt down OpenOffice packages manually and install them so that portupgrade ignores them, then go from there. ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/ seems to have what `portupgrade -P` should expect, right? So I wouldn't have to move from stable to release+sec. I wonder if people who succeed in building OOo (happens about twice a year to me) could put their packages on some kind of ftp server. From their mailing list I get the impression OOo-porting team could need all kind of help. Might be easier to just slam a Debian into a chroot. How do chroot and Linuxulator play together, anyway? Can I have a random-Linux in /compat/linux and then have a different one in /compat/linux/var/chroot/debian ? Alternatively I could just leave this poor notebook alone WRT building and run the same FreeBSD on one of my beefier machines to build binary packages and share the successes. Would probably involve two complete installations, one with a ports tree that only ever builds OO (and pulls in it's dependencies but nothing else). If you manage to install OOo in Linuxolator, please publish some kind of HOWTO... If there is a serious question WRT it does run in the Linux emulator that would be easy enough to test, I can just NFS-mount one of my diskless Debians. Today I started an experiment: I created a jail as a clean build enviroment for OOo. Yet it has installed 145 dependencies and not even started building OOo. I expected nothing less. The Java requirement is particularly annoying on FreeBSD. And all that do get a Powerpoint clone with drunker mouse pointer syndrome written in tcl... Martin -- %%% Martin Cracauer craca...@cons.org http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Binary packages for releases and portupgrade
It's time to bite the bullet. My 1.3 GHz Pentium-M Notebook just can't keep up with the port building. I need OpenOffice and stuff and the party is really over at that point. I need something with binary packages. Do I understand that correctly if I run 8.0 release I get to have prebuilt binaries as recognized by portupgrade? What happens to the minor security updates? Can I follow TRELENG_8_0 and port portsupgrade recognize this as something that uses 8-release binary packages? Any other recommendations? Martin -- %%% Martin Cracauer craca...@cons.org http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Binary packages for releases and portupgrade
Doug Barton wrote on Tue, Jan 05, 2010 at 01:58:57PM -0800: Martin Cracauer wrote: It's time to bite the bullet. My 1.3 GHz Pentium-M Notebook just can't keep up with the port building. I need OpenOffice and stuff and the party is really over at that point. I need something with binary packages. Do I understand that correctly if I run 8.0 release I get to have prebuilt binaries as recognized by portupgrade? Well, 8-release or 8-stable should both be fine for this purpose, for most packages, with portupgrade or portmaster. My understanding is that we've given up trying to produce packages for openoffice on all branches. Are you saying there are binary packages for 8-stable? I thought I can only have them for -RELEASE? What happens to the minor security updates? Can I follow TRELENG_8_0 and port portsupgrade recognize this as something that uses 8-release binary packages? RELENG_8_0 is _exactly_ 8.0-RELEASE, and will never change. If you want 8-stable, RELENG_8 is the way to go. Otherwise you will need to update the tag each time a new security branch is created. RELENG_8 will lift be out of binary ports, at least as far as portupgrade is concerned. RELENG_8_0 will have emergency fixes AFAIK and I was hoping that I could run that and make portupgrade to the right thing (recognize the binary packages a insert them appropriately). If we have binary packages for 8-stable and/or if I can coerce portupgrade to use 8-release packages on 8-stable that would be fine, too. Martin -- %%% Martin Cracauer craca...@cons.org http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
How do conditionalize plist on $NOPORTDOCS (was: lang/cmucl - fails: install_error)
The problem mailed to me below is caused by NOPORTDOCS=yes
The port's Makefile properly conditionalizes on it, but pkg-plist does not.
How do I conditionalize ppk-list on NOPORTDOCS=yes?
Makefile:
.if !defined(NOPORTDOCS)
@${MKDIR} ${DOCSDIR}
${INSTALL_DATA} ${WRKDIR}/doc/cmucl/* ${DOCSDIR}
.endif
pkg-plist:
%%DOCSDIR%%/README
%%DOCSDIR%%/release-19c.txt
Martin
[EMAIL PROTECTED] wrote on Sun, Nov 16, 2008 at 06:52:57AM +0200:
Hi,
The build which triggered this email is done under tinderbox-2.4.3, on
7-STABLE on amd64, with tinderd_flags=-nullfs -plistcheck -onceonly
and ccache support, with the official up-to-date Ports Tree, with the
following vars set:
NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes.
The build of this port was tried 6 times since last BotMail
(probably while trying to build ports that depend on it).
Excerpt from http://T64.TecNik93.com/logs/7-STABLE-FTP/cmucl-19c.log :
building cmucl-19c in directory /var/tinderbox/7-STABLE-FTP
maintained by: [EMAIL PROTECTED]
building for: 7.0-STABLE amd64
port directory: /usr/ports/lang/cmucl
Makefile ident: $FreeBSD: ports/lang/cmucl/Makefile,v 1.31 2007/10/04
01:25:15 edwin Exp $
prefixes: LOCALBASE=usr/local X11BASE=usr/local
NO* env vars: NOPORTDOCS=yes NOPORTEXAMPLES=yes NOPORTDATA=yes
build started at Sun Nov 16 04:52:37 UTC 2008
.Last 40 lines of the log..
=== cmucl-19c depends on shared library: c.4 - found
=== Configuring for cmucl-19c
phase 5: make test
make: don't know how to make regression-test(continuing)
phase 6: make install
add_pkg localedata-5.4.tbz compat4x-i386-5.3_9.tbz
adding dependencies
pkg_add localedata-5.4.tbz
skipping localedata-5.4, already added
pkg_add compat4x-i386-5.3_9.tbz
skipping compat4x-i386-5.3_9, already added
=== Installing for cmucl-19c
=== cmucl-19c depends on shared library: c.4 - found
=== Generating temporary packing list
=== Checking if lang/cmucl already installed
install -s -o root -g wheel -m 555 /work/a/ports/lang/cmucl/work/bin/lisp
/usr/local/bin
cd /work/a/ports/lang/cmucl/work /usr/bin/find lib | /usr/bin/cpio -pdm
-L -R root:wheel /usr/local
48081 blocks
install -o root -g wheel -m 444
/work/a/ports/lang/cmucl/work/man/man1/cmucl.1 /usr/local/man/man1
install -o root -g wheel -m 444
/work/a/ports/lang/cmucl/work/man/man1/lisp.1 /usr/local/man/man1
=== Compressing manual pages for cmucl-19c
=== Registering installation for cmucl-19c
phase 7: make package
=== Building package for cmucl-19c
tar: share/doc/cmucl/README: Cannot stat: No such file or directory
tar: share/doc/cmucl/release-19c.txt: Cannot stat: No such file or directory
tar: Error exit delayed from previous errors.
pkg_create: make_dist: tar command failed with code 256
Creating package /tmp/packages/All/cmucl-19c.tbz
Registering depends: compat4x-i386-5.3_9 localedata-5.4.
Creating bzip'd tar ball in '/tmp/packages/All/cmucl-19c.tbz'
*** Error code 1
Stop in /a/ports/lang/cmucl.
build of /usr/ports/lang/cmucl ended at Sun Nov 16 04:52:55 UTC 2008
A description of the testing process can be found here:
http://T32.TecNik93.com/FreeBSD/QA-Tindy/
Thanks for your work on making FreeBSD better,
--
IOnut - Un^d^dregistered ;) FreeBSD user
Intellectual Property is nowhere near as valuable as Intellect
FreeBSD committer - [EMAIL PROTECTED], PGP Key ID 057E9F8B493A297B
--
%%%
Martin Cracauer [EMAIL PROTECTED] http://www.cons.org/cracauer/
FreeBSD - where you want to go, today. http://www.freebsd.org/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How do conditionalize plist on $NOPORTDOCS (was: lang/cmucl - fails: install_error)
Ion-Mihai Tetcu wrote on Tue, Nov 18, 2008 at 06:57:17PM +0200: On Tue, 18 Nov 2008 11:05:28 -0500 Martin Cracauer [EMAIL PROTECTED] wrote: The problem mailed to me below is caused by NOPORTDOCS=yes [ .. ] [EMAIL PROTECTED] wrote on Sun, Nov 16, 2008 at 06:52:57AM +0200: Hi, BTW, you got the same error in two other BotMails (at least): From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: lang/cmucl - fails: install_error Date: Sun, 24 Aug 2008 13:45:17 +0300 (EEST) From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: lang/cmucl - fails: install_error Date: Wed, 3 Sep 2008 07:06:07 +0300 (EEST) Did you received those emails ? I thought somebody else messed with my port and waited for him/her to fix it :-) Sorry. Which is kind of true, I didn't put these lines into pkg-plist. But it seems to have been a multi-port sweep. While we are talking, how do you guys thing I should handle this problem: it's a binary port. There are different binaries for FreeBSD-6.x, 7.x, 8.x http://common-lisp.net/project/cmucl/downloads/release/19e/ The 6.3 will run everywhere. Should I just use that one? Do you want me to conditionalize on FreeBSD version? Martin -- %%% Martin Cracauer [EMAIL PROTECTED] http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How do conditionalize plist on $NOPORTDOCS (was: lang/cmucl - fails: install_error)
Ion-Mihai Tetcu wrote on Tue, Nov 18, 2008 at 07:28:37PM +0200: On Tue, 18 Nov 2008 12:08:26 -0500 Martin Cracauer [EMAIL PROTECTED] wrote: While we are talking, how do you guys thing I should handle this problem: it's a binary port. There are different binaries for FreeBSD-6.x, 7.x, 8.x http://common-lisp.net/project/cmucl/downloads/release/19e/ The 6.3 will run everywhere. Should I just use that one? Do you want me to conditionalize on FreeBSD version? If they bother to release different native binaries for our supported OS versions let encourage them to keep doing that ;-) They == kind of me, although I didn't build these particular binaries. Is there prior art in ports about how to do this? What do I do with oddball version numbers? Martin -- %%% Martin Cracauer [EMAIL PROTECTED] http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How do conditionalize plist on $NOPORTDOCS
While we are talking, how do you guys thing I should handle this problem: it's a binary port. There are different binaries for FreeBSD-6.x, 7.x, 8.x http://common-lisp.net/project/cmucl/downloads/release/19e/ The 6.3 will run everywhere. Should I just use that one? Do you want me to conditionalize on FreeBSD version? If they bother to release different native binaries for our supported OS versions let encourage them to keep doing that ;-) They == kind of me, although I didn't build these particular binaries. Is there prior art in ports about how to do this? What do I do with oddball version numbers? Perhaps you can conditionalize the DISTNAME based on the FreeBSD version number, as shown on this page: http://www.freebsd.org/doc/en/books/porters-handbook/freebsd-versions.html? If you do that, just make sure that the distinfo file has an entry for each possible DISTNAME value, so the checksum verification will work on any FreeBSD version. So what happens when a user runs FreeBSD-6, installs such a port, then upgrades to FreeBSD-7. Would the port for the installed package come up with the wrong plist and whatnot? Martin -- %%% Martin Cracauer [EMAIL PROTECTED] http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How do conditionalize plist on $NOPORTDOCS
Wesley Shields wrote on Tue, Nov 18, 2008 at 01:36:23PM -0500: On Tue, Nov 18, 2008 at 01:30:33PM -0500, Martin Cracauer wrote: While we are talking, how do you guys thing I should handle this problem: it's a binary port. There are different binaries for FreeBSD-6.x, 7.x, 8.x http://common-lisp.net/project/cmucl/downloads/release/19e/ The 6.3 will run everywhere. Should I just use that one? Do you want me to conditionalize on FreeBSD version? If they bother to release different native binaries for our supported OS versions let encourage them to keep doing that ;-) They == kind of me, although I didn't build these particular binaries. Is there prior art in ports about how to do this? What do I do with oddball version numbers? Perhaps you can conditionalize the DISTNAME based on the FreeBSD version number, as shown on this page: http://www.freebsd.org/doc/en/books/porters-handbook/freebsd-versions.html? If you do that, just make sure that the distinfo file has an entry for each possible DISTNAME value, so the checksum verification will work on any FreeBSD version. So what happens when a user runs FreeBSD-6, installs such a port, then upgrades to FreeBSD-7. Would the port for the installed package come up with the wrong plist and whatnot? Maybe I'm misunderstanding what you're asking but if the port installs different files based upon the version it's being installed on it should use PLIST_SUB accordingly. http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/plist.html But you'd have the wrong one installed. Your freebsd-7 would have the freebsd-6 package installed and the installed files don't match. On second thought, I don't think it matters since it's not different from having /usr/ports/lang/cmucl/* updated to something new. Never mind. Martin -- %%% Martin Cracauer [EMAIL PROTECTED] http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
