Re: graphics/libEGL & graphics/libglapi fail: Localization?
I fetched these 2 ports from the public FreeBSD repository, re-named them to what poudriere expects for naming convention And re-started poudriere. graphics/gbm and graphics/libGL fail with same error (no surprise). Fetching these two and re-naming them as described allows poudriere to go on with its business. ===> Building for libGL-10.3.2 gmake[1]: Entering directory '/wrkdirs/usr/ports/graphics/libGL/work/Mesa-10.3.2/src/mesa/drivers/dri/common/xmlpool' cd ../../../../../.. && gmake am--refresh cd ../../../../../.. && gmake am--refresh Updating (ca) ca/LC_MESSAGES/options.mo from ca.po. msgfmt: not found Makefile:638: recipe for target 'ca/LC_MESSAGES/options.mo' failed gmake[1]: *** [ca/LC_MESSAGES/options.mo] Error 127 gmake[1]: Leaving directory '/wrkdirs/usr/ports/graphics/libGL/work/Mesa-10.3.2/src/mesa/drivers/dri/common/xmlpool' *** Error code 2 -- FreeBSD_amd64_11-Current_RadeonKMS - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/graphics-libEGL-graphics-libglapi-fail-Localization-tp5961228p5961364.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ 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: Reducing the size of the ports tree (brainstorm v2)
On 31/10/2014 18:56, Baptiste Daroussin wrote: > Hi all, > > tijl@ spotted an interesting point, distinfo and pkg-descr files files > convenient are taking a lot of space for "free", we can reduce the size of the > while ports tree by a factor 2 by simply merging them into one of the other > files (Makefile and/or pkg-plist) from my testing it really devides > significantly the size of the tree. > > Problem is how to merge them if we want to. > > What we do not want to loose: > - Easyness of parsing distinfo > - Easyness to get informations about the description > > so far I have not been able to figure out a user friendly way > > Ideas I got so far only concerns pkg-descr: > Adding an entry in the Makefile for the WWW: > WWW= bla > or an entry in the plist: @www http... > > for the description the Makefile is not suitable as multi line entry in > Makefiles are painful > Maybe a new keyword: > @descr < mydesc > in > multiline > EOD > > which could easily be added to the plist parser in pkg. But I'm do not find > that > very friendly in particular for make(1) to extract the data. > > Concerning the distinfo I have no idea. > > so this mail is a call of ideas :), if nothing nice ideas is found we will > just > do nothing here :) Most respondents in this thread are talking in terms of incorporating the small files in a port into one or other of the larger files. That's an obvious first step. However, I wonder if it wouldn't make more sense to create one file which includes all of the other bits of port infrastructure. This should be a text format that people can read easily and manipulate with a text editor or standard unix tools. Something like UCL might be a good choice. So the first step would be to pack Makefile, pkg-plist, pkg-descr, distinfo into one file, and add a step to unpack the port contents as the first thing when building a port. Which should be something that can be handled through the category and top-level Makefiles. This should achieve the aim of reducing inode consumption and the fragmentation in the filesystem but retain backwards compatibility for everything that uses the ports currently. Ultimately though, I'd be happy to see the metadata not related to actually building the port -- maintainer, comment, categories, license info, even master sites and other information about distfiles moved out of the Makefile and become variables in the port file. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matt...@infracaninophile.co.uk signature.asc Description: OpenPGP digital signature
Re: Reducing the size of the ports tree (brainstorm v2)
On 11/1/2014 2:20 AM, Matthew Seaman wrote: However, I wonder if it wouldn't make more sense to create one file which includes all of the other bits of port infrastructure. This should be a text format that people can read easily and manipulate with a text editor or standard unix tools. Something like UCL might be a good choice. That sounds dangerously close to reinventing SRPM. ___ 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: Reducing the size of the ports tree (brainstorm v2)
On 01/11/2014 10:19, Darren Pilgrim wrote: > On 11/1/2014 2:20 AM, Matthew Seaman wrote: >> However, I wonder if it wouldn't make more sense >> to create one file which includes all of the other bits of port >> infrastructure. This should be a text format that people can read >> easily and manipulate with a text editor or standard unix tools. >> Something like UCL might be a good choice. > > That sounds dangerously close to reinventing SRPM. Now you mention it, yes it does. Although SRPM's are a bit more opaque than what I had in mind. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matt...@infracaninophile.co.uk signature.asc Description: OpenPGP digital signature
RE: RE: reducing the size of the ports tree
Not initially welcoming this new effort... explanation and other PKG problems taking precedence... I've a few scripts which use the smaller files, and have used them extensively in pipes. Syntax within the Makefile would make those counterintuitive.I would wonder also if it would break port infrastructure like the Mk and Tools and "make search" and portsearch (etc -- ports )... essentially breaking more things than would be solved. Indeed, I've many ideas for MORE small files for people crafting shell scripts that would be of more use down the road, and incorporated someday into additional port tools, portmasters, portupgrades, etc... So as far as this particular suggestion, maybe if someone wants it bad enough one should build a prototype and test locally several years with many ports and upgrades to determine what it breaks... and how to write new tools. But I conjecture that effort would be better spent with PR backlogs, fixing pkg2ng (which fails here on one machine ) etc... and making pkg more robust... (complete recovery if the database is hosed, with a something local_sqlite_hosed_reuild_sh.sh etc etc And the documentation. Many many more examples of everyday usage over the course of a year and UPDATING scenarious would be appreciated... and also streamlining pkg so it works better on low power machines with many ports installed. Including less segfaults... As an aside, I am now on a machine which never had the problem before, after a failed pkg2ng conversion, A... pkg install -f nettle wants to install csound! what file is telling it that? The database ??? ... and seven others I had just deinstalled B... make install ( proceeds with "Child process terminated abnomally... segmentation fault) before the install. Not known if anything was running beforehand. Not problems with the install. But it keeps occuring... What process? Something in the background wanting that nettle >> csound dependency? Pkg working before the make command? Part of the make command infrastructure now more buggy? Thankfully that machine is not the primary one here, and all the programs installed still work on it as far as I know. But its registration data is not exact and pkg-devel as installed on it could be debugged more... as well as pkg2ng retested to work on v9 more precisely... It failed three times to convert that machine. (not installed unless desinstalling direct from the port, so could not upgrade.. or pkg info the port) ___ 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: CFT: Update to xf86-video-ati 7.5.0
On 31.10.2014 21:36, Christian Weisgerber wrote:
> Maybe it wasn't clear in the Xorg.0.log snippet I sent, but from
> comparing log files, the actual error was this:
>
> [351790.259] drmOpenByBusid: Interface 1.4 failed, trying 1.1
> ...
> [351790.259] (EE) RADEON(0): [drm] failed to set drm interface version.
> [351790.259] (EE) RADEON(0): Kernel modesetting setup failed
It made me think that somehow, radeondrm, the old kernel non-KMS module,
was loaded. That's why I asked about xf86-video-ati{,-ums} 6.14.6. I
don't know how this happened.
--
Jean-Sébastien Pédron
signature.asc
Description: OpenPGP digital signature
Re: graphics/libEGL & graphics/libglapi fail: Localization?
2014-11-01 10:17 GMT+03:00 Beeblebrox : > I fetched these 2 ports from the public FreeBSD repository, > re-named them to what poudriere expects for naming convention > And re-started poudriere. graphics/gbm and graphics/libGL fail with same > error (no surprise). > Fetching these two and re-naming them as described allows poudriere to go on > with its business. > > ===> Building for libGL-10.3.2 > gmake[1]: Entering directory > '/wrkdirs/usr/ports/graphics/libGL/work/Mesa-10.3.2/src/mesa/drivers/dri/common/xmlpool' > cd ../../../../../.. && gmake am--refresh > cd ../../../../../.. && gmake am--refresh > Updating (ca) ca/LC_MESSAGES/options.mo from ca.po. > msgfmt: not found > Makefile:638: recipe for target 'ca/LC_MESSAGES/options.mo' failed > gmake[1]: *** [ca/LC_MESSAGES/options.mo] Error 127 > gmake[1]: Leaving directory > '/wrkdirs/usr/ports/graphics/libGL/work/Mesa-10.3.2/src/mesa/drivers/dri/common/xmlpool' > *** Error code 2 > > -- > FreeBSD_amd64_11-Current_RadeonKMS > > > > > - > FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS > -- > View this message in context: > http://freebsd.1045724.n5.nabble.com/graphics-libEGL-graphics-libglapi-fail-Localization-tp5961228p5961364.html > Sent from the freebsd-ports mailing list archive at Nabble.com. > ___ > 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" I had the same problem. See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194561 It seems that NLS enabled gmake makes affected ports able to build. -- Mikhail ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: net-mgmt/icinga2: Icinga Web is not working: Error: Could not read object configuration data!
On Fri, Oct 31, 2014 at 07:55:04PM +0100, O. Hartmann wrote: > > On CURRENT (most recent), I run net-mgmt/icinga2. Setup ran smooth, I also > set up the IDO > for PostgreSQL. Checking whether icinga2 logs data to the PostgreSQL database > resulted > positive. > > I try to install/configure a Web Interface a sdescribed in the Icinga2 docs. > IDO is a > prerequiste for Icinga Web (I'm not using Icinga Web 2!). > > For that purpose, I installed net/mgmt/icinga (which contains the web > interface). I made > the proper changes to /usr/local/etc/icinga/cgi.cfg as reported in this HowTo: > http://lists.freebsd.org/pipermail/freebsd-ports/2014-June/093372.html. > Please see also > https://forums.freebsd.org/threads/icinga2-network-monitoring.47106/. Via > icinga2-enable-feature I also enabled all requested modules as described in > the Icinga2 > docs. > > So far. Having doen EXACTLY as suggested, I do not get any kind of > Webinterface. The web > browser (Mozilla Firefox) reports always: Error: Could not read object > configuration data! > > There is something missing. > > Is someone using Icinga2 with the classical Web and has followed these > instructions and > gets a different result? > Hi Oliver, on a clean system, I just followed (my own) CFT instructions you also used. I didn't encounter a problem. The only typo in the list is that this: cp /usr/local/share/examples/icinga/apache22/icinga.conf-sample /usr/local/etc/apache2/Includes/icinga.conf should be apache22 Apart from this, there wasn't anything that didn't work. I used "pkg install apache22 icinga icinga2" though and didn't need to copy the .cfg-sample file as the icinga port does this by itself now. Can you please check all file and directory locations you changed in icinga/cgi.cfg? I guess the "status_file" line leads to a non-existing status.dat. Please also CC me on any questions you have regarding icinga[2] and FreeBSD as I maintain both ports. Lars pgpm7nd68Kf6M.pgp Description: PGP signature
Re: pkg 1.4 freeze please test test test!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 29/10/2014 02:19, Baptiste Daroussin wrote: > We are starting the release process of pkg 1.4, we want to have a > better release process than with every single previous version of > pkg. For that we will need you help! > > pkg-devel has been updated to the latest version of pkg as of > alpha2. I have 1.4.0.p.a16 installed and have two problems now: (1) Latest 11:amd64 package repository doesn't have newest package (2) this package thinks, that 1.4.0.p.a16 is newer than 1.4.0.a4: lev@labrat:~% pkg version -vIL= ... pkg-devel-1.4.0.p.a16 > succeeds index (index has 1.4.0.a4) ... lev@labrat:~% sudo pkg -4 upgrade Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. All repositories are up-to-date. Checking for upgrades (216 candidates): 37% pkg-devel~ports-mgmt/pkg-devel has no direct installation candidates, change it to pkg-devel~ports-mgmt/pkg-devel? [Y/n]: y Checking for upgrades (216 candidates): 100% Processing candidates (216 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. lev@labrat:~% - -- // Lev Serebryakov -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJUVOQAXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EeP1EUQALM9Hs2X1F3Zoa94RwpHK4XI 0H8/VWB/NA9J//UGqW1btikXpbSDRSA2DsjL3wzfk0Z0SNQrExrUlwthkv3n/llh OPTthShVOijOGTuvE+voBuc0aGNDOfAodNaJKHncF/qai/6P3WqqGnxsuEGegZm4 JD0bM0OQfnoQz/xECWFOwJA6EFPgneAzCthpNkCFUbe0d7/hk9uDD3I6rmJPzT4T pMRizelSZxNyMc0kVJZjfa/Zlj6h818R6puzbb3ErX0SyijyzyOKI1pAZ5mmSgl4 vPbMWELHQWVRRQS1KcvGfNJMgpYB0UG93flZ+E9M3h/ScBqdZc+2OqYUEd+ZiE/T kPJ0oQw9t283banasA0k8Ej59478ZN1CxnmO766x96lqCTlbqbl3KFwgpNORCvas /WBjV0T8ZgSf1gCh5WnFQDF0rmpfql4Ol0ynY4A8ToKtJsAUpQ+vwR8WieHRKWf9 28fqmq/+ZewX5mS/7/eZ/DZdlqgKSmWv7JbETVYR3IAkF1a3s38DrU1ZZ5TnUrPM xWqvFC8hfW7aiMtzQ8OWW8WIFMC02/0oyxEqnFsVh/+IIsvXtTQOmPFd+tNlU3Xq FjkqFJRmVBqLS2eXtNvF5WzOJrEJmAOkkYVzGAlpYQVAVie+UZHKu3D1A8B8+EPO 3PfdV96CUGhS56H9Z8R3 =v9Qt -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: net-mgmt/icinga2: Icinga Web is not working: Error: Could not read object configuration data!
Am Sat, 1 Nov 2014 14:12:08 +0100 Lars Engels schrieb: > On Fri, Oct 31, 2014 at 07:55:04PM +0100, O. Hartmann wrote: > > > > On CURRENT (most recent), I run net-mgmt/icinga2. Setup ran smooth, I also > > set up the > > IDO for PostgreSQL. Checking whether icinga2 logs data to the PostgreSQL > > database > > resulted positive. > > > > I try to install/configure a Web Interface a sdescribed in the Icinga2 > > docs. IDO is a > > prerequiste for Icinga Web (I'm not using Icinga Web 2!). > > > > For that purpose, I installed net/mgmt/icinga (which contains the web > > interface). I > > made the proper changes to /usr/local/etc/icinga/cgi.cfg as reported in > > this HowTo: > > http://lists.freebsd.org/pipermail/freebsd-ports/2014-June/093372.html. > > Please see > > also https://forums.freebsd.org/threads/icinga2-network-monitoring.47106/. > > Via > > icinga2-enable-feature I also enabled all requested modules as described in > > the > > Icinga2 docs. > > > > So far. Having doen EXACTLY as suggested, I do not get any kind of > > Webinterface. The > > web browser (Mozilla Firefox) reports always: Error: Could not read object > > configuration data! > > > > There is something missing. > > > > Is someone using Icinga2 with the classical Web and has followed these > > instructions > > and gets a different result? > > > > Hi Oliver, > > on a clean system, I just followed (my own) CFT instructions you also > used. I didn't encounter a problem. The only typo in the list is that > this: > cp /usr/local/share/examples/icinga/apache22/icinga.conf-sample > /usr/local/etc/apache2/Includes/icinga.conf > > > > should be > apache22 > > Apart from this, there wasn't anything that didn't work. I used > "pkg install apache22 icinga icinga2" though and didn't need to copy the > .cfg-sample file as the icinga port does this by itself now. > > Can you please check all file and directory locations you changed in > icinga/cgi.cfg? I guess the "status_file" line leads to a non-existing > status.dat. > > > Please also CC me on any questions you have regarding icinga[2] and > FreeBSD as I maintain both ports. > > > Lars Correct - I had a type in cgi.cfg. I use Apache 2.4 (www/apache24) by the way. I have now a web page - but it is empty/ugly looking. I guess there is a bit of further work. Thanks a lot for the hint. Kind Regards, Oliver pgptEo7KEmxJR.pgp Description: OpenPGP digital signature
Re: Reducing the size of the ports tree (brainstorm v2)
On Sat, Nov 01, 2014 at 12:07:23AM +0100, Tijl Coosemans wrote:
> On Fri, 31 Oct 2014 19:56:21 +0100 Baptiste Daroussin
> wrote:
> > tijl@ spotted an interesting point, distinfo and pkg-descr files files
> > convenient are taking a lot of space for "free", we can reduce the size of
> > the
> > while ports tree by a factor 2 by simply merging them into one of the other
> > files (Makefile and/or pkg-plist) from my testing it really devides
> > significantly the size of the tree.
> >
> > Problem is how to merge them if we want to.
> >
> > What we do not want to loose:
> > - Easyness of parsing distinfo
> > - Easyness to get informations about the description
> >
> > so far I have not been able to figure out a user friendly way
> >
> > Ideas I got so far only concerns pkg-descr:
> > Adding an entry in the Makefile for the WWW:
> > WWW= bla
> > or an entry in the plist: @www http...
> >
> > for the description the Makefile is not suitable as multi line entry in
> > Makefiles are painful
> > Maybe a new keyword:
> > @descr < > mydesc
> > in
> > multiline
> > EOD
> >
> > which could easily be added to the plist parser in pkg. But I'm do not find
> > that
> > very friendly in particular for make(1) to extract the data.
> >
> > Concerning the distinfo I have no idea.
> >
> > so this mail is a call of ideas :), if nothing nice ideas is found we will
> > just
> > do nothing here :)
>
> For distinfo I was thinking about something like this in the Makefile:
>
> DIST_FILES= FOO BAR
>
> FOO_FILE= foo-1.0
> FOO_SITES=http://www.example.com/foo/
> FOO_SIZE= 12345
> FOO_SHA256= 0123456789abcdef.
>
> BAR_FILE= bar-2.0
> BAR_SITES=http://www.example.com/bar/
> BAR_SIZE= 54321
> BAR_SHA256= .fedcba9876543210
>
> If bsd.port.mk then contained this:
> DIST_FILES?= DIST
> DIST_FILE?=
> ${PORTNAME}-${DISTVERSIONPREFIX}${DISTVERSION}${DISTVERSIONSUFFIX}
>
> Then for ports with a single distfile named after PORTNAME (the large
> majority), the above would reduce to:
>
> DIST_SITES= http://www.example.com/foo/
> DIST_SIZE=12345
> DIST_SHA256= 0123456789abcdef.
>
> Also, if BAR_SITES is the same as FOO_SITES you can use somthing like
> BAR_SITES=${FOO_SITES} of course.
Yes, it should work, especially if we don't stick to the binary solution:
there are only ~1000 distinfo with more than one distfile and ~350 with more
than two. So, we can embed distfile information for majority of ports
and keep 350 distinfo files. This will allow us to remove 24k+ files.
> pkg-descr and pkg-plist will be around for a while I think but maybe pkg
> could support an alternative syntax that is similar to the manifest file
> included in the package. This file (named Manifest maybe?) would include
> a comment, description, install/deinstall scripts and a list of files and
> directories like this (copied from https://github.com/freebsd/pkg):
I don't like embedded files, they are usually not user-serviceable.
We can add WWW variable to the Makefile though, it will greatly speed up
INDEX building.
--
Alex
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
how to get back ruby-fox16
I've belatedly noticed that a port I use (x11-toolkits/ruby-fox16) no longer exists, reason being: "Has expired: RubyForge shutdown May 15 2014". What do I need to do to get it back? -- Will ___ 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"
users of devel/svk ?
Hi! I'm researching the state of the port devel/svk. There's an open PR https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194337 and there was discussion about removing that port because there's no real/maintained upstream anymore and the software has too many open issues. So: who is still using this port ? -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ 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"
math/jama fail due to UNSET DOCS
I have "OPTIONS_UNSET= DOCS EXAMPLES" Fails with: ===> Staging for jama-1.2.5 ===> Generating temporary packing list /bin/mkdir -p /wrkdirs/usr/ports/math/jama/work/stage/usr/local/include/tnt /usr/bin/unzip -qo /portdistfiles/tnt/jama125.zip -d /wrkdirs/usr/ports/math/jama/work/stage/usr/local/include/tnt /bin/mkdir -p /wrkdirs/usr/ports/math/jama/work/doc /wrkdirs/usr/ports/math/jama/work/stage/usr/local/share/doc/jama /usr/bin/unzip -qo /portdistfiles/tnt/jama102doc.zip -d /wrkdirs/usr/ports/math/jama/work/doc unzip: Failed to open '/portdistfiles/tnt/jama102doc.zip' *** Error code 1 - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/math-jama-fail-due-to-UNSET-DOCS-tp5961638.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ 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"
makepatch, update-patches, patchtool
We have (at least) three helpers in the ports tree for creating and updating patch-* files: * makepatch bsd.port.mk target, self-contained * update-patches bsd.port.mk target, calls Tools/scripts/update-patches (originally taken from OpenBSD but not synced in a long time) * patchtool Tools/scripts/patchtool.py Is it time to trim some of those? I'm under the impression that "makepatch" is currently the favored one. Any reason to keep the others? -- Christian "naddy" Weisgerber na...@mips.inka.de ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
devel/tex-web2c not found
Hi, when I try to compile tex-web2c, I will get this: configure: You requested to build `web2c' using an installed `kpathsea' version, configure: which requires to locate the header file. configure: error: Sorry, not found under any of: /usr/local/include * ===> Script "configure" failed unexpectedly. Please report the problem to h...@freebsd.org [maintainer] and attach the "/usr/home/PORTS/work/usr/ports/devel/tex-web2c/work/texlive-20140525-source/texk/web2c/config.log" including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. a /usr/local/sbin/pkg-static info -g -Ea). *** Error code 1 Stop. make: stopped in /usr/ports/devel/tex-web2c [X220]...devel/tex-web2c (root) > I hope it is a simple as the file does not exist at all. Erich PS The log file is available here: http://www.alogt.com/downloads/config.log What snv says: [X220]/usr/ports (root) > svn info Path: . Working Copy Root Path: /usr/ports URL: svn://svn0.us-east.freebsd.org/ports/head Relative URL: ^/head Repository Root: svn://svn0.us-east.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 371983 Node Kind: directory Schedule: normal Last Changed Author: antoine Last Changed Rev: 371983 Last Changed Date: 2014-11-01 15:05:51 +0800 (Sat, 01 Nov 2014) ___ 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"
