On Fri, Mar 26, 2010 at 05:26:03PM -0700, Xin LI wrote:
This is wrong, FreeBSD has native 64-bit stat() etc. and does not need
_LARGEFILE_WHATEVER.
Yes we do not need that and it just cause compilation errors.
The problem is that some third party software thinks that they need to
define
It seems to stop with mozilla. All ports are up to date. This is the
only one that won't build for us on 7.3.
c++ -o nsHtml5NamedCharacters.o -c -I../../dist/system_wrappers
-include ../../config/gcc_hidden.h -DMOZILLA_INTERNAL_API
-D_IMPL_NS_COM -DEXPORT_XPT_API -DEXPORT_XPTC_API
On 3/27/10 2:46 PM, eculp wrote:
It seems to stop with mozilla. All ports are up to date. This is the
only one that won't build for us on 7.3.
c++ -o nsHtml5NamedCharacters.o -c -I../../dist/system_wrappers -include
../../config/gcc_hidden.h -DMOZILLA_INTERNAL_API -D_IMPL_NS_COM
Hi,
I was wondering why LyX in the FreeBSD ports isn't upgraded anymore. The
current version in ports is still 1.5.7, but the latest LyX version is
1.6.5. The version in ports is 1,5 years old.
Regards,
Marco
--
In every hierarchy the cream rises until it sours.
-- Dr.
Le Saturday 27 Mar 2010 à 17:32:42 (+0100), Marco Beishuizen a écrit :
Hi,
I was wondering why LyX in the FreeBSD ports isn't upgraded anymore. The
current version in ports is still 1.5.7, but the latest LyX version is
1.6.5. The version in ports is 1,5 years old.
Probably because noone
On Sat 27 Mar 2010 at 09:34:54 PDT Baptiste Daroussin wrote:
Le Saturday 27 Mar 2010 à 17:32:42 (+0100), Marco Beishuizen a écrit :
Hi,
I was wondering why LyX in the FreeBSD ports isn't upgraded anymore. The
current version in ports is still 1.5.7, but the latest LyX version is
1.6.5. The
Quoting Florian Smeets f...@smeets.im:
On 3/27/10 2:46 PM, eculp wrote:
It seems to stop with mozilla. All ports are up to date. This is the
only one that won't build for us on 7.3.
c++ -o nsHtml5NamedCharacters.o -c -I../../dist/system_wrappers -include
../../config/gcc_hidden.h
On 03/27/10 21:49, eculp wrote:
Quoting daniele gl...@live.com:
HI !
do you get any system message similar to swap_pager_getswapspace(2):
failed ?
d
Hi Daniele,
I just greped the log files on both machines for swap and found nothing.
I'm going to keep looking at swap and memory.
Thanks,
This is the error I'm getting (both with cvsup8 and cvsup.freebsd.org)
Connecting to cvsup.FreeBSD.org
Connected to 72.233.193.64
Server software version: SNAP_16_1h
Negotiating file attribute support
Exchanging collection information
Establishing multiplexed-mode data connection
Running
The error:
# Parsing supfile /etc/cvsupfile
Connecting to cvsup.FreeBSD.org
Connected to 72.233.193.64
Server software version: SNAP_16_1h
Negotiating file attribute support
Exchanging collection information
Establishing multiplexed-mode data connection
Running
Updating collection ports-all/cvs
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
On 03/27/10 14:50, Tim Kellers wrote:
This is the error I'm getting (both with cvsup8 and cvsup.freebsd.org)
Connecting to cvsup.FreeBSD.org
Connected to 72.233.193.64
Server software version: SNAP_16_1h
Negotiating file attribute support
Doug Barton wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
On 03/27/10 14:50, Tim Kellers wrote:
This is the error I'm getting (both with cvsup8 and cvsup.freebsd.org)
Connecting to cvsup.FreeBSD.org
Connected to 72.233.193.64
Server software version: SNAP_16_1h
Negotiating file
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
On 03/27/10 16:02, Tim Kellers wrote:
Thanks. rm -rf ports/audio/aureal-kmod/ did the trick
If that's true you probably have other errors that you don't know about.
Make sure you run csup without the -s option on a regular basis to make
sure
Doug Barton wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
On 03/27/10 16:02, Tim Kellers wrote:
Thanks. rm -rf ports/audio/aureal-kmod/ did the trick
If that's true you probably have other errors that you don't know about.
Make sure you run csup without the -s option on
14 matches
Mail list logo