Works for me !
2013/5/21 Hiroki Sato :
> Hiroki Sato wrote
> in <20130519.070840.2265196291393572686@allbsd.org>:
>
> hr> "Christopher J. Ruwe" wrote
> hr> in <20130518025801.0659b...@dijkstra.cruwe.de>:
> hr>
> hr> cj> I have included the patches, they are rather trivial, although, I
>
Please open the attached Notepad to view my order.
Quotation Needed.rtf
Description: Binary data
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr..
On 05/21/13 07:02, Cy Schubert wrote:
> Hi,
>
> I'm experiencing firefox crashes since updating to 21.0.
Me too. For me, it'll run ok for a while and then when I bring up a new
tab or actively do something with the UI it will crash unexpectedly.
Happening approximately every few minutes of active
Hi,
Since we are back on normal rolling packages update for stable and I got
pointyhat-west up to do some testing, I would like to move on with this case.
I just wonder if someone already has a patch to make it as default, else I will
have a look at it within this week.
- Martin
On Mar 15, 20
Hi,
JFYI, freebsd-tex mailing list[*] has been created for discussing TeX
related ports. If you are interested in porting and/or have
questions about TeX and its applications on FreeBSD, please subscribe
it.
[*] http://lists.freebsd.org/mailman/listinfo/freebsd-tex
-- Hiroki
pgpc7NvU7WAP
In message <201305220036.r4m0aip4020...@slippy.cwsent.com>, Cy Schubert
writes:
> In message <997344171-1369083778-cardhu_decombobulator_blackberry.rim.net-10
> 735
> 04366-@b17.c23.bise6.blackberry>, "Cy Schubert" writes:
> > Hi,
> >
> > I'm experiencing firefox crashes since updating to 21.0. I
In message <997344171-1369083778-cardhu_decombobulator_blackberry.rim.net-10
735
04366-@b17.c23.bise6.blackberry>, "Cy Schubert" writes:
> Hi,
>
> I'm experiencing firefox crashes since updating to 21.0. It works properly fo
> llowing the restore of my ~/.mozilla directory however subsequently it
Is any one else having a problem[1] building kdelibs4 since the update to
KDE 4.10.3? I'm seeing the same error on three different machines. Any
clues how to fix?
[1] http://mail.kde.org/pipermail/kde-freebsd/2013-May/015369.html
--
Greg Rivers
___
Howdy,
I added an option for mutt integration to the notmuch port via
notmuch-mutt. I've attached a tarball of all the modifications,
but here is a list of modified files:
Makefile
pkg-plist
files/patch-notmuch-mutt
Here are some references for more information:
notmuch-mutt: http://not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-05-21 18:11:23 -0400, John Marino wrote:
> On 5/21/2013 23:05, Jung-uk Kim wrote:
>> Can you please explain the most common incompatibilities you
>> experienced from dports?
>>
>> FYI, I have added these two shims for FreeBSD:
>>
>> http://s
On 5/21/2013 23:05, Jung-uk Kim wrote:
Can you please explain the most common incompatibilities you
experienced from dports?
FYI, I have added these two shims for FreeBSD:
http://svnweb.freebsd.org/changeset/base/250877
http://svnweb.freebsd.org/changeset/base/250878
With these two shims, I wa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-05-21 16:30:48 -0400, John Marino wrote:
> On 5/21/2013 22:03, Jung-uk Kim wrote:
>> Please note flex/lex was updated to 2.5.37 from
>> flex.sourceforge.net and __FreeBSD_version was bumped to
>> 133.
>>
>> FYI, I added couple of compatibi
On 5/21/2013 22:03, Jung-uk Kim wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please note flex/lex was updated to 2.5.37 from flex.sourceforge.net and
__FreeBSD_version was bumped to 133.
FYI, I added couple of compatibility shims (just enough to build the
previous source trees) but
Am 21.05.2013 13:31, schrieb Michael Gmelin:
> I had the same problem yesterday in a clean jail:
>
> cd /usr/ports/devel/python33
> make install
>
> It stopped with lots of error messages, I was too tired to care
> and just ran
>
> make install
>
> once again and then it worked.
> (no update o
On Tue, May 21, 2013 at 04:03:44PM -0400, Jung-uk Kim wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Please note flex/lex was updated to 2.5.37 from flex.sourceforge.net and
> __FreeBSD_version was bumped to 133.
>
> FYI, I added couple of compatibility shims (just enough to bui
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please note flex/lex was updated to 2.5.37 from flex.sourceforge.net and
__FreeBSD_version was bumped to 133.
FYI, I added couple of compatibility shims (just enough to build the
previous source trees) but it is not 100% compatible with the old
ve
Hi!
current llvm-devel failed to build under FreeBSD 10-HEAD:
llvm[2]: Compiling SemaStmt.cpp for Release build
llvm[2]: Compiling Tools.cpp for Release build
Tools.cpp: In member function 'virtual void
clang::driver::tools::Clang::ConstructJob(clang::driver::Compilation&,
const clang::driver::Jo
On Tue, May 21, 2013 at 10:53:14PM +0800, Martin Wilke wrote:
> known issue, set USE_GCC=any in the qt4-corelib Makefile and it will builds
> ...
Thank you for that, but I still see a failure:
dwolf-bsd(9.1-S)[15] cd /usr/ports/
dwolf-bsd(9.1-S)[16] svn info
Path: .
Working Copy Root Path: /commo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/21/13 12:14 PM, Greg Larkin wrote:
>
> Greetings,
>
> A while back, I started working on ports for the vagrant
> (http://www.vagrantup.com/) and veewee
> (https://github.com/jedi4ever/veewee) tools. At the time, vagrant
> was packaged as a Ru
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greetings,
A while back, I started working on ports for the vagrant
(http://www.vagrantup.com/) and veewee
(https://github.com/jedi4ever/veewee) tools. At the time, vagrant was
packaged as a Ruby gem with a variety of other gem dependencies. Some
o
known issue, set USE_GCC=any in the qt4-corelib Makefile and it will builds
On May 20, 2013, at 9:54 AM, David Wolfskill wrote:
> On a system running: FreeBSD 9.1-STABLE #80 r250806: Sun May 19 04:54:21
> PDT 2013 i386, I was performing my usual weekly update/refresh -- at
> this point, "portmast
Hello,
I'm testing your patch for libmodbus. Unfortunatelly there is many
changes between 2.x and current 3.x version of libmodbus. So evene
enabling modbus plugin to collectd4 there is problem with configure
script.
So this should be modified by collectd project - i.e. modbus_new_tcp
which repla
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
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting
each other in the packages/Latest directory. If your ports confli
Update to 0.96.
Changes:http://search.cpan.org/dist/Imager/Changes
-
Build ID: 20130521114600-6515
Job owner: to...@freebsd.org
Buildtime: 7 minutes
Enddate: Tue, 21 May 2013 11:
On Tue, 21 May 2013 09:03:01 +0200
Albert Shih wrote:
> Le 21/05/2013 ? 08:54:37+0400, Ruslan Makhmatkhanov a écrit
> > Hi,
> >
> > Albert Shih wrote on 19.05.2013 20:29:
> > > Hi all
> > >
> > > Just report the
> > >
> > >
> > > /usr/ports/lang/python33
> > >
> > > don't build on
> > >
>
Hello,
just a short heads-up to inform you that as of r318663, the default
version of Tcl/Tk used in the ports tree is 8.6.
Best,
--
Pietro Cerutti
The FreeBSD Project
g...@freebsd.org
PGP Public Key:
http://gahr.ch/pgp
pgpp3teESn_Me.pgp
Description: PGP signature
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as "forbidden" in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
exploits.
An overview of each port, inclu
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. The most common probl
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. The most common probl
Hiroki Sato wrote
in <20130519.070840.2265196291393572686@allbsd.org>:
hr> "Christopher J. Ruwe" wrote
hr> in <20130518025801.0659b...@dijkstra.cruwe.de>:
hr>
hr> cj> I have included the patches, they are rather trivial, although, I
hr> cj> think, dirty. I have also included a complete l
Le 21/05/2013 ? 08:54:37+0400, Ruslan Makhmatkhanov a écrit
> Hi,
>
> Albert Shih wrote on 19.05.2013 20:29:
> > Hi all
> >
> > Just report the
> >
> >
> > /usr/ports/lang/python33
> >
> > don't build on
> >
> > FreeBSD 9.1-STABLE #3 r250807: Sun May 19 17:48:52 CEST 2013
> >
> > all ot
32 matches
Mail list logo
