[QAT] r325179: 4x leftovers

[Ports-QAT]

Update to openvex 0.5.2 which fixes a workaround for a bug in sdcc that
has recently been fixed.

Submitted by:   Jason Bacon  (maintainer)
-

  Build ID:  20130822094800-19987
  Job owner: t...@freebsd.org
  Buildtime: 12 minutes
  Enddate:   Thu, 22 Aug 2013 10:00:08 GMT

  Revision:  r325179
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=325179

-

Port:devel/openvex 0.5.2

  Buildgroup: 9.1-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~t...@freebsd.org/20130822094800-19987-172092/openvex-0.5.2.log

  Buildgroup: 9.1-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~t...@freebsd.org/20130822094800-19987-172093/openvex-0.5.2.log

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~t...@freebsd.org/20130822094800-19987-172094/openvex-0.5.2.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~t...@freebsd.org/20130822094800-19987-172095/openvex-0.5.2.log


--
Buildarchive URL: 
redports 
___
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: building seamonkey with clang

[Dan Lukes]

On 08/22/13 01:04, Cary:

On Wed, Aug 21, 2013 at 07:20:52PM +0200, Dan Lukes wrote:

0.  Program arguments: /usr/bin/clang++ -cc1 -triple i386-unknown-freebsd9.0

...

sr/local/include -fmodule-cache-path /var/tmp/clang-module-cache -O3 -Wall -Wpoi

...

y/work/comm-release/mailnews/local/src/nsMsgMaildirStore.cpp


You may be interested to know that source will compile with -O0
(instead of -O3).



in what way could one change the port's configuration before running make?


I don't know, I didn't do it.

I just entered the failed command from command line (from appropriate 
directory, with -O3 changed to -O0). You can restart make then. It will 
continue with compilation of next source.


Note, there is OPTIMIZED_CFLAGS option recognized. It has been used for 
task you are asked for in the past. It is ignored by both Seamonkey's 
and Firefox's Makefile now. I don't know it is intentional or it is 
another bug.



Dan


___
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

[portscout]

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/performance   | 0.3.2   | 0.4.0
+-+


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...@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"

[SOLVED] Re: Can't build p5-Encode-Detect

[Andrea Venturoli]

On 08/22/13 00:10, Andrea Venturoli wrote:

Hello.

I'm deploying a fresh box and I'm stuck on the following.


# cd /usr/ports/converters/p5-Encode-Detect
# make
===> Fetching all distfiles required by p5-Encode-Detect-1.01 for
building
===>  Extracting for p5-Encode-Detect-1.01
=> SHA256 Checksum OK for Encode-Detect-1.01.tar.gz.
===>  Patching for p5-Encode-Detect-1.01
===>   p5-Encode-Detect-1.01 depends on package:
p5-ExtUtils-CBuilder>=0 - found
===>   p5-Encode-Detect-1.01 depends on file:
/usr/local/lib/perl5/site_perl/5.14/Module/Build.pm - found
===>   p5-Encode-Detect-1.01 depends on file:
/usr/local/bin/perl5.14.4 - found
===>  Configuring for p5-Encode-Detect-1.01
Warning: ExtUtils::CBuilder not installed or no compiler detected
Proceeding with configuration, but compilation may fail during Build

Created MYMETA.yml and MYMETA.json
Creating new 'Build' script for 'Encode-Detect' version '1.01'
===>  Building for p5-Encode-Detect-1.01
Building Encode-Detect
Error: no compiler detected to compile 'src/LangBulgarianModel.cpp'.
Aborting
*** Error code 45

Stop in /usr/ports/converters/p5-Encode-Detect.




Of course p5-ExtUtils-CBuilder is there and it doesn't even give a
warning when I build it.


# pkg_info|grep p5-Ext
p5-ExtUtils-CBuilder-0.2802.05,1 Compile and link C code for Perl modules
# perl -v

This is perl 5, version 14, subversion 4 (v5.14.4) built for
amd64-freebsd

 > ...

# uname -a
FreeBSD .x 8.3-RELEASE FreeBSD 8.3-RELEASE #0: Mon Apr  9
21:23:18 UTC 2012
r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64




I tried all the suggestions I could find on the web (including
installing p5-IPC-Cmd and rebuilding), but none worked.



Any help?

  bye & Thanks
 av.


