Am 20.07.2013 01:23 schrieb "Anton Shterenlikht" :
>
> https://redports.org/~mexas/2013071921-42286-133205/libtool-2.4.2.log
>
> My port is actually astro/xearth, which,
> I think, doesn't even need a libtool.
> A successful build of xearth is e.g.:
> https://redports.org/~mexas/2013071921-
On Fri, Jul 19, 2013 at 5:03 PM, Kenta Suzumoto wrote:
> Screenfetch is a bash script for system information, similar to
> sysutils/bsdinfo but MANY more features
> and much more actively developed. Would anyone be interested in
> maintaining it in ports and keeping
> it up to date as new version
Screenfetch is a bash script for system information, similar to
sysutils/bsdinfo but MANY more features
and much more actively developed. Would anyone be interested in maintaining it
in ports and keeping
it up to date as new versions are released? Seems like an easy port. Thanks to
anyone who he
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-07-19 15:39:09 -0400, Mike Jakubik wrote:
> On 07/19/13 14:28, Jung-uk Kim wrote:
>> I had the same problem last night and made a patch.
>>
>> http://people.freebsd.org/~jkim/patch-clang
>>
>> Drop this file in files directory and try it agai
Thanks Evan but this is not the case, clang flag is set.
clang++ '-D_FILE_OFFSET_BITS=64' '-DNO_TCMALLOC' '-DDISABLE_NACL'
'-DCHROMIUM_BUILD' '-DUSE_DEFAULT_RENDER_THEME=1' '-DUSE_LIBJPEG_TURBO=1'
'-DUSE_NSS=1' '-DUSE_X11=1' '-DENABLE_ONE_CLICK_SIGNIN'
'-DGTK_DISABLE_SINGLE_INCLUDES=1' '-DENABLE_R
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-07-19 14:28:48 -0400, Evan Martin wrote:
> I asked the Chrome clang masters on your behalf and got this
> answer:
> https://groups.google.com/a/chromium.org/d/topic/clang/YEdQW6NTghY/discussion
No,
>
that's the case here. In fact, we had th
https://redports.org/~mexas/2013071921-42286-133205/libtool-2.4.2.log
My port is actually astro/xearth, which,
I think, doesn't even need a libtool.
A successful build of xearth is e.g.:
https://redports.org/~mexas/2013071921-42286-133209/xearth-1.2.log
What's going on?
BTW, right now re
On Fri, Jul 19, 2013 at 04:46:48PM +0100, Anton Shterenlikht wrote:
> I noticed that some ports create directories/files
> under /root:
>
> drwxr-xr-x 3 root wheel 512 Mar 19 2012 .subversion
> drwxr-xr-x 2 root wheel 512 Mar 4 10:23 .qt
>
> drwxr-xr-x 2 root wheel 512 Jul 10 15:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-07-19 14:41:15 -0400, Jung-uk Kim wrote:
> On 2013-07-19 14:28:48 -0400, Evan Martin wrote:
>> I asked the Chrome clang masters on your behalf and got this
>> answer:
>> https://groups.google.com/a/chromium.org/d/topic/clang/YEdQW6NTghY/discu
On 07/19/13 14:28, Jung-uk Kim wrote:
I had the same problem last night and made a patch.
http://people.freebsd.org/~jkim/patch-clang
Drop this file in files directory and try it again.
Jung-uk Kim
This patch works, chromium compiles and seems to run without any issues.
Thank you.
On Fri, 19 Jul 2013, Anton Shterenlikht wrote:
I noticed that some ports create directories/files
under /root:
drwxr-xr-x 3 root wheel 512 Mar 19 2012 .subversion
drwxr-xr-x 2 root wheel 512 Mar 4 10:23 .qt
drwxr-xr-x 2 root wheel 512 Jul 10 15:27 .astkrc
drwxr-xr-x 2 root
I asked the Chrome clang masters on your behalf and got this answer:
https://groups.google.com/a/chromium.org/d/topic/clang/YEdQW6NTghY/discussion
On Fri, Jul 19, 2013 at 11:22 AM, George Liaskos wrote:
> Yes, unfortunately clang build is currently broken.
>
> This is why we switched the port bac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-07-19 13:43:48 -0400, Mike Jakubik wrote:
> Hello,
>
> Latest Chromium does not seem to compile with Clang 3.3.
>
> CXX(target)
> out/Release/obj.target/v8_base.x64/v8/src/string-search.o
> CXX(target)
> out/Release/obj.target/v8_base.x64/v8
Hello,
Latest Chromium does not seem to compile with Clang 3.3.
CXX(target) out/Release/obj.target/v8_base.x64/v8/src/string-search.o
CXX(target) out/Release/obj.target/v8_base.x64/v8/src/string-stream.o
CXX(target) out/Release/obj.target/v8_base.x64/v8/src/strtod.o
CXX(target) out/Relea
Yes, unfortunately clang build is currently broken.
This is why we switched the port back to gcc by default until we figure out
how to handle all the different clang && base version combinations...
___
freebsd-ports@freebsd.org mailing list
http://lists.
I noticed that some ports create directories/files
under /root:
drwxr-xr-x 3 root wheel 512 Mar 19 2012 .subversion
drwxr-xr-x 2 root wheel 512 Mar 4 10:23 .qt
drwxr-xr-x 2 root wheel 512 Jul 10 15:27 .astkrc
drwxr-xr-x 2 root wheel 512 Jul 10 15:27 flasheur
(these two are p
Last I heard fortran@ was going to maintain it.
On Fri, Jul 19, 2013 at 11:42 AM, Anton Shterenlikht wrote:
>
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "fr
___
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 am using gcc46 to build ports.
Port configuration:
===> The following configuration options are available for curl-7.31.0:
CA_BUNDLE=on: Install CA bundle for OpenSSL
COOKIES=on: Cookies support
CURL_DEBUG=off: cURL debug memory tracking
DEBUG=off: Install debug symbols
On 07/04/13 04:16, bw.mail.lists wrote:
> I'm not sure when it happened, I think since latest pkgng upgrade,
> version 1.1.3, but pkgng now acts differently in at least two cases.
>
> 1. pkg upgrade -f
> What happens:
>
> -
> /root # pkg upgrade -f
> Updating repository catalogue
Marko, can you try this?
http://feld.me/freebsd/rt-extension-mandatoryontransition.tar.gz
Thanks!
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubsc
On 07/18/13 00:38, Rodrigo OSORIO wrote:
On 18/07/13 00:40 +1000, R Skinner wrote:
This has been a real fiasco to send one around the bend.
I'm trying to quickly submit a port and I used the send-pr this time and
attached my shar as opposed to using the web form, except my sendmail is
being rej
- add dependency on archivers/lzo2 to enable lzo compression
(just replace compression=GZIP with compression=LZO in Options) [1]
- replace rmdir with ${RMDIR} added in previous commit (portlint warning)
- correct bacula UPDATING entry [2]
PR: 178691
Submitted by: Oleg Ginzburg [1]
On 19/07/2013 15:49, O. Hartmann wrote:
Please CC me if some hints or solutions are available.
I have just submitted a patch to update osl to 1.3.3 - pr/180650
The release notes say "Changes to support LLVM 3.3" but I haven't
confirmed that it fixes the 10 compile yet.
_
Ports-QAT wrote on 19.07.2013 14:01:
- move bacula configuration to ${ETCDIR}/bacula
- bump PORTREVISION
- add UPDATING entry
- add an option to enable python support (both client and server
need to be rebuilt with this)
[...]
Port:sysutils/bacula-server 5.2.12_1
B
- move bacula configuration to ${ETCDIR}/bacula
- bump PORTREVISION
- add UPDATING entry
- add an option to enable python support (both client and server
need to be rebuilt with this)
Dan's submission is based on:
PR: 170882
Submitted by: Michael Carlson
PR: 171818
Submitted by: Fl
| 20130719
+-+
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
Hi,
since yesterday devel/pear will not fetch:
===> Fetching all distfiles required by pear-1.9.4_2 for building
=> SHA256 Checksum mismatch for pear-1.9.4.tar.bz2.
===> Refetch for 1 more times files: pear-1.9.4.tar.bz2
=> pear-1.9.4.tar.bz2 doesn't seem to exist in /distfiles/.
=> A
On 2013-07-18 21:33, olli hauer wrote:
> On 2013-07-18 21:09, Baptiste Daroussin wrote:
>> On Thu, Jul 18, 2013 at 09:04:09PM +0200, olli hauer wrote:
>>> Hm, I just picked the bugzilla44 port and struggle over the logs.
>>>
===> de-bugzilla-4.4 conflicts with installed package(s):
29 matches
Mail list logo
