ports include /etc/src.conf? i.e. graphics/libfpx
Setting only base system source compiler optins in /etc/src.conf, for instance # CXXFLAGS+= -stdlib=libc++ CXXFLAGS+= -std=c++11 which do NOT appear in /etc/make.conf, make building port grahpics/libfpx complaining about unrecognized compiler options. As far a sI know, /etc/src.conf is ONLY for building the source tree of the operating system and make.conf is supposed to contain all stuff necessary for compiling both world and ports, but /etc/src.conf is world only. Am I wrong? Oliver ===> libfpx-1.3.1.1 depends on file: /usr/local/sbin/pkg - found ===> Extracting for libfpx-1.3.1.1 => SHA256 Checksum OK for libfpx-1.3.1-1.tar.xz. ===> Patching for libfpx-1.3.1.1 ===> Applying FreeBSD patches for libfpx-1.3.1.1 /usr/bin/sed -i '' -e '/^#include "fpxlib-config.h"/d' /usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/basics/filename.cpp /usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/oless/h/owchar.h /usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/ole/gen_guid.cpp /usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/fpxlib.h ===> Configuring for libfpx-1.3.1.1 ===> FreeBSD 10 autotools fix applied to /usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/configure ===> FreeBSD 10 autotools fix applied to /usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/aclocal.m4 ===> FreeBSD 10 autotools fix applied to /usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/m4/libtool.m4 ===> Building for libfpx-1.3.1.1 Warning: Object directory not changed from original /usr/ports/graphics/libfpx/work/libfpx-1.3.1-1 g++ -O2 -pipe -march=native -DHAVE_WCHAR_H -DHAVE_DLFCN_H -DHAVE_SYS_TIME_H -DHAVE_SYS_PARAM_H -DHAVE_SYS_MOUNT_H -O3 -pipe -march=native -fstack-protector -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wpointer-arith -Wno-uninitialized -fno-rtti -fno-exceptions -fno-strict-aliasing -DHAVE_WCHAR_H -DHAVE_DLFCN_H -DHAVE_SYS_TIME_H -DHAVE_SYS_PARAM_H -DHAVE_SYS_MOUNT_H -I/usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/oless/h -I/usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/jpeg -I/usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/ole -I/usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/basics -I/usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/ri_image -I/usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/oless -I/usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/fpx -I/usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/. -I/usr/local/include -D_UNIX -stdlib=libc++ -std=c++11 -c /usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/basics/geometry.cpp -o geometry.o cc1plus: error: unrecognized command line option "-stdlib=libc++" cc1plus: error: unrecognized command line option "-std=c++11" *** [geometry.o] Error code 1 Stop in /usr/ports/graphics/libfpx/work/libfpx-1.3.1-1. *** [do-build] Error code 1 Stop in /usr/ports/graphics/libfpx. signature.asc Description: OpenPGP digital signature
Re: 7+ days of dogfood
From s...@troutmask.apl.washington.edu Wed Feb 13 03:40:53 2013 On Wed, Feb 13, 2013 at 02:15:08AM +, b.f. wrote: > On 2/13/13, Steve Kargl wrote: > > On Wed, Feb 13, 2013 at 12:18:29AM +, b.f. wrote: > >> ># cat /etc/make.conf|grep FFLAGS > >> >FFLAGS = -O2 -pipe -march=native -mtune=native > >> > >> Please do _not_ assign flags unconditionally in make.conf. > > > > FFLAGS is for compiling Fortran. I'm one of the people who > > has spent years working/patching gfortran. I think I might > > have a better understanding of what options to use with > > gfortran than most people. > > > > I know you have, but you are giving advice that is liable to be abused > by those who are less experienced. The flags you are adding are not > the problem -- it's the way that you are adding them -- specifically, > the assignment in the first line of your snippet, if it's applied > unconditionally. You should either be appending all of them, or > assigning them conditionally, so that they are sure to be assigned > only once, or -- preferably -- using another makefile that can't be > re-read multiple times during a build (ports/Mk/bsd.port.mk > automatically includes several makefiles that can be used for this > purpose, if you are building a port). You have been lucky not to trip > over this: every couple of months for the last several years I have > had to debug errors reported by users that arise from this problem. It > is more common with CFLAGS and CXXFLAGS but it can happen with FFLAGS, > too. Try 'find /usr/ports -name Makefile -maxdepth 3 | xargs grep FFLAGS' Then go read about the options chosen by the various port maintainers. I specifically set FFLAGS to avoid the questionable options set in the ports. If -malign-double appears in a port, it should probably be marked as broken. If a port uses -fdefault-real-8, it should probably be marked as broken. If a port uses -ffast-math, it may have issues that are extremely difficult to debug. (I removed freebsd-current@ and added cc to ports@) Oi vey. I see, it is complicated. So on the one hand some options are risky or just wrong and must not be used. On the other there is a large number of ports, which might not even build if this is implemented, and convincing upstream that they are wrong is never easy. Is there a middle ground? What about appending the suggested options to FFLAGS in ports/MK/bsd.port.mk? Or will it make debugging ports with "questionable" options even harder? 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"
11
11 ___ 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 include /etc/src.conf? i.e. graphics/libfpx
On 2013/02/13 19:08, O. Hartmann wrote: > Setting only base system source compiler optins in /etc/src.conf, for > instance > > # > CXXFLAGS+= -stdlib=libc++ > CXXFLAGS+= -std=c++11 > > > which do NOT appear in /etc/make.conf, make building port > grahpics/libfpx complaining about unrecognized compiler options. > > As far a sI know, /etc/src.conf is ONLY for building the source tree of > the operating system and make.conf is supposed to contain all stuff > necessary for compiling both world and ports, but /etc/src.conf is world > only. > > Am I wrong? > > Oliver > Yes. Because files/Makefile.bsd includes , /etc/src.conf is included. Remove CXXFLAGS from /etc/src.conf Add the following to /etc/make.conf .if !empty(.CURDIR:M/usr/src*) || !empty(.CURDIR:M/usr/obj*) CXXFLAGS+= -std=c++11 -stdlib=libc++ .endif ___ 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 include /etc/src.conf? i.e. graphics/libfpx
On Wed, Feb 13, 2013 at 12:30 PM, Yamaya Takashi wrote: > On 2013/02/13 19:08, O. Hartmann wrote: >> Setting only base system source compiler optins in /etc/src.conf, for >> instance >> >> # >> CXXFLAGS+= -stdlib=libc++ >> CXXFLAGS+= -std=c++11 >> >> >> which do NOT appear in /etc/make.conf, make building port >> grahpics/libfpx complaining about unrecognized compiler options. >> >> As far a sI know, /etc/src.conf is ONLY for building the source tree of >> the operating system and make.conf is supposed to contain all stuff >> necessary for compiling both world and ports, but /etc/src.conf is world >> only. >> >> Am I wrong? >> >> Oliver >> > Yes. > Because files/Makefile.bsd includes , > /etc/src.conf is included. > > src.conf(5) says: The only purpose of src.conf is to control the compilation of the FreeBSD source code, which is usually located in /usr/src. Cheers 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 include /etc/src.conf? i.e. graphics/libfpx
On Wed, Feb 13, 2013 at 3:33 PM, Tom Evans wrote: > On Wed, Feb 13, 2013 at 12:30 PM, Yamaya Takashi > wrote: >> On 2013/02/13 19:08, O. Hartmann wrote: >>> Setting only base system source compiler optins in /etc/src.conf, for >>> instance >>> >>> # >>> CXXFLAGS+= -stdlib=libc++ >>> CXXFLAGS+= -std=c++11 >>> >>> >>> which do NOT appear in /etc/make.conf, make building port >>> grahpics/libfpx complaining about unrecognized compiler options. >>> >>> As far a sI know, /etc/src.conf is ONLY for building the source tree of >>> the operating system and make.conf is supposed to contain all stuff >>> necessary for compiling both world and ports, but /etc/src.conf is world >>> only. >>> >>> Am I wrong? >>> >>> Oliver >>> >> Yes. >> Because files/Makefile.bsd includes , >> /etc/src.conf is included. >> >> > > src.conf(5) says: > > The only purpose of src.conf is to control the compilation of the FreeBSD > source code, which is usually located in /usr/src. > > Cheers > > Tom If this is taken literally then could it be said that ports that use bsd.lib.mk are broken because they are using makefile includes from the source tree? -Kimmo ___ 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"
Writing port makefile
Hi, I am writing a makefile for a new port. The port in question is a simple port that is a simple download extract and copy to a directory, how is the best way to achieve this? There is no compiling of files in the work directory it simply needs to extract and copy the file to a directory. Many thanks -- Regards, Gary J. Hayers g...@hayers.org PGP Signature http://www.hayers.org/pgp ___ 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: Writing port makefile
On 13 Feb 2013 15:20, "Gary J. Hayers" wrote: > > Hi, > > I am writing a makefile for a new port. The port in question is a simple port that is a simple download extract and copy to a directory, how is the best way to achieve this? There is no compiling of files in the work directory it simply needs to extract and copy the file to a directory. First define NO_BUILD=yes, and then make a do-install target. What type of files, and to where? 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"
french/aster build failure on amd64
Hi This is complex port, so maybe I made some errors in the dependend ports. The failure I get is: compiling aster... [FAILED] Exit code : 1 EXIT_COMMAND_5602_0069=1 *** Exception raised : error during compilation The full build log: http://eis.bris.ac.uk/~mexas/build.log Many 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: Writing port makefile
On 13/02/2013 15:30, Chris Rees wrote:
On 13 Feb 2013 15:20, "Gary J. Hayers" wrote:
First define NO_BUILD=yes, and then make a do-install target.
What type of files, and to where?
Chris
Thanks Chris, as it happens I found the NO_BUILD=yes target just after I
mailed the list. there will be 3 files installed in
/usr/share/doc/%{PORTNAME} and 1 file in /usr/local/bin. So I just have
to learn a little of the do-install target now.
--
Regards,
Gary J. Hayers
g...@hayers.org
PGP Signature
http://www.hayers.org/pgp
___
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: Writing port makefile
On Wed, Feb 13, 2013 at 03:34:59PM +, Gary J. Hayers wrote:
> On 13/02/2013 15:30, Chris Rees wrote:
> > On 13 Feb 2013 15:20, "Gary J. Hayers" wrote:
> > First define NO_BUILD=yes, and then make a do-install target.
> >
> > What type of files, and to where?
> >
> > Chris
>
> Thanks Chris, as it happens I found the NO_BUILD=yes target just after I
> mailed the list. there will be 3 files installed in
> /usr/share/doc/%{PORTNAME} and 1 file in /usr/local/bin. So I just have
> to learn a little of the do-install target now.
Don't forget to read the Porter's Handbook first:
http://www.freebsd.org/doc/en/books/porters-handbook/book.html
pgpE_1mMb7Biz.pgp
Description: PGP signature
Re: Writing port makefile
On 13/02/2013 15:37, Lars Engels wrote:
Thanks Chris, as it happens I found the NO_BUILD=yes target just after I
mailed the list. there will be 3 files installed in
/usr/share/doc/%{PORTNAME} and 1 file in /usr/local/bin. So I just have
to learn a little of the do-install target now.
Don't forget to read the Porter's Handbook first:
http://www.freebsd.org/doc/en/books/porters-handbook/book.html
Thanks Lars, I am going through it slowly, it's not like the first port
I ported which was fairly easy in comparison.
--
Regards,
Gary J. Hayers
g...@hayers.org
PGP Signature
http://www.hayers.org/pgp
___
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 sci/gramps?
What's the status on sci/gramps? Has the latest (or close to it) version been ported? Is there a list I should be on to see if it has or discuss it? I am really interested in this port and haven't heard from the new maintainer in a while. -- Yours in Christ, Joseph A Nagy Jr "Whoever loves instruction loves knowledge, But he who hates correction is stupid." -- Proverbs 12:1 Emails are not formal business letters, whatever businesses may want. Original content CopyFree (F) under the OWL http://copyfree.org/licenses/owl/license.txt ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ports include /etc/src.conf? i.e. graphics/libfpx
Am 02/13/13 15:05, schrieb Kimmo Paasiala: > On Wed, Feb 13, 2013 at 3:33 PM, Tom Evans wrote: >> On Wed, Feb 13, 2013 at 12:30 PM, Yamaya Takashi >> wrote: >>> On 2013/02/13 19:08, O. Hartmann wrote: Setting only base system source compiler optins in /etc/src.conf, for instance # CXXFLAGS+= -stdlib=libc++ CXXFLAGS+= -std=c++11 which do NOT appear in /etc/make.conf, make building port grahpics/libfpx complaining about unrecognized compiler options. As far a sI know, /etc/src.conf is ONLY for building the source tree of the operating system and make.conf is supposed to contain all stuff necessary for compiling both world and ports, but /etc/src.conf is world only. Am I wrong? Oliver >>> Yes. >>> Because files/Makefile.bsd includes , >>> /etc/src.conf is included. >>> >>> >> >> src.conf(5) says: >> >> The only purpose of src.conf is to control the compilation of the FreeBSD >> source code, which is usually located in /usr/src. >> >> Cheers >> >> Tom > > If this is taken literally then could it be said that ports that use > bsd.lib.mk are broken because they are using makefile includes from > the source tree? > > -Kimmo > I would consider them broken! How could I track down problems if they are results of intermixed config files when the manpage explicitely tells me, that the /etc/src.conf is only for the build of the operating system? signature.asc Description: OpenPGP digital signature
Re: 7+ days of dogfood
On 2/13/13, Anton Shterenlikht wrote:
> From s...@troutmask.apl.washington.edu Wed Feb 13 03:40:53 2013
>
> On Wed, Feb 13, 2013 at 02:15:08AM +, b.f. wrote:
> > On 2/13/13, Steve Kargl wrote:
> > > On Wed, Feb 13, 2013 at 12:18:29AM +, b.f. wrote:
> > >> ># cat /etc/make.conf|grep FFLAGS
> > >> >FFLAGS = -O2 -pipe -march=native -mtune=native
> > >>
> > >> Please do _not_ assign flags unconditionally in make.conf.
> > >
> > > FFLAGS is for compiling Fortran. I'm one of the people who
> > > has spent years working/patching gfortran. I think I might
> > > have a better understanding of what options to use with
> > > gfortran than most people.
> > >
> >
> > I know you have, but you are giving advice that is liable to be abused
> > by those who are less experienced. The flags you are adding are not
> > the problem -- it's the way that you are adding them -- specifically,
> > the assignment in the first line of your snippet, if it's applied
> > unconditionally. You should either be appending all of them, or
> > assigning them conditionally, so that they are sure to be assigned
> > only once, or -- preferably -- using another makefile that can't be
> > re-read multiple times during a build (ports/Mk/bsd.port.mk
> > automatically includes several makefiles that can be used for this
> > purpose, if you are building a port). You have been lucky not to trip
> > over this: every couple of months for the last several years I have
> > had to debug errors reported by users that arise from this problem. It
> > is more common with CFLAGS and CXXFLAGS but it can happen with FFLAGS,
> > too.
>
> Try 'find /usr/ports -name Makefile -maxdepth 3 | xargs grep FFLAGS'
> Then go read about the options chosen by the various port maintainers.
> I specifically set FFLAGS to avoid the questionable options set in
> the ports. If -malign-double appears in a port, it should probably
> be marked as broken. If a port uses -fdefault-real-8, it should
> probably
> be marked as broken. If a port uses -ffast-math, it may have issues
> that
> are extremely difficult to debug.
>
> (I removed freebsd-current@ and added cc to ports@)
>
> Oi vey. I see, it is complicated.
> So on the one hand some options are
> risky or just wrong and must not be used.
> On the other there is a large number of ports,
> which might not even build if this is implemented,
> and convincing upstream that they are wrong
> is never easy.
>
> Is there a middle ground?
> What about appending the suggested options
> to FFLAGS in ports/MK/bsd.port.mk?
> Or will it make debugging ports with "questionable"
> options even harder?
By all means, adjust our conservative default flags if you want to
improve the performance of some ports or other software -- only be
sure to test the results. Dr. Kargl has given you some good
candidates. But I'd advise you to add to the flags once at the start
of a build, and to deal with flag changes in a port or other piece of
software that you think are unnecessary and problematic by patching
the software itself. (If the software uses gmake or adds problematic
flags and then uses them before it invokes make(1) again you won't be
able to deal with them in make.conf, anyway.) It's probably best to
use a makefile that was intended for this purpose, like
${PORTSDIR}/Mk/bsd.local.mk. (Or, If you still prefer make.conf, you
could make the flag alterations there, but conditionally -- you could
test .CURDIR, for example, to prevent your changes from being
reapplied if you have descended into a work directory. But using
another makefile would probably be better.)
b.
___
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: Writing port makefile
On Wed, 13 Feb 2013 15:40:46 +
Gary J. Hayers articulated:
> Thanks Lars, I am going through it slowly, it's not like the first
> port I ported which was fairly easy in comparison.
If you don't have "portlint" installed, I would highly recommend that
you do so -- {/usr/ports/ports-mgmt/portlint}. Check out its 'man'
page. It is a very useful tool for checking 'Makefiles' in the ports
system.
--
Jerry ♔
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__
___
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: Writing port makefile
On 13/02/2013 15:40, Gary J. Hayers wrote:
Thanks Lars, I am going through it slowly, it's not like the first port
I ported which was fairly easy in comparison.
Ok sor got that going now but after I run make I get:
"Makefile", line 19: Need an operator
make: fatal errors encountered -- cannot continue
Anyone got any thoughts? Below is my Makefile or partial anyway
LICENSE=GPLv2
LICENSE_FILE= ${WRKSRC}/gpl.txt
RUN_DEPENDS=p5-NNTPClient:${PORTSDIR}/news/p5-NNTPClient
NO_BUILD= yes
do-install:
${INSTALL_SCRIPT} ${WRKSRC}/script ${PREFIX}/bin
${MKDIR} ${PREFIX}/doc/${PORTNAME}
${INSTALL_DATA} ${WRKSRC}/README.txt ${PREFIX}/doc/${PORTNAME}
${INSTALL_DATA} ${WRKSRC}/Changelog ${PREFIX}/doc/${PORTNAME}
${INSTALL_DATA} ${WRKSRC}/gpl.txt ${PREFIX}/doc/${PORTNAME}
.include
--
Regards,
Gary J. Hayers
g...@hayers.org
PGP Signature
http://www.hayers.org/pgp
___
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"
Switch from portupgrade to portmaster - looking for '--keep-going'
Hi, luky using portmater now - but I am searching for any flag that was called --keep-going in portupgrade: , | --keep-going Force the upgrade of a package even if some of the | requisite packages have failed to upgrade in | advance. ` Is there something like this in portupgrade? Heino ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Writing port makefile
On 13/02/2013 17:49, Gary J. Hayers wrote:
On 13/02/2013 15:40, Gary J. Hayers wrote:
Thanks Lars, I am going through it slowly, it's not like the first port
I ported which was fairly easy in comparison.
Ok sor got that going now but after I run make I get:
"Makefile", line 19: Need an operator
make: fatal errors encountered -- cannot continue
Anyone got any thoughts? Below is my Makefile or partial anyway
LICENSE=GPLv2
LICENSE_FILE= ${WRKSRC}/gpl.txt
RUN_DEPENDS=p5-NNTPClient:${PORTSDIR}/news/p5-NNTPClient
NO_BUILD= yes
do-install:
${INSTALL_SCRIPT} ${WRKSRC}/script ${PREFIX}/bin
${MKDIR} ${PREFIX}/doc/${PORTNAME}
${INSTALL_DATA} ${WRKSRC}/README.txt ${PREFIX}/doc/${PORTNAME}
${INSTALL_DATA} ${WRKSRC}/Changelog ${PREFIX}/doc/${PORTNAME}
${INSTALL_DATA} ${WRKSRC}/gpl.txt ${PREFIX}/doc/${PORTNAME}
.include
Scratch that, got it working. Many thanks all
--
Regards,
Gary J. Hayers
g...@hayers.org
PGP Signature
http://www.hayers.org/pgp
___
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 sci/gramps?
Joseph A. Nagy, Jr writes: > What's the status on sci/gramps? Has the latest (or close to it) > version been ported? Is there a list I should be on to see if it > has or discuss it? I am really interested in this port and > haven't heard from the new maintainer in a while. gramps-3.3.0 builds and runs for me on amd64. Mind you, I don't do anything that's likely to kick over any rocks Robert Huff ___ 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/visionworkbench: 4 out of 4 hunks failed--saving rejects to src/vw/BundleAdjustment/ControlNetworkLoader.cc.rej
Since a couple of days now, the last update of port graphics/visionworkbench seems to be very sloppy and incomplete committed: ===>>> Starting check for build dependencies ===>>> Gathering dependency list for graphics/visionworkbench from ports ===>>> Dependency check complete for graphics/visionworkbench ===>>> All >> visionworkbench-2.2.0_3 (1/1) ===> Cleaning for visionworkbench-2.2.0_4 ===> License NOSA accepted by the user ===> visionworkbench-2.2.0_4 depends on file: /usr/local/sbin/pkg - found ===> Extracting for visionworkbench-2.2.0_4 => SHA256 Checksum OK for VisionWorkbench-2.2.0.tar.gz. ===> Patching for visionworkbench-2.2.0_4 ===> Applying FreeBSD patches for visionworkbench-2.2.0_4 4 out of 4 hunks failed--saving rejects to src/vw/BundleAdjustment/ControlNetworkLoader.cc.rej File to patch: signature.asc Description: OpenPGP digital signature
devel/mips-rtems-gcc build problem
Hello :-) I need to build mips-rtems-gcc but I found this problem: Configuring in mips-rtems/libgcc checking for --enable-version-specific-runtime-libs... no checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking for gawk... nawk checking build system type... amd64-portbld-freebsd9.1 checking host system type... mips-unknown-rtems checking for mips-rtems-ar... /usr/local/mips-rtems/bin/ar checking for mips-rtems-lipo... mips-rtems-lipo checking for mips-rtems-nm... /mnt/stuff/usr/ports/devel/mips-rtems-gcc/work/build/./gcc/nm checking for mips-rtems-ranlib... /usr/local/mips-rtems/bin/ranlib checking for mips-rtems-strip... /usr/local/mips-rtems/bin/strip checking whether ln -s works... yes checking for mips-rtems-gcc... /mnt/stuff/usr/ports/devel/mips-rtems-gcc/work/build/./gcc/xgcc -B/mnt/stuff/usr/ports/devel/mips-rtems-gcc/work/build/./gcc/ -nostdinc -B/mnt/stuff/usr/ports/devel/mips-rtems-gcc/work/build/mips-rtems/newlib/ -isystem /mnt/stuff/usr/ports/devel/mips-rtems-gcc/work/build/mips-rtems/newlib/targ-include -isystem /mnt/stuff/usr/ports/devel/mips-rtems-gcc/work/gcc-4.5.2/newlib/libc/include -B/usr/local/mips-rtems/bin/ -B/usr/local/mips-rtems/lib/ -isystem /mnt/stuff/usr/ports/devel/mips-rtems-gcc/work/build/./gcc -isystem /usr/local/mips-rtems/include -isystem /usr/local/mips-rtems/sys-include checking for suffix of object files... configure: error: in `/mnt/stuff/usr/ports/devel/mips-rtems-gcc/work/build/mips-rtems/libgcc': configure: error: cannot compute suffix of object files: cannot compile See `config.log' for more details. gmake[1]: *** [configure-target-libgcc] Error 1 gmake[1]: Leaving directory `/mnt/stuff/usr/ports/devel/mips-rtems-gcc/work/build' gmake: *** [all] Error 2 *** [do-build] Error code 1 Stop in /mnt/stuff/usr/ports/devel/mips-rtems-gcc. *** [build] Error code 1 Stop in /mnt/stuff/usr/ports/devel/mips-rtems-gcc. -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: Switch from portupgrade to portmaster - looking for '--keep-going'
On 13 Feb 2013 18:18, "Heino Tiedemann" wrote: > > Hi, > > luky using portmater now - but I am searching for any flag that was > called --keep-going in portupgrade: > > , > | --keep-going Force the upgrade of a package even if some of the > | requisite packages have failed to upgrade in > | advance. > ` > > > Is there something like this in portupgrade? I'm afraid not. The author of portmaster considered that it wouldn't be safe, since the code couldn't guess at the reason for failure. 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"