I'll answer myself, hoping this message will live to help others.
The problem was I had /usr/ports mounted through NFS; after I copied it 
locally, it was gone.

I just wish the error message would be clearer :)

 bye
av.
___
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: sysutils/fusefs-ntfs & fusefs_enable="YES"

[Mark Felder]

On Wed, Aug 21, 2013, at 17:09, RW wrote:
> On Wed, 21 Aug 2013 23:44:41 +0200
> Dominic Fandrey wrote:
> 
> > On 21/08/2013 23:39, RW wrote:
> > > The README.FreeBSD file for sysutils/fusefs-ntfs and several howtos
> > > suggest adding the line:
> > > 
> > > fusefs_enable="YES"
> > > 
> > > to rc.conf, but as far as I can see this doesn't affect anything
> > > since the port doesn't install an rc.d file. I would have expected
> > > such a file to load the fuse kernel module which I'm having to load
> > > myself.
> > 
> > The file is there. fusefs-kmod
> 
> I see what's happened. Earlier in the year,against my better judgement,
> I move to CURRENT in futile attempt to make intel KMS work. It looks
> like fuse has been moved into the base system, but /etc/rc.d/ hasn't yet
> been updated to reflect that. 
>

There isn't an /etc/rc.d/ for every kernel module. If you want to use
fuse on FreeBSD 10 and later just put fuse_load="YES" in loader.conf.
The rc.d script in the port was just a nice courtesy. I don't think it's
likely we'll see an /etc/rc.d/fuse script appear in the base system.
___
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: pkgng+portmaster: portmaster erased the field packages.time

[Bryan Drewery]

On 8/21/2013 12:44 AM, Yuri wrote:
> After I converted to pkgng, field packages.time contained the time of
> conversion.
> 
> When I ran portmaster to rebuild few ports, all those timestamps
> disappeared, and portmaster only left the timestamps on the ports it
> reinstalled.
> I suspect this is a bug, since this behavior doesn't appear reasonable.
> Why would portmaster erase the time field? How can it conclude it is wrong?
> 
> Yuri

By "Packages.time" I assume you mean the timestamp the package was
installed? There is no "conversion" timestamp stored by pkgng.

How are you seeing this timestamp? With 'pkg query "%o %t"'?

