Re: port building in CURRENT (including r247839) BROKEN
On Tue, Mar 5, 2013 at 1:10 PM, Hartmann, O. wrote: > On all FreeBSD boxes with > FreeBSD 10.0-CURRENT #1 r247839: Tue Mar 5 12:28:12 CET 2013/amd64 the > build of ports - or updating/upgrading ports is BROKEN! > > Every port which is about to be updated fails with > > [...] > *** [do-extract] Signal 13 > > This is common on ALL CURRENT systems so I consider this a BREAKAGE. > > The problem is painful due to the fact that several kernel modules need, > accordung to the entry 20130304: in /usr/src/UPDATING an update. > > devel/dbus isn't starting anymore on ALL systems, I couldn't figure out > why. So X11 doesn't start either. And I can not rebuild those ports to > accomplish what's suggested/required in UPDATING. > > Regards, > Oliver There's a few posts in -current about the same thing, and it does not appear to be limited to ports. Just going by the complaints, I would guess that something recently committed subtly broke pipes (in certain circumstances). Signal 13 is defined as "write to a pipe with no reader", so feel free to speculate or debug. -- Daniel Nebdal ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: port building in CURRENT (including r247839) BROKEN
On Wed, Mar 6, 2013 at 11:11 AM, Daniel Nebdal wrote: > On Tue, Mar 5, 2013 at 1:10 PM, Hartmann, O. > wrote: >> On all FreeBSD boxes with >> FreeBSD 10.0-CURRENT #1 r247839: Tue Mar 5 12:28:12 CET 2013/amd64 the >> build of ports - or updating/upgrading ports is BROKEN! >> >> Every port which is about to be updated fails with >> >> [...] >> *** [do-extract] Signal 13 >> >> This is common on ALL CURRENT systems so I consider this a BREAKAGE. >> >> The problem is painful due to the fact that several kernel modules need, >> accordung to the entry 20130304: in /usr/src/UPDATING an update. >> >> devel/dbus isn't starting anymore on ALL systems, I couldn't figure out >> why. So X11 doesn't start either. And I can not rebuild those ports to >> accomplish what's suggested/required in UPDATING. >> >> Regards, >> Oliver > > There's a few posts in -current about the same thing, and it does not > appear to be limited to ports. > > Just going by the complaints, I would guess that something recently > committed subtly broke pipes (in certain circumstances). Signal 13 is > defined as "write to a pipe with no reader", so feel free to speculate > or debug. > > -- > Daniel Nebdal Ha, I see you were writing a sensible post to -current while I typed that - never mind me, then. :) -- Daniel Nebdal ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Dropbox on FreeBSD
W dniu 2013-03-05 20:20, Wojciech Puchar pisze: > got into webpage, and it looks like detailless advert just like plenty > of others. > > Found that it "simplify sharing", get quite bored after trying to find > out WHAT and HOW it actually provides. I'm using Dropbox with boxcryptor (files gets encrypted on device and then sent to the Dropbox cloud) - it's nice synchronization tool between my home pc, work pc, netbook and android smartphone. Also auto upload of photos from the phone and easy sharing of files with non-tech people is a neat feature. I'm not saying it's the best of them all, but it does it job good and it's quite popular. I'd love to see FreeBSD client of it. -- best regards, Lukasz Wasikowski ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ devel/make++| 2.0 | 2.0.98.3 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt If wish to stop receiving portscout reminders, please contact portsc...@portscout.freebsd.org Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[HEADSUP] new USES in ports
Hi, The ports now support a new Macro (porters only): USES You may use it that way: USES= pathfix feature1 feature2:arguments it will load the following files (just at the begining of bsd.port.post.mk): Mk/Uses/pathfix.mk Mk/Uses/feature1.mk Mk/Uses/feature2.mk aka load features on demand. a feature2_ARGS variable will be created and it will contain "arguments" The first feature available is: pathfix pathfix is a copy of the bsd.gnome.mk "gnomehack" so that porters do not need to include the full bsd.gnome.mk each time they need it. Lots more to come regards, Bapt pgpTKRgymHIC3.pgp Description: PGP signature
[HEADS UP] FreeBSD Ports tree has been tagged with RELEASE_7_EOL
The FreeBSD Ports Management Team wishes to remind users that February 28 was the end of support for the Ports Collection for both FreeBSD 7.4 RELEASE and the FreeBSD 7.x STABLE branch. Neither the infrastructure nor individual ports are guaranteed to work on these FreeBSD versions after that date. A tag has be created for users who cannot upgrade for some reason, at which time these users are advised to stop tracking the latest ports repository and use the RELEASE_7_EOL tag instead. While many people still use RELENG_7, it is at the end of its development cycle. The Ports Management team has set the following policies with regard to EOL/EOS of this branch and would like to let developers know that: - We do not require committers/maintainers to support 7.x, although ports will need to be marked as BROKEN/IGNORE if they do not build/run. - Port maintainers are encouraged to accept patches from the community that allow their ports to build and run on 7.x. However, since running on 7.x is no longer a requirement, maintainers may use their discretion in cases where a proposed patch would be disruptive to other supported FreeBSD branches, or would unreasonably impede ongoing maintenance of the port. - We strongly encourage all users and developers to migrate to the FreeBSD 8.x or 9.x branch, both of which is a stable and mature platform, and are now the reference branches for the ports collection. Pleae refer to the FreeBSD Security Officer list of unsupported branches http://www.freebsd.org/security/#unsup ___ 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"
xbmc and poudriere compile error
Hi, I have problems compiling xbmc with poudriere-devel. Logfile says: DVDAudioCodecFFmpeg.cpp: In member function 'virtual int CDVDAudioCodecFFmpeg::Decode(BYTE*, int)': DVDAudioCodecFFmpeg.cpp:163: error: 'struct AVFrame' has no member named 'nb_samples' DVDAudioCodecFFmpeg.cpp: In member function 'void CDVDAudioCodecFFmpeg::ConvertToFloat()': DVDAudioCodecFFmpeg.cpp:208: error: 'struct AVFrame' has no member named 'nb_samples' gmake[1]: *** [DVDAudioCodecFFmpeg.o] Error 1 gmake: *** [xbmc/cores/dvdplayer/DVDCodecs/Audio/Audio.a] Error 2 *** [do-build] Error code 1 I tried several options, EXTERNAL_FFMPEG, NONFREE and LIBBLURAY on and off, but no changes. I also tried compiling without CCACHE Poudriere uses a FreeBSD 9.1-RELEASE AMD64 Jail. Any help is appreciated, thanks in advance. kind regards Wolfgang Riegler ___ 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"
geda-
Installing geda-symcheck-1.4.3_4,1...pkg: geda-symcheck-1.4.3_4,1 conflicts with geda-1.8.1,1 (installs files into the same place). Problematic file: /usr/local/man/man1/gsymcheck.1.gz *** [fake-pkg] Error code 70 Stop in /usr/ports/cad/geda-symcheck. and also such in geda-utils geda-attrib geda gathered, and some additional components aren't present, it while so is necessary? -- Я є я! І мене не змінити ___ 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: portdowngrade(CVS) deprecated -> alternative for portsnap(8) usage
> > http://forums.freebsd.org/showthread.php?p=203241 > > > > Will it be transformed to checkout via SVN, only origins we need, or will > > it be dumped from ports tree as obsolete. > > Thanks. > > > > Hey, > > I rewrote it in sh, quite simply because I thought that c++ was insane > for such simple code. > > I'm afraid it doesn't quite have the same behaviour, but it's still > very easy to use. > > Please let me know if there's something you desperately miss about the > old version. > > Chris > Thanks for your effort! # portdowngrade audio/oss Listed all revisions # portdowngrade audio/oss r300895 I've picked one from the past However: # portsnap fetch update Is blind to this change and fails to update it back, to it's latest version portdowngrade should also alter/update portsnap's DB Domagoj Smolčić ___ 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: portdowngrade(CVS) deprecated -> alternative for portsnap(8) usage
On Wed, Mar 6, 2013 at 11:15 AM, wrote: > > > http://forums.freebsd.org/showthread.php?p=203241 > > > > > > Will it be transformed to checkout via SVN, only origins we need, or > will > > > it be dumped from ports tree as obsolete. > > > Thanks. > > > > > > > Hey, > > > > I rewrote it in sh, quite simply because I thought that c++ was insane > > for such simple code. > > > > I'm afraid it doesn't quite have the same behaviour, but it's still > > very easy to use. > > > > Please let me know if there's something you desperately miss about the > > old version. > > > > Chris > > > > > Thanks for your effort! > > # portdowngrade audio/oss > Listed all revisions > # portdowngrade audio/oss r300895 > I've picked one from the past > > However: > # portsnap fetch update > Is blind to this change and fails to update it back, to it's latest > version > > portdowngrade should also alter/update portsnap's DB > > > Domagoj Smolčić Portdowngrade always warned that portsnap would always overwrite any altering of the origin, which I believe is still the best path. If anything a warning should be displayed, if not already. -jgh -- Jason Helfman | FreeBSD Committer j...@freebsd.org | http://people.freebsd.org/~jgh | The Power to Serve ___ 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: portdowngrade(CVS) deprecated -> alternative for portsnap(8) usage
On 6 Mar 2013 19:15, wrote: > > > > http://forums.freebsd.org/showthread.php?p=203241 > > > > > > Will it be transformed to checkout via SVN, only origins we need, or will > > > it be dumped from ports tree as obsolete. > > > Thanks. > > > > > > > Hey, > > > > I rewrote it in sh, quite simply because I thought that c++ was insane > > for such simple code. > > > > I'm afraid it doesn't quite have the same behaviour, but it's still > > very easy to use. > > > > Please let me know if there's something you desperately miss about the > > old version. > > > > Chris > > > > > Thanks for your effort! > > # portdowngrade audio/oss > Listed all revisions > # portdowngrade audio/oss r300895 > I've picked one from the past > > However: > # portsnap fetch update > Is blind to this change and fails to update it back, to it's latest version > > portdowngrade should also alter/update portsnap's DB Portdowngrade now simply checks out the port to your current directory; if you run it in ~, you simply cd $portname. I wouldn't recommend the old behaviour of downgrading in place like that; it significantly complicates many things, including svn conflicts and portsnap update maybe overwriting it, maybe not. I view it as a tool for testing older versions/reverting until a fix is issued. Chris ___ 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: Dropbox on FreeBSD
Something must have happened...its like at the top of page 4 in "popular" for me. But, I've thrown some more votes on it. In the meantime...I'm running a Linux VM in VirtualBox on my FreeBSD machine, serving it out using NFS from the VM and mounting it in FreeBSD (which is what raises the issue of mountlate being too agressive on dealing with the NFS mountmountlate runs a couple of steps after mountcritremote, so that's way too early to late mount it. and using bg, mountlate will do another bg mountresulting in double bg NFS mounts.) Though I've been meaning to take a look at owncloud. - Original Message - > There is a votebox on this question on the dropbox site. The > petition to add > FreeBSD support to dropbox is in second place on the "most popular" > list. I > find that really encouraging. > > The petition is actually very close to overtaking the most popular > suggestion (adding support for languages other than English.) > > For anyone who would run Dropbox on BSD if it were natively > supported, > voting for this initiative may be the best way to encourage them to > add such > support. > > https://www.dropbox.com/votebox/186/add-support-for-freebsd > > Thanks, > Erik > > > Lawrence ___ 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: portdowngrade(CVS) deprecated -> alternative for portsnap(8) usage
Doesn't the old advice of adding, something like REFUSE audio/oss to /etc/portsnap.conf still work? - Original Message - > On Wed, Mar 6, 2013 at 11:15 AM, wrote: > > > > > http://forums.freebsd.org/showthread.php?p=203241 > > > > > > > > Will it be transformed to checkout via SVN, only origins we > > > > need, or > > will > > > > it be dumped from ports tree as obsolete. > > > > Thanks. > > > > > > > > > > Hey, > > > > > > I rewrote it in sh, quite simply because I thought that c++ was > > > insane > > > for such simple code. > > > > > > I'm afraid it doesn't quite have the same behaviour, but it's > > > still > > > very easy to use. > > > > > > Please let me know if there's something you desperately miss > > > about the > > > old version. > > > > > > Chris > > > > > > > > > Thanks for your effort! > > > > # portdowngrade audio/oss > > Listed all revisions > > # portdowngrade audio/oss r300895 > > I've picked one from the past > > > > However: > > # portsnap fetch update > > Is blind to this change and fails to update it back, to it's > > latest > > version > > > > portdowngrade should also alter/update portsnap's DB > > > > > > Domagoj Smolčić > > > Portdowngrade always warned that portsnap would always overwrite any > altering of the origin, which I believe is still the best path. If > anything > a warning should be displayed, if not already. > > -jgh > -- Who: Lawrence K. Chen, P.Eng. - W0LKC - Senior Unix Systems Administrator For: Enterprise Server Technologies (EST) -- & SafeZone Ally Snail: Computing and Telecommunications Services (CTS) Kansas State University, 109 East Stadium, Manhattan, KS 66506-3102 Phone: (785) 532-4916 - Fax: (785) 532-3515 - Email: lkc...@ksu.edu Web: http://www-personal.ksu.edu/~lkchen - Where: 11 Hale Library ___ 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: portdowngrade(CVS) deprecated -> alternative for portsnap(8) usage
On 6 March 2013 21:32, Lawrence K. Chen, P.Eng. wrote: > Doesn't the old advice of adding, something like > > REFUSE audio/oss > > to /etc/portsnap.conf still work? I hope I haven't upset anyone with the change in behaviour, but I need to reiterate that portdowngrade no longer touches the ports tree-- it simply provides a port skeleton in the current directory. Therefore, this is no longer a problem. Chris ___ 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"
regression: lang/gcc47, gcc48 on amd64: configure: error: cannot compute suffix of object files: cannot compile
Hi Gerald amd64 r246552 with clang root@zzz:~ # pkg version -vX gcc-4.\*2013 gcc-4.7.3.20130216 < needs updating (port has 4.7.3.20130302) gcc-4.8.0.20130210 < needs updating (port has 4.8.0.20130303) root@zzz:~ # Identical error for both ports: checking for x86_64-portbld-freebsd10.0-gcc... /usr/ports/lang/gcc48/work/build/./gcc/xgcc -B/usr/ports/lang/gcc48/work/build/./gcc/ -B/usr/local/x86_64-portbld-freebsd10.0/bin/ -B/usr/local/x86_64-portbld-freebsd10.0/lib/ -isystem /usr/local/x86_64-portbld-freebsd10.0/include -isystem /usr/local/x86_64-portbld-freebsd10.0/sys-include checking for suffix of object files... configure: error: in `/usr/ports/lang/gcc48/work/build/x86_64-portbld-freebsd10.0/libgcc': configure: error: cannot compute suffix of object files: cannot compile See `config.log' for more details. gmake[2]: *** [configure-stage1-target-libgcc] Error 1 checking for x86_64-portbld-freebsd10.0-gcc... /usr/ports/lang/gcc47/work/build/./gcc/xgcc -B/usr/ports/lang/gcc47/work/build/./gcc/ -B/usr/local/x86_64-portbld-freebsd10.0/bin/ -B/usr/local/x86_64-portbld-freebsd10.0/lib/ -isystem /usr/local/x86_64-portbld-freebsd10.0/include -isystem /usr/local/x86_64-portbld-freebsd10.0/sys-include checking for suffix of object files... configure: error: in `/usr/ports/lang/gcc47/work/build/x86_64-portbld-freebsd10.0/libgcc': configure: error: cannot compute suffix of object files: cannot compile See `config.log' for more details. gmake[2]: *** [configure-stage1-target-libgcc] Error 1 Shall I open a GCC PR? Anton ___ 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: regression: lang/gcc47, gcc48 on amd64: configure: error: cannot compute suffix of object files: cannot compile
On Wed, 6 Mar 2013, Anton Shterenlikht wrote: > Hi Gerald > > amd64 r246552 with clang clang may be related. Can you look into what happens here? My tests (with a full build) definitely have succeeded, and they have actually used clang as cc on FreeBSD 10. Is this specific to amd64 for you and works on i386, say? > Shall I open a GCC PR? No, unless it looks like a general issue. So far my guess is that it may be something in your environment. Gerald ___ 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: portdowngrade(CVS) deprecated -> alternative for portsnap(8) usage
- Original Message - > On 6 March 2013 21:32, Lawrence K. Chen, P.Eng. > wrote: > > Doesn't the old advice of adding, something like > > > > REFUSE audio/oss > > > > to /etc/portsnap.conf still work? > > I hope I haven't upset anyone with the change in behaviour, but I > need > to reiterate that portdowngrade no longer touches the ports tree-- it > simply provides a port skeleton in the current directory. > > Therefore, this is no longer a problem. > > Chris > Except I don't know of another way to downgrade a port to work with other portsperhaps there's a way in portmaster.rc that I haven't stumbled upon yet. I know I had something in pkgtools.conf at one time to prevent virtualbox from upgrading (has istgt been updated to work with the current virtualbox yet? Have since removed istgt) Forget what the other time that I used portdowngradesomething to do with X11 I think, which was resolved by rebuilding with "WITH_NEW_XORG=YES" in my /etc/make.conf. OTOH, there are parts of my ports tree that I have to remember to 'update' after a 'portsnap update'like www/chromium Lawrence ___ 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: Dropbox on FreeBSD
Dropbox is a good service. You put files in a folder and it automatically synchs them across multiple devices. someone else service? not mine - i mean dropbox server installed by me? just one another way to control people. No thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: regression: lang/gcc47, gcc48 on amd64: configure: error: cannot compute suffix of object files: cannot compile
From bf1...@googlemail.com Wed Mar 6 23:04:14 2013 > > checking for x86_64-portbld-freebsd10.0-gcc... /usr/ports/lang/gcc48/work/build/./gcc/xgcc -B/usr/ports/lang/gcc48/work/build/./gcc/ -B/usr/local/x86_64-portbld-freebsd10.0/bin/ -B/usr/local/x86_64-portbld-freebsd10.0/lib/ -isystem /usr/local/x86_64-portbld-freebsd10.0/include -isystem /usr/local/x86_64-portbld-freebsd10.0/sys-include > checking for suffix of object files... configure: error: in `/usr/ports/lang/gcc48/work/build/x86_64-portbld-freebsd10.0/libgcc': > configure: error: cannot compute suffix of object files: cannot compile > See `config.log' for more details. > gmake[2]: *** [configure-stage1-target-libgcc] Error 1 > > > checking for x86_64-portbld-freebsd10.0-gcc... /usr/ports/lang/gcc47/work/build/./gcc/xgcc -B/usr/ports/lang/gcc47/work/build/./gcc/ -B/usr/local/x86_64-portbld-freebsd10.0/bin/ -B/usr/local/x86_64-portbld-freebsd10.0/lib/ -isystem /usr/local/x86_64-portbld-freebsd10.0/include -isystem /usr/local/x86_64-portbld-freebsd10.0/sys-include > checking for suffix of object files... configure: error: in `/usr/ports/lang/gcc47/work/build/x86_64-portbld-freebsd10.0/libgcc': > configure: error: cannot compute suffix of object files: cannot compile > See `config.log' for more details. > gmake[2]: *** [configure-stage1-target-libgcc] Error 1 > > Shall I open a GCC PR? > Not without learning more first. I had to comment out the 3 last lines: # cat /etc/make.conf SENDMAIL_CFLAGS+= -I/usr/local/include -DSASL=2 SENDMAIL_LDFLAGS+= -L/usr/local/lib SENDMAIL_LDADD+=-lsasl2 WITH_PKGNG=yes PERL_VERSION=5.16.2 #CMAKE_ARGS+=-DCMAKE_COLOR_MAKEFILE=off #CFLAGS+= -fno-color-diagnostics #CXXFLAGS+= -fno-color-diagnostics to make gcc-4.7 build: ===>>> Upgrade of gcc-4.7.3.20130216 to gcc-4.7.3.20130302 complete I'm checking gcc-4.8 now. The irony is that I added those lines to have clearer diagnostics of failures with sript(1). Thanks Anton ___ 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: Dropbox on FreeBSD
On 3/6/2013 6:57 PM, Wojciech Puchar wrote: >> Dropbox is a good service. You put files in a folder and it >> automatically synchs them across multiple devices. > > someone else service? not mine - i mean dropbox server installed by me? > > just one another way to control people. > > Control people? How do they "control people"? ___ 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: geda-
2013-03-06 19:56, Михаил Рэверс skrev: Installing geda-symcheck-1.4.3_4,1...pkg: geda-symcheck-1.4.3_4,1 conflicts with geda-1.8.1,1 (installs files into the same place). Problematic file: /usr/local/man/man1/gsymcheck.1.gz *** [fake-pkg] Error code 70 Stop in /usr/ports/cad/geda-symcheck. and also such in geda-utils geda-attrib geda gathered, and some additional components aren't present, it while so is necessary? You can use kicad if you don't get geda working. ___ 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: regression: lang/gcc47, gcc48 on amd64: configure: error: cannot compute suffix of object files: cannot compile
From bf1...@googlemail.com Wed Mar 6 23:04:14 2013 > > checking for x86_64-portbld-freebsd10.0-gcc... /usr/ports/lang/gcc48/work/build/./gcc/xgcc -B/usr/ports/lang/gcc48/work/build/./gcc/ -B/usr/local/x86_64-portbld-freebsd10.0/bin/ -B/usr/local/x86_64-portbld-freebsd10.0/lib/ -isystem /usr/local/x86_64-portbld-freebsd10.0/include -isystem /usr/local/x86_64-portbld-freebsd10.0/sys-include > checking for suffix of object files... configure: error: in `/usr/ports/lang/gcc48/work/build/x86_64-portbld-freebsd10.0/libgcc': > configure: error: cannot compute suffix of object files: cannot compile > See `config.log' for more details. > gmake[2]: *** [configure-stage1-target-libgcc] Error 1 > > > checking for x86_64-portbld-freebsd10.0-gcc... /usr/ports/lang/gcc47/work/build/./gcc/xgcc -B/usr/ports/lang/gcc47/work/build/./gcc/ -B/usr/local/x86_64-portbld-freebsd10.0/bin/ -B/usr/local/x86_64-portbld-freebsd10.0/lib/ -isystem /usr/local/x86_64-portbld-freebsd10.0/include -isystem /usr/local/x86_64-portbld-freebsd10.0/sys-include > checking for suffix of object files... configure: error: in `/usr/ports/lang/gcc47/work/build/x86_64-portbld-freebsd10.0/libgcc': > configure: error: cannot compute suffix of object files: cannot compile > See `config.log' for more details. > gmake[2]: *** [configure-stage1-target-libgcc] Error 1 > > Shall I open a GCC PR? > Not without learning more first. yep: ===>>> Upgrade of gcc-4.8.0.20130210 to gcc-4.8.0.20130303 complete So, are these options in /etc/make.conf harmful: #CMAKE_ARGS+=-DCMAKE_COLOR_MAKEFILE=off #CFLAGS+= -fno-color-diagnostics #CXXFLAGS+= -fno-color-diagnostics Thanks Anton ___ 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"
