Re: Best way to have a port...
In message: <20100302120308.ga53...@elmar.spoerlein.net> Ulrich Spörlein writes: : On Mon, 01.03.2010 at 23:51:25 -0700, M. Warner Losh wrote: : > ... that builds part of FreeBSD? : > : > Let me back up... : > : > I'm trying to create a port for gcc and binutils that is configured : > for FreeBSD for a given machine. FreeBSD mips, say. binutils was : > relatively easy (once I ported our mips support forward). However, : > gcc vexes me. It requires, to build libgcc and friends, a fully : > populated include tree. And it wants to use : > /usr/local/freebsd-mips/include instead of /usr/include (which is : > good). However, the former doesn't exist. I'd like to create a port : > for it, but I'm unclear how to even start. This port should consist : > of all files from make includes TARGET_ARCH=mips. : > : > So, some questions: First, how do I know where the FreeBSD source tree : > is? Is there some standard define like SYSDIR that contains this : > infomration? : : Simply take a look at ports that required /src or /sys to compile, eg. : lsof or fusefs-kmod: : : lsof has: FREEBSD_SYS?= /usr/src/sys : fusefs-kmod has: SRC_BASE?= /usr/src : : So neither of them use a predefined var. There's a lot more ports that use SYSDIR for /usr/src/sys :). lsof and fusefs-kmod are odd-men here. I think that most of the ports that rely on this feature do so because they include kmod.mk, for example. : > Second, I need to invoke make includes (and a few other things), with : > some slightly non-standard args. is there a stylied way to do this? : > I'd like to avoid extracting everything into myport/work/FreeBSD :) : : Not quite sure on *when* you want to run make includes and if you want : to run it for the port or for /usr/src? : : You could override the "pre-build:" target with stuff necessary pre : build :) I want it to be a port that my gcc port depends on. So, to make that port, I need to know where /usr/src for the system lives. That's only half the battle, since I don't want to "extract" it to work/freebsd-mips-headers/blah, but just do the includes target there (with a combination of MAKEOBJDIRPREFIX and DESTDIR tricks, I think). Warner ___ 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"
Best way to have a port...
... that builds part of FreeBSD? Let me back up... I'm trying to create a port for gcc and binutils that is configured for FreeBSD for a given machine. FreeBSD mips, say. binutils was relatively easy (once I ported our mips support forward). However, gcc vexes me. It requires, to build libgcc and friends, a fully populated include tree. And it wants to use /usr/local/freebsd-mips/include instead of /usr/include (which is good). However, the former doesn't exist. I'd like to create a port for it, but I'm unclear how to even start. This port should consist of all files from make includes TARGET_ARCH=mips. So, some questions: First, how do I know where the FreeBSD source tree is? Is there some standard define like SYSDIR that contains this infomration? Second, I need to invoke make includes (and a few other things), with some slightly non-standard args. is there a stylied way to do this? I'd like to avoid extracting everything into myport/work/FreeBSD :) Without solving these problems, the notion that we can use a ports compiler to build FreeBSD becomes less viable... Comments? Warner ___ 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: Is fetching source RPMs in linux ports really required?
In message: <20090605133321.ga18...@hades.panopticon> Dmitry Marakasov writes: : Hi! : : I have concerns with linux ports fetching source RPMs when : PACKAGE_BUILDING is defined. As I understand, that is done to comply : with GPL, however GPL does not strictly require mirroring sources, : and just a not on where t get them would suffice. Here's forward : of message with details. I don't think that GPLv2 section 3c applies because we've not received an section 3b offer to redistribute. Instead, the RPMs are provided under section 3a. The FSF made a big deal about this not being sufficient a while ago. I've not done a GPLv3 analysis. Warner : - Forwarded message from Dmitry Marakasov - : : Date: Thu, 4 Jun 2009 21:10:55 +0400 : From: Dmitry Marakasov : To: Boris Samorodov : Cc: ports-committ...@freebsd.org, cvs-po...@freebsd.org, : freebsd-emulat...@freebsd.org : Subject: Re: cvs commit: ports/Mk bsd.linux-apps.mk bsd.linux-rpm.mk : ports/accessibility Makefile ports/accessibility/linux-f10-atk : Makefile distinfo.i386 pkg-plist ports/archivers Makefile : ports/archivers/linux-f10-ucl Makefile distinfo.i386 ... : : * Boris Samorodov (b...@ipt.ru) wrote: : : > This is used while packaging to pet GPL which ensures that sources : > are available together with binaries. : : Is that absolutely necessary? It seems to be that GPL does not require : doing this. : : >From GPLv2: : --- : 3. You may copy and distribute the Program (or a work based on it, : under Section 2) in object code or executable form under the terms of : Sections 1 and 2 above provided that you also do one of the following: : : c) Accompany it with the information you received as to the offer to : distribute corresponding source code. (This alternative is allowed only : for noncommercial distribution and only if you received the program in : object code or executable form with such an offer, in accord with : Subsection b above.) : --- : : Looks to be our case, as we received program in object code (i386.rpm) : with an information on where to get source code. If and only if you aren't doing any modifications to the source at all. : >From GPLv3: : --- : 6. Conveying Non-Source Forms. : : d) Convey the object code by offering access from a designated place : (gratis or for a charge), and offer equivalent access to the : Corresponding Source in the same way through the same place at no : further charge. You need not require recipients to copy the : Corresponding Source along with the object code. If the place to : copy the object code is a network server, : : > the Corresponding Source may be on a different server (operated by : > you or a third party) that supports equivalent copying facilities, : > provided you maintain clear directions next to the object code : > saying where to find the Corresponding Source. : : Regardless of what server hosts the Corresponding Source, you remain : obligated to ensure that it is available for as long as needed to : satisfy these requirements. : --- : : This is even more clear. : : Thus, I believe we can comply with GPL just by providing link to source : download locations of Fedora (through pkg-message I believe). : : > This has no impact on users who use ports to install linux : > applications. : : It does if user runs tinderbox, I've just stepped into this. : Also it's inconvenient for maintainers as you need to define : PACKAGE_BUILDING for make fetch/makesum. : : Also Fedora mirror list may need cleaning: : : => libICE-1.0.4-4.fc10.src.rpm doesn't seem to exist in /tmp/distfiles/rpm/i386/fedora/10. : => Attempting to fetch from file:///distcache/rpm/i386/fedora/10/. : fetch: file:///distcache/rpm/i386/fedora/10/libICE-1.0.4-4.fc10.src.rpm: No such file or directory : => Attempting to fetch from http://archives.fedoraproject.org/pub/archive/fedora/linux/core/../releases/10/Everything/i386/os/Packages/. : fetch: http://archives.fedoraproject.org/pub/archive/fedora/linux/core/../releases/10/Everything/i386/os/Packages/libICE-1.0.4-4.fc10.src.rpm: Not Found : => Attempting to fetch from http://archives.fedoraproject.org/pub/archive/fedora/linux/core/../updates/10/i386/. : fetch: http://archives.fedoraproject.org/pub/archive/fedora/linux/core/../updates/10/i386/libICE-1.0.4-4.fc10.src.rpm: Not Found : => Attempting to fetch from http://archives.fedoraproject.org/pub/archive/fedora/linux/core/../releases/10/SRPMS/libICE-1.0.4-4.fc10.src.rpm: Not Found : => Attempting to fetch from http://archives.fedoraproject.org/pub/archive/fedora/linux/core/../updates/10/SRPMS/. : fetch: http://archives.fedoraproject.org/pub/archive/fedora/linux/core/../updates/10/SRPMS/libICE-1.0.4-4.fc10.src.rpm: Not Found : => Attempting to fetch from http://mirrors.kernel.org/fedora/core/../releases/10/Everything/i386/os/Packages/. : fetch: http://mirrors.kernel.org/fedora/core/../releases/10/Everything/i386/os/Packages/libICE-1.0.4-4.fc10.src.rpm: No
Re: cvs commit: ports/net Makefile ports/net/bwi-firmware-kmod Makefile distinfo pkg-descr pkg-plist
In message: <790a9fff0905101305l70d7809cl1ca2525729d53...@mail.gmail.com> Scot Hetzel writes: : On Sun, May 10, 2009 at 11:20 AM, wrote: : > : > : > add_pkg : > ===> Installing for bwi-firmware-kmod-3.130.20 : > ===> Generating temporary packing list : > ===> Checking if net/bwi-firmware-kmod already installed : > install -o root -g wheel -m 555 bwi_v3_ucode.ko /boot/modules : > kldxref /boot/modules : > ===> Registering installation for bwi-firmware-kmod-3.130.20 : > : > : > ===> Building package for bwi-firmware-kmod-3.130.20 : > Creating package /tmp/packages/All/bwi-firmware-kmod-3.130.20.tbz : > Registering depends:. : > Creating bzip'd tar ball in '/tmp/packages/All/bwi-firmware-kmod-3.130.20.tbz' : > Deleting bwi-firmware-kmod-3.130.20 : > : > : > === Checking filesystem state : > list of extra files and directories in / (not present before this port was installed but present after it was deinstalled) : > 33067887 4 -rw-r--r-- 1 root wheel 88 May 10 16:20 boot/modules/linker.hints : > : : This shouldn't be flaged as an mtree error. The reason that : linker.hints was left behind is due to this file is generated by : kldxref. The port/package runs kldxref during the install of the : firmware module to update the existing or create a linker.hints file, : and when the package is removed, it runs kldxref again to clean up the : linker.hints file to only contain the modules in /boot/modules. It : has no way to know if it is safe to remove this file. : : Should Kernel Modules be running kldxref in /boot/modules? I think so. In general, one needs to run it for optimal performance. : Should I change the port to have a do-install target that installs the : bwi firmware kernel module so that it doesn't run kldxref during the : install? What do other firmware ports do here? Warner ___ 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: Gxemul & FreeBSD/MIPS
In message: <[EMAIL PROTECTED]> Oleksandr Tymoshenko <[EMAIL PROTECTED]> writes: : Just to save time to somebody who's going to try it. Due to small : issue with gxemul (PCI registers values of piix controller are not : saved having been written) FreeBSD in gxemul panics after detecting : IDE devices. Apply this patch to fix it: : : http://people.freebsd.org/~gonzo/mips2/gxemul.diff I've taken the liberty of snagging the gxemul port from ports@ and adding this patch. gxemul 0.4.6.5_1 or newer will have this fix. Warner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bin/11420 [nanobsd] Build failure on RELENG_6
The following reply was made to PR ports/11420; it has been noted by GNATS.
From: "M. Warner Losh" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: bin/11420 [nanobsd] Build failure on RELENG_6
Date: Mon, 02 Jul 2007 07:47:21 -0600 (MDT)
In message: <[EMAIL PROTECTED]>
Henrik Brix Andersen <[EMAIL PROTECTED]> writes:
: On Sun, Jul 01, 2007 at 07:01:35PM -0600, M. Warner Losh wrote:
: > In message: <[EMAIL PROTECTED]>
: > Henrik Brix Andersen <[EMAIL PROTECTED]> writes:
: ...
: > : [1]: http://www.freebsd.org/cgi/query-pr.cgi?pr=114200
: >
: > This patch is incorrect.
: >
: > +.if !defined(NO_INSTALLLIB)
: >
: > should be
: >
: > +.if ${MK_INSTALLIB} != "no"
:
: Oh - thanks for catching this. I guess the same change should be done
: in lib/ncurses/ncurses/Makefile, then?
I belive so. I've CC'd ru@ to make sure.
Warner
: Here's an updated patch:
:
: --- usr.bin/lex/lib/Makefile.orig2007-07-02 01:06:20.0 +0200
: +++ usr.bin/lex/lib/Makefile 2007-07-02 10:41:47.0 +0200
: @@ -6,8 +6,10 @@
: SRCS= libmain.c libyywrap.c
: NO_PIC=
:
: +.if ${MK_INSTALLLIB} != "no"
: LINKS= ${LIBDIR}/libln.a ${LIBDIR}/libl.a
: LINKS+= ${LIBDIR}/libln.a ${LIBDIR}/libfl.a
: +.endif
:
: .if ${MK_PROFILE} != "no"
: LINKS+= ${LIBDIR}/libln_p.a ${LIBDIR}/libl_p.a
:
:
: And for good meassure - a patch for lib/ncurses/ncurses/Makefile:
:
: --- lib/ncurses/ncurses/Makefile.orig2007-07-02 10:43:17.0
+0200
: +++ lib/ncurses/ncurses/Makefile 2007-07-02 10:44:14.0 +0200
: @@ -280,7 +280,7 @@
: INCSLINKS= curses.h ${INCLUDEDIR}/ncurses.h
: .endif
:
: -.if !defined(NO_INSTALLLIB)
: +.if ${MK_INSTALLLIB} != "no"
: SYMLINKS+= libncurses${LIB_SUFFIX}.a ${LIBDIR}/libcurses${LIB_SUFFIX}.a
: SYMLINKS+= libncurses${LIB_SUFFIX}.a ${LIBDIR}/libtermcap${LIB_SUFFIX}.a
: SYMLINKS+= libncurses${LIB_SUFFIX}.a ${LIBDIR}/libtermlib${LIB_SUFFIX}.a
:
:
: --
: Henrik Brix Andersen <[EMAIL PROTECTED]>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to get a list of all kernel modules
In message: <[EMAIL PROTECTED]> Edwin Groothuis <[EMAIL PROTECTED]> writes: : On Sun, Jun 17, 2007 at 09:18:55AM +0200, [LoN]Kamikaze wrote: : > M. Warner Losh wrote: : > > In message: <[EMAIL PROTECTED]> : > > [EMAIL PROTECTED] (Mark Linimon) writes: : > > : On Sun, Jun 17, 2007 at 12:42:01AM -0600, M. Warner Losh wrote: : > > : > I'd kinda hoped there was a pseudo category that I could key off of. : > > : : > > : Kinda sounds like there should be. : > > : > > That would make grepping the info out of INDEX easy : > : > I'm with Mark here, there definitely should be one. : > : > I think it would be best to create it and send a HEADS UP to ports@ or to all : > maintainers. : : If you decide on a name for the category, I'll send-pr it and ask : the maintainer of portlint to incoperate a check for it. 'kmod' would be my first choice. But I don't care as long as I know what it is. Warner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to get a list of all kernel modules
In message: <[EMAIL PROTECTED]> [EMAIL PROTECTED] (Mark Linimon) writes: : On Sun, Jun 17, 2007 at 12:42:01AM -0600, M. Warner Losh wrote: : > I'd kinda hoped there was a pseudo category that I could key off of. : : Kinda sounds like there should be. : : Here's my list so far: : : audio/aureal-kmod : audio/emu10kx : comms/hcfmdm : comms/ixj : comms/ltmdm : comms/uticom : comms/vpb-driver : graphics/kix-kmod : graphics/plasma-kmod : misc/zaptel : multimedia/pvr250 : multimedia/pwcbsd : net/acx100 : net/ipw-firmware : net/iwi-firmware : net/ng_daphne : net/nvnet : net/p54u : palm/uppc-kmod : security/vncrypt : sysutils/cd9660_unicode : sysutils/est : sysutils/fusefs-kmod : sysutils/ipmi-kmod : x11/nvidia-driver I think you missed: multimedia/kbtv sysutils/pmap sysutils/biosfont sysutils/devcpu net/ng_car net/ng_netflow net/ipvs although some of these install a lot more than just a single driver. Warner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to get a list of all kernel modules
In message: <[EMAIL PROTECTED]> [EMAIL PROTECTED] (Mark Linimon) writes: : On Sun, Jun 17, 2007 at 12:42:01AM -0600, M. Warner Losh wrote: : > I'd kinda hoped there was a pseudo category that I could key off of. : : Kinda sounds like there should be. That would make grepping the info out of INDEX easy Warner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to get a list of all kernel modules
In message: <[EMAIL PROTECTED]> Kris Kennaway <[EMAIL PROTECTED]> writes: : On Sun, Jun 17, 2007 at 02:28:19AM -0400, Kris Kennaway wrote: : > On Sun, Jun 17, 2007 at 01:22:57AM -0500, Mark Linimon wrote: : > > On Sun, Jun 17, 2007 at 12:15:16AM -0600, M. Warner Losh wrote: : > > > I want a list of all the ports in /usr/ports that install kernel modules. : > > : > > IIRC they're all in misc/. Let me see if I can come up with a quick list. : > : > Nope, but I'm grepping for them now. : : Partial list: : : Binary file ./linux-kmod-compat-20070326.tbz matches : Binary file ./biosfont-1.1.tbz matches : Binary file ./iwi-firmware-2.4_7.tbz matches : Binary file ./ipw-firmware-1.3_8.tbz matches : Binary file ./linux-js-2.2.tbz matches : Binary file ./kqemu-kmod-1.3.0.p11.tbz matches : Binary file ./ltmdm-1.4_18.tbz matches : : This is from 6.x, and I know there are others, so a more complete grep : will be needed. Grepping for '\.ko$' does fairly well at coming up with a good list. However, there are a few interesting false positives: ./editors/emacs/pkg-plist ./editors/emacs-devel/pkg-plist ./editors/emacs20/pkg-plist ./editors/xemacs/pkg-plist ./editors/xemacs-devel/pkg-plist ./editors/xemacs-devel-mule/pkg-plist ./editors/xemacs21-mule/pkg-plist ./editors/emacs.app/pkg-plist ./korean/hlatex/pkg-plist ./korean/msdosfs/pkg-plist ./korean/pgp.language/pkg-plist ./korean/texinfo/pkg-plist All of these because there are files that I think are in korean with a .ko suffix. and there's only one in misc: ./misc/zaptel/pkg-plist which lists a bunch of .ko's installed into /usr/local/lib/zaptel that turn out to be kernel drivers, but no mention of "/boot" at all. Warner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to get a list of all kernel modules
In message: <[EMAIL PROTECTED]> Edwin Groothuis <[EMAIL PROTECTED]> writes: : On Sun, Jun 17, 2007 at 12:42:01AM -0600, M. Warner Losh wrote: : > I'd kinda hoped there was a pseudo category that I could key off of. : > pvr250 is also kinda a mess too, since I can't build it w/o a CD I : > don't have... : : Don't blame me, there are lots of ports which require distfiles : which you can't just download :-) I don't blame you. I understand the reasons for it, but it makes it harder to automatically check them. Warner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to get a list of all kernel modules
In message: <[EMAIL PROTECTED]>
"[LoN]Kamikaze" <[EMAIL PROTECTED]> writes:
: M. Warner Losh wrote:
: > In message: <[EMAIL PROTECTED]>
: > "[LoN]Kamikaze" <[EMAIL PROTECTED]> writes:
: > : [LoN]Kamikaze wrote:
: > : > M. Warner Losh wrote:
: > : >> Greetings,
: > : >>
: > : >> is there an easy way to get a list of all the ports that compile
: > : >> kernel modules? I'd like to add them to my kernel build. I did this
: > : >> once before, but I lost all information on how to do it when I lost my
: > : >> laptop's hard disk after the last bsdcan...
: > : >>
: > : >> Warner
: > : >
: > : > # find /boot/ -type f -exec pkg_info -W \{} \;
: > :
: > : Sorry about that, it takes very long. Better is:
: > :
: > : # sh -c 'for mod in `pkg_info -qaL|grep -E "^/+boot"`; { pkg_info -W
"$mod"; }
: >
: > This sounds great, except for one problem. This will tell me all the
: > modules that I've installed that are from ports. Since I've never
: > installed any from ports, this will not work for what I want. I want
: > a list of all the ports in /usr/ports that install kernel modules.
: > I'd even settle for a list of all the ports in /usr/ports that only
: > install modules.
: >
: > Something like
: > egrep -l '\.ko$' /usr/ports/*/*/pkg-plist | sed -e s=/pkg-plist//
: > might do the trick, but that blows the command line limits out of the
: > water. Replacing egrep with 'find' would need to be carefully
: > constructed to avoid false positives in any work directories I have
: > laying around. I was hoping for something a little easier to do...
: >
: > Warner
:
: I see I misunderstood, sorry about that. So how about that one:
:
: # find /usr/ports/ -type f -name pkg-plist -exec grep -El
: '[EMAIL PROTECTED]:space:]]+/boot' \{} \; | sed -E 's|^/usr/ports/||1' | sed
-E
: 's|/pkg-plist$||1'
:
: It only works with ports that have a pkg-plist file, though.
This won't quite work because there are things like:
% cat multimedia/pvr250/pkg-plist
@unexec rm %%MODULESDIR%%/cxm.ko
@unexec rm %%MODULESDIR%%/cxm_iic.ko
bin/pvr250-setchannel
I'd kinda hoped there was a pseudo category that I could key off of.
pvr250 is also kinda a mess too, since I can't build it w/o a CD I
don't have...
Warner
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to get a list of all kernel modules
In message: <[EMAIL PROTECTED]>
"[LoN]Kamikaze" <[EMAIL PROTECTED]> writes:
: [LoN]Kamikaze wrote:
: > M. Warner Losh wrote:
: >> Greetings,
: >>
: >> is there an easy way to get a list of all the ports that compile
: >> kernel modules? I'd like to add them to my kernel build. I did this
: >> once before, but I lost all information on how to do it when I lost my
: >> laptop's hard disk after the last bsdcan...
: >>
: >> Warner
: >
: > # find /boot/ -type f -exec pkg_info -W \{} \;
:
: Sorry about that, it takes very long. Better is:
:
: # sh -c 'for mod in `pkg_info -qaL|grep -E "^/+boot"`; { pkg_info -W "$mod"; }
This sounds great, except for one problem. This will tell me all the
modules that I've installed that are from ports. Since I've never
installed any from ports, this will not work for what I want. I want
a list of all the ports in /usr/ports that install kernel modules.
I'd even settle for a list of all the ports in /usr/ports that only
install modules.
Something like
egrep -l '\.ko$' /usr/ports/*/*/pkg-plist | sed -e s=/pkg-plist//
might do the trick, but that blows the command line limits out of the
water. Replacing egrep with 'find' would need to be carefully
constructed to avoid false positives in any work directories I have
laying around. I was hoping for something a little easier to do...
Warner
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How to get a list of all kernel modules
Greetings, is there an easy way to get a list of all the ports that compile kernel modules? I'd like to add them to my kernel build. I did this once before, but I lost all information on how to do it when I lost my laptop's hard disk after the last bsdcan... Warner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Uggg!
In message: <[EMAIL PROTECTED]> Kris Kennaway <[EMAIL PROTECTED]> writes: : On Sat, Jun 02, 2007 at 01:19:51AM +0200, Erwin Lansing wrote: : > On Fri, Jun 01, 2007 at 02:56:51PM -0600, M. Warner Losh wrote: : > > : > > [[ as an aside, the updating instructions for xorg should say you may : > >need to regenerate your config file, since when I used my old one : > >I got pcidata not found ]] : > > : > Snipped from UPDATING: : > : > If you plan on keeping your current /etc/X11/xorg.conf, make sure you : > change ModulePath to /usr/local/lib/xorg/modules prior to running X. : > This should be all you need to fix the pcidata error. True. I had thought my /usr/X11R6 -> /usr/local symlink would have saved me, but no dice. : As well as possible a later snippage telling you to install x11/xorg. I did have that one installed, so I got the newer stuff... until all the +CONTENTS files disappeared. :-( Still, I was really upset when the +CONTENTS stuff disappeared, but so far everything has built w/o a hassle. Only one left: ooo. Warner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Uggg!
In message: <[EMAIL PROTECTED]> Doug Barton <[EMAIL PROTECTED]> writes: : M. Warner Losh wrote: : : > I don't see the 't' option listed in the portupgrade -help output. : > What does it do? : : portmaster != portupgrade :) : : In portmaster, the -t option means to thoroughly recurse dependencies : (using all-depends-list instead of the union of build/run-depends-list). Ah, ok. I'm just a fount of confusion today. Warner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Uggg!
In message: <[EMAIL PROTECTED]> Doug Barton <[EMAIL PROTECTED]> writes: : Warner Losh wrote: : >> Best solution is to back up /var/db/pkg if it is in danger of deletion : >> by a wanton admin :) : > : > The ONLY data corruption that I saw when my laptop died was *ALL* of : > the +CONTENTS files going away. It seems to have died during the : > updating of the meta-data for the dvdauthor port. Why all the files : > of unreleated packages would disapper is a mystery to me, unless : > mergemaster, or one of the pkg tools, deleted them all, and then : > wanted to rewrite them and I got screwed between these two steps. : : I think you're thinking of portmaster, mergemaster doesn't touch ports : stuff. What portmaster does when it updates +CONTENTS files is to : update a temp copy first, then move the updated file into place after : it's done. Not sure what portupgrade does. Yea, forget I said mergemaster. It was portupgrade. : In terms of easily recreating them, I can't think of a way to do that : reliably other than to build the ports again. portmaster relies : heavily on the data in +CONTENTS, and it couldn't even rebuild your : ports in place without them since it wouldn't be able to find the ORIGIN. rm -rf /var/db/pkg/* /usr/local/* /usr/X11R6/* is somewhat liberating... That's what I opted for... However, I've not yet tried to rebuild openoffice. Firefox and X11 worked. [[ as an aside, the updating instructions for xorg should say you may need to regenerate your config file, since when I used my old one I got pcidata not found ]] : What you could do with portmaster is to pick a high level leaf port : with a lot of dependencies (something like firefox) and do 'portmaster : -aft /usr/ports/www/firefox' (make sure you specify the directory in : /usr/ports, not the pkg directory). I don't see the 't' option listed in the portupgrade -help output. What does it do? Warner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: libusb failed
In message: <[EMAIL PROTECTED]> Yuri Pankov <[EMAIL PROTECTED]> writes: : On Thu, May 31, 2007 at 01:30:40AM -0600, M. Warner Losh wrote: : > Maybe this is old news, but libusb failed for me: : > : > (cd .libs && rm -f libusb.la && ln -s ../libusb.la libusb.la) : > if /bin/sh /usr/local/bin/libtool --mode=compile c++ -DHAVE_CONFIG_H-I. -O2 -fno-strict-aliasing -pipe -MT usbpp.lo -MD -MP -MF ".deps/usbpp.Tpo" -c -o usbpp.lo usbpp.cpp; then mv -f ".deps/usbpp.Tpo" ".deps/usbpp.Plo"; else rm -f ".deps/usbpp.Tpo"; exit 1; fi : > c++ -DHAVE_CONFIG_H -I. -O2 -fno-strict-aliasing -pipe -MT usbpp.lo -MD -MP -MF .deps/usbpp.Tpo -c usbpp.cpp -fPIC -DPIC -o .libs/usbpp.o : > c++ -DHAVE_CONFIG_H -I. -O2 -fno-strict-aliasing -pipe -MT usbpp.lo -MD -MP -MF .deps/usbpp.Tpo -c usbpp.cpp -o usbpp.o >/dev/null 2>&1 : > /bin/sh /usr/local/bin/libtool --mode=link c++ -O2 -fno-strict-aliasing -pipe-o libusbpp.la -rpath /usr/local/lib -version-info 8:4:4 -release 0.1 -export-dynamic -lusb usbpp.lo : > c++ -shared -nostdlib /usr/lib/crti.o /usr/lib/crtbeginS.o .libs/usbpp.o -Wl,--rpath -Wl,/tmp/ports/devel/libusb/work/libusb-0.1.12/.libs -Wl,--rpath -Wl,/usr/local/lib /tmp/ports/devel/libusb/work/libusb-0.1.12/.libs/libusb.so -L/usr/lib -lstdc++ -lm -lgcc_pic /usr/lib/crtendS.o /usr/lib/crtn.o -Wl,-soname -Wl,libusbpp-0.1.so.8 -o .libs/libusbpp-0.1.so.8 : > /usr/bin/ld: cannot find -lgcc_pic : > *** Error code 1 : > : > Stop in /tmp/ports/devel/libusb/work/libusb-0.1.12. : > *** Error code 1 : > : > Stop in /tmp/ports/devel/libusb/work/libusb-0.1.12. : > *** Error code 1 : > : > Stop in /tmp/ports/devel/libusb/work/libusb-0.1.12. : > *** Error code 1 : > : > Stop in /tmp/ports/devel/libusb. : > ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.60394.37 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=libusb-0.1.12 UPGRADE_PORT_VER=0.1.12 make : > ** Fix the problem and try again. : > : > Any ideas? : > : > Warner : : Try reinstalling libtool. The libtool I had was the most current. Yet, when I removed the symlink I'd kludged in and rebuild/installed libtool, libusb now builds. Thanks for the tip. Warner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
libusb failed
Maybe this is old news, but libusb failed for me: (cd .libs && rm -f libusb.la && ln -s ../libusb.la libusb.la) if /bin/sh /usr/local/bin/libtool --mode=compile c++ -DHAVE_CONFIG_H-I. -O2 -fno-strict-aliasing -pipe -MT usbpp.lo -MD -MP -MF ".deps/usbpp.Tpo" -c -o usbpp.lo usbpp.cpp; then mv -f ".deps/usbpp.Tpo" ".deps/usbpp.Plo"; else rm -f ".deps/usbpp.Tpo"; exit 1; fi c++ -DHAVE_CONFIG_H -I. -O2 -fno-strict-aliasing -pipe -MT usbpp.lo -MD -MP -MF .deps/usbpp.Tpo -c usbpp.cpp -fPIC -DPIC -o .libs/usbpp.o c++ -DHAVE_CONFIG_H -I. -O2 -fno-strict-aliasing -pipe -MT usbpp.lo -MD -MP -MF .deps/usbpp.Tpo -c usbpp.cpp -o usbpp.o >/dev/null 2>&1 /bin/sh /usr/local/bin/libtool --mode=link c++ -O2 -fno-strict-aliasing -pipe -o libusbpp.la -rpath /usr/local/lib -version-info 8:4:4 -release 0.1 -export-dynamic -lusb usbpp.lo c++ -shared -nostdlib /usr/lib/crti.o /usr/lib/crtbeginS.o .libs/usbpp.o -Wl,--rpath -Wl,/tmp/ports/devel/libusb/work/libusb-0.1.12/.libs -Wl,--rpath -Wl,/usr/local/lib /tmp/ports/devel/libusb/work/libusb-0.1.12/.libs/libusb.so -L/usr/lib -lstdc++ -lm -lgcc_pic /usr/lib/crtendS.o /usr/lib/crtn.o -Wl,-soname -Wl,libusbpp-0.1.so.8 -o .libs/libusbpp-0.1.so.8 /usr/bin/ld: cannot find -lgcc_pic *** Error code 1 Stop in /tmp/ports/devel/libusb/work/libusb-0.1.12. *** Error code 1 Stop in /tmp/ports/devel/libusb/work/libusb-0.1.12. *** Error code 1 Stop in /tmp/ports/devel/libusb/work/libusb-0.1.12. *** Error code 1 Stop in /tmp/ports/devel/libusb. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.60394.37 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=libusb-0.1.12 UPGRADE_PORT_VER=0.1.12 make ** Fix the problem and try again. Any ideas? Warner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
My problem
I think my problem was caused by a stale ruby18. When I did a make delete-old-libs, that program would no longer run due to a missing library. Rebuilding it, and then rebuilding portupgrade-devel was the ticket. You might want to suggest in the UPDATING file that people make sure their base system is up-to-date, and to update ruby as well after crossing the gcc 4.2/symbol versioning rubicon... Warner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
upgrade
Greetings. I set out on the great 7.2 upgrade, but didn't get very far: sudo portupgrade -f -o ports-mgmt/portupgrade-devel portupgrade ... ===> Cleaning for portupgrade-devel-2.3.0_5 ---> Cleaning out obsolete shared libraries FFaattaall eeoorr ''Thread is not system scope. Thread is not system scope. '' aatt lliinnee 331166 iinn ffiillee /hp/imp/p4/arm/src/lib/libpthread/thread/thr_sig.c/hp/imp/p4/arm/src/lib/libpthread/thread/thr_sig.c ((eennoo == 22)) FFaattaall eeoorr ''Thread is not system scope. Thread is not system scope. '' aatt lliinnee 331166 iinn ffiillee /hp/imp/p4/arm/src/lib/libpthread/thread/thr_sig.c/hp/imp/p4/arm/src/lib/libpthread/thread/thr_sig.c ((eennoo == 22)) /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:498:in `__system': Command failed [exit code 0]: /usr/local/sbin/pkgdb -aFOQ (CommandFailedError) from /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:521:in `__sudo' from /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:527:in `xsystem!' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:865:in `autofix!' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:861:in `autofix' from /usr/local/sbin/portupgrade:507:in `main' from /usr/local/sbin/portupgrade:769:in `call' from /usr/local/sbin/portupgrade:769:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:785:in `initialize' from /usr/local/sbin/portupgrade:220:in `new' from /usr/local/sbin/portupgrade:220:in `main' from /usr/local/sbin/portupgrade:2084 and now any attempt to run portupgrade gives: FFatal error 'Thread is not system scope. ' at line 316 in file /hp/imp/p4/arm/src/lib/libpthread/thread/thr_sig.c (errno = 2) atal error 'Thread is not system scope. ' at line 316 in file /hp/imp/p4/arm/src/lib/libpthread/thread/thr_sig.c (errno = 2) Abort (core dumped) I suspect it is threads related. The full script of what I did is at http://people.freebsd.org/~imp/xorg-script. Ideas? Warner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
firefox + cups problem
With my old laptop, a FreeBSD/i386 box running current, I was able to print to my cups printers w/o a problem with firefox. That laptop died a horrible death. So I bought a amd64 laptop and am running FreeBSD/amd64. Every time I print now in firefox, firefox dies a horrible death. I just did a portupgrade -a, and that hasn't solved the issue, so I thought I'd ask here if people have seen this. Warner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
i386 packages on amd64
[[ please redirect this if this isn't the right place ]] I'd like to install OpenOffice on my amd64 box. All attempts that I've made to compile it have failed. Usually due to java compilation issues. So, I thought I'd install the i386 binaries from the package cluster snapshots on the amd64 box. Before I did this, however, I thought I'd ask to see if there might be any gotchas here. Warner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