Portmaster itself is not modifying this data at all (it can't), only
pkgng updates this timestamp.

-- 
Regards,
Bryan Drewery



signature.asc
Description: OpenPGP digital signature

Re: sysutils/fusefs-ntfs & fusefs_enable="YES"

[RW]

On Thu, 22 Aug 2013 06:41:33 -0500
Mark Felder wrote:

> On Wed, Aug 21, 2013, at 17:09, RW wrote:

> > I see what's happened. Earlier in the year,against my better
> > judgement, I move to CURRENT in futile attempt to make intel KMS
> > work. It looks like fuse has been moved into the base system,
> > but /etc/rc.d/ hasn't yet been updated to reflect that. 
> >
> 
> There isn't an /etc/rc.d/ for every kernel module. If you want to use
> fuse on FreeBSD 10 and later just put fuse_load="YES" in loader.conf.
> The rc.d script in the port was just a nice courtesy. I don't think
> it's likely we'll see an /etc/rc.d/fuse script appear in the base
> system.

I have added it to loader.conf, but the reason I brought it up was that
I thought the documentation might be out of date, which appears to be
the case. 

If nothing's been decided I can't really submit a documentation
patch.

If anyone's interested the relevant files are:

sysutils/ntfsprogs/files/README.FreeBSD
sysutils/fusefs-ntfs/files/README.FreeBSD
___
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: sysutils/fusefs-ntfs & fusefs_enable="YES"

[Mark Felder]

On Thu, Aug 22, 2013, at 8:16, RW wrote:
> On Thu, 22 Aug 2013 06:41:33 -0500
> Mark Felder wrote:
> 
> > On Wed, Aug 21, 2013, at 17:09, RW wrote:
> 
> > > I see what's happened. Earlier in the year,against my better
> > > judgement, I move to CURRENT in futile attempt to make intel KMS
> > > work. It looks like fuse has been moved into the base system,
> > > but /etc/rc.d/ hasn't yet been updated to reflect that. 
> > >
> > 
> > There isn't an /etc/rc.d/ for every kernel module. If you want to use
> > fuse on FreeBSD 10 and later just put fuse_load="YES" in loader.conf.
> > The rc.d script in the port was just a nice courtesy. I don't think
> > it's likely we'll see an /etc/rc.d/fuse script appear in the base
> > system.
> 
> I have added it to loader.conf, but the reason I brought it up was that
> I thought the documentation might be out of date, which appears to be
> the case. 
> 
> If nothing's been decided I can't really submit a documentation
> patch.
> 
> If anyone's interested the relevant files are:
> 
> sysutils/ntfsprogs/files/README.FreeBSD
> sysutils/fusefs-ntfs/files/README.FreeBSD
> 

I forgot about the READMEs that come with those ports. We might want to
mention FreeBSD 10+ specific setup there I guess.
___
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: pkgng+portmaster: portmaster erased the field packages.time

[Yuri]

On 08/22/2013 04:49, Bryan Drewery wrote:

By "Packages.time" I assume you mean the timestamp the package was
installed? There is no "conversion" timestamp stored by pkgng.


After pkg2ng has ran, all fields packages.time were !=null. This was 
probably the original install time then.




How are you seeing this timestamp? With 'pkg query "%o %t"'?


I use firefox plugin to look into .sqlite file directly.



Portmaster itself is not modifying this data at all (it can't), only
pkgng updates this timestamp.



After portmaster ran, I observed all package.time fields became null, 
except for the ones updated by portmaster.

I am not sure who deleted them, this is what happened after portmaster ran.

Yuri
___
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: pkgng+portmaster: portmaster erased the field packages.time

[Yuri]

On 08/22/2013 04:49, Bryan Drewery wrote:

By "Packages.time" I assume you mean the timestamp the package was
installed? There is no "conversion" timestamp stored by pkgng.


After pkg2ng has ran, all fields packages.time were !=null. This was 
probably the original install time then.




How are you seeing this timestamp? With 'pkg query "%o %t"'?


I use firefox plugin to look into .sqlite file directly.



Portmaster itself is not modifying this data at all (it can't), only
pkgng updates this timestamp.



After portmaster ran, I observed all package.time fields became null, 
except for the ones updated by portmaster.

I am not sure who deleted them, this is what happened after portmaster ran.

Yuri
___
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: building seamonkey with clang

[Cary]

On Wed, Aug 21, 2013 at 07:10:05PM +, Cary wrote:
> On Wed, Aug 21, 2013 at 05:29:28PM +0200, Dimitry Andric wrote:
> > On Aug 21, 2013, at 13:23, Cary  wrote:
> > > On Wed, Aug 21, 2013 at 06:50:45AM +, Cary wrote:
> > >> On Tue, Aug 20, 2013 at 11:05:42PM +0200, Dimitry Andric 
> > >> wrote:
> > >>> On Aug 20, 2013, at 00:54, Cary  wrote:
> >  Several attempts to build the current port of seamonkey on 9.1-release 
> >  have 
> >  all failed at the same point.
> >  I have rebuilt clang and have no idea what else
> >  can be done.
> >  Here is the error:
> >  
> >  
> >  Assertion failed: (isa(Val) && "Unknown live-in to the entry 
> >  block"),
> >  function solveBlockValueNonLocal, file 
> >  /usr/src/lib/clang/libllvmanalysis/../../
> >  ../contrib/llvm/lib/Analysis/LazyValueInfo.cpp, line 605.
> > >>> 
> > >>> This is clang 3.1, so meanwhile the assert will most likely have been
> > >>> fixed.  Can you try building one of the lang/clang ports, and build the
> > >>> seamonkey port with that instead?
> > >>> 
> > >>> -Dimitry
> > 
> > However, out of interest, I would like to determine the exact upstream
> > revision which fixed it.  Could you please send me files that clang++
> > mentioned in your original post (if you still have them):
> > 
> >   clang++: note: diagnostic msg: /tmp/nsMsgMaildirStore-SbFLtj.ii
> >   clang++: note: diagnostic msg: /tmp/nsMsgMaildirStore-SbFLtj.sh
> > 
> > -Dimitry
> > 
> > 
> Still building the port.  The files you requested should be available 
> here:
> http://filebin.ca/sJ7l6KWpOr3/tmp-2.20.tar.gz
> 
http://filebin.ca was not available last I looked.
The file tmp-2.20.tar.gz is attached now for
anyone who might need to use it.
-- 
c...@sdf.org
SDF Public Access UNIX System - http://sdf.org
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"