On 4/16/21 10:53 AM, Hans Petter Selasky wrote:
On 7/9/18 10:08 AM, Koichiro Iwao wrote:
On Mon, Jul 09, 2018 at 04:59:38PM +0900, 山田真由 wrote:
My port is located at http://taurus.ics.nara-wu.ac.jp/my/
403
Works for me.
Hi,
Forgot to look at the e-mail date :-)
Please ignore :-)
--HPS
On 7/9/18 10:08 AM, Koichiro Iwao wrote:
On Mon, Jul 09, 2018 at 04:59:38PM +0900, 山田真由 wrote:
My port is located at http://taurus.ics.nara-wu.ac.jp/my/
403
Works for me.
--HPS
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/
Thank you !
2018-07-11 0:04 GMT+09:00 Kurt Jaeger :
> Hi!
>
> > I'm sorry.
> > The URL was wrong.
> >
> > The correct URL is http://taurus.ics.nara-wu.ac.
> jp/my/singular-port.tar.gz
>
> It was committed with quite a few modifications, see:
>
> https://lists.freebsd.org/pipermail/svn-ports-all/2
Hi!
> I'm sorry.
> The URL was wrong.
>
> The correct URL is http://taurus.ics.nara-wu.ac.jp/my/singular-port.tar.gz
It was committed with quite a few modifications, see:
https://lists.freebsd.org/pipermail/svn-ports-all/2018-July/187954.html
--
p...@opsec.eu+49 171 3101372
I'm sorry.
The URL was wrong.
The correct URL is http://taurus.ics.nara-wu.ac.jp/my/singular-port.tar.gz
Thank you!!
> Hello!
>
> The first install the Ports Collection and put my port under /usr/ports/math/
> and then compile it as usual.
>
> My port is located at http://taurus.ics.nara-wu.
On Mon, Jul 09, 2018 at 04:59:38PM +0900, 山田真由 wrote:
> My port is located at http://taurus.ics.nara-wu.ac.jp/my/
403
--
meta
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any
On Sat, May 12, 2012 at 8:58 AM, Leslie Jensen wrote:
>
>
> 2012-05-12 16:19, RW skrev:
>
>> On Sat, 12 May 2012 14:16:58 +0200
>> Leslie Jensen wrote:
>>
>>>
>>>
>>> 2012-05-12 12:34, Colin Percival skrev:
On 05/12/12 00:22, Leslie Jensen wrote:
>
> host -t srv _http._tcp.geodns
2012-05-12 16:19, RW skrev:
On Sat, 12 May 2012 14:16:58 +0200
Leslie Jensen wrote:
2012-05-12 12:34, Colin Percival skrev:
On 05/12/12 00:22, Leslie Jensen wrote:
host -t srv _http._tcp.geodns.portsnap.freebsd.org
;; Truncated, retrying in TCP mode.
;; Connection to 172.17.0.1#53(172.17.
On Sat, 12 May 2012 14:16:58 +0200
Leslie Jensen wrote:
>
>
> 2012-05-12 12:34, Colin Percival skrev:
> > On 05/12/12 00:22, Leslie Jensen wrote:
> >> host -t srv _http._tcp.geodns.portsnap.freebsd.org
> >> ;; Truncated, retrying in TCP mode.
> >> ;; Connection to 172.17.0.1#53(172.17.0.1) for
>
On 05/12/12 05:16, Leslie Jensen wrote:
> 2012-05-12 12:34, Colin Percival skrev:
>> On 05/12/12 00:22, Leslie Jensen wrote:
>>> host -t srv _http._tcp.geodns.portsnap.freebsd.org
>>> ;; Truncated, retrying in TCP mode.
>>> ;; Connection to 172.17.0.1#53(172.17.0.1) for
>>> _http._tcp.geodns.portsn
2012-05-12 12:34, Colin Percival skrev:
On 05/12/12 00:22, Leslie Jensen wrote:
host -t srv _http._tcp.geodns.portsnap.freebsd.org
;; Truncated, retrying in TCP mode.
;; Connection to 172.17.0.1#53(172.17.0.1) for
_http._tcp.geodns.portsnap.freebsd.org failed: connection refused.
Ok, you hav
On 05/12/12 00:22, Leslie Jensen wrote:
> host -t srv _http._tcp.geodns.portsnap.freebsd.org
> ;; Truncated, retrying in TCP mode.
> ;; Connection to 172.17.0.1#53(172.17.0.1) for
> _http._tcp.geodns.portsnap.freebsd.org failed: connection refused.
Ok, you have a broken recursive DNS server config
2012-05-12 09:04, Colin Percival skrev:
On 05/12/12 00:02, Leslie Jensen wrote:
portsnap fetch -s geodns.portsnap.freebsd.org
Looking up geodns.portsnap.freebsd.org mirrors... none found.
Fetching snapshot tag from geodns.portsnap.freebsd.org... failed.
No mirrors remaining, giving up.
Hmm,
On 05/12/12 00:02, Leslie Jensen wrote:
> portsnap fetch -s geodns.portsnap.freebsd.org
> Looking up geodns.portsnap.freebsd.org mirrors... none found.
> Fetching snapshot tag from geodns.portsnap.freebsd.org... failed.
> No mirrors remaining, giving up.
Hmm, that's not good. What do
# host -t sr
2012-05-12 05:54, Colin Percival skrev:
Hi all,
Please test:
# portsnap fetch -s geodns.portsnap.freebsd.org
If you experience any problems, please let me know where you are, which mirror
was selected, and what address `host -t a $mirror` returns for it. (As the
name suggests, different peop
On 5/12/2012 1:13 AM, Jason Hellenthal wrote:
>
> On Fri, May 11, 2012 at 09:55:13PM -0700, Colin Percival wrote:
>> > On 05/11/12 21:54, Jason Hellenthal wrote:
>>> > > There is no A record @8.8.8.8 or @8.8.4.4 or at the root servers.
>> >
>> > There's not supposed to be an A record. Portsnap
On Fri, May 11, 2012 at 09:55:13PM -0700, Colin Percival wrote:
> On 05/11/12 21:54, Jason Hellenthal wrote:
> > There is no A record @8.8.8.8 or @8.8.4.4 or at the root servers.
>
> There's not supposed to be an A record. Portsnap should work
> anyway... it uses SRV. :-)
Aaah! you got me ther
On 05/11/12 21:54, Jason Hellenthal wrote:
> There is no A record @8.8.8.8 or @8.8.4.4 or at the root servers.
There's not supposed to be an A record. Portsnap should work
anyway... it uses SRV. :-)
--
Colin Percival
Security Officer, FreeBSD | freebsd.org | The power to serve
Founder / author,
There is no A record @8.8.8.8 or @8.8.4.4 or at the root servers.
or here:
dig +short @72.52.71.1 geodns.portsnap.freebsd.org A
dig +short @38.103.2.1 geodns.portsnap.freebsd.org A
dig +short @63.243.194.1 geodns.portsnap.freebsd.org A
Maybe this hasnt propogated yet ? or is it @ 127.0.0.1 ;)
O
On 02/18/2012 19:03, Mark Linimon wrote:
> On Sat, Feb 18, 2012 at 03:59:37PM -0800, Doug Barton wrote:
>> Where I think reasonable minds can differ are (appropriate) responses of
>> the form, "This was not done properly, here is how it can/should be done
>> (better)." IMO those should *always* be
On Sat, Feb 18, 2012 at 03:59:37PM -0800, Doug Barton wrote:
> Where I think reasonable minds can differ are (appropriate) responses of
> the form, "This was not done properly, here is how it can/should be done
> (better)." IMO those should *always* be public in order to help others
> who are payin
On 02/17/2012 10:22, Mark Linimon wrote:
> On Sun, Feb 12, 2012 at 08:35:05PM +, Michael Scheidell wrote:
>> Public flogging seems to be more enjoyable than a private email to the
>> developer, the maintainer, and a committer.
>
> I know we are all a little frustrated with some of the local co
On Sun, Feb 12, 2012 at 03:22:38PM -0600, Stephen Montgomery-Smith wrote:
> Also, if everyone starts using [redports], isn't the backlog going to
> become huge?
We're working on getting more hardware.
Having something become "too successful" is a problem we should be happy
to have :)
mcl
___
On Sun, Feb 12, 2012 at 08:35:05PM +, Michael Scheidell wrote:
> Public flogging seems to be more enjoyable than a private email to the
> developer, the maintainer, and a committer.
I know we are all a little frustrated with some of the local commits, but
remember:
"praise in public, critic
On 02/14/12 08:40, b. f. wrote:
On 12.02.2012 22:43, Stephen Montgomery-Smith wrote:
On 02/12/2012 03:33 PM, Andriy Gapon wrote:
on 12/02/2012 23:22 Stephen Montgomery-Smith said the following:
On 02/12/2012 03:15 PM, Andriy Gapon wrote:
Today I became another user of redports.org. I can de
> On 12.02.2012 22:43, Stephen Montgomery-Smith wrote:
> > On 02/12/2012 03:33 PM, Andriy Gapon wrote:
> >> on 12/02/2012 23:22 Stephen Montgomery-Smith said the following:
> >>> On 02/12/2012 03:15 PM, Andriy Gapon wrote:
> >>>
> Today I became another user of redports.org. I can definitely
On 12.02.2012 22:43, Stephen Montgomery-Smith wrote:
On 02/12/2012 03:33 PM, Andriy Gapon wrote:
on 12/02/2012 23:22 Stephen Montgomery-Smith said the following:
On 02/12/2012 03:15 PM, Andriy Gapon wrote:
Today I became another user of redports.org. I can definitely
recommend it.
Yes, but
On Sun, 12 Feb 2012 21:48:57 +0100 (CET)
Jimmy Olgeni articulated:
>
> On Sun, 12 Feb 2012, Stephen Montgomery-Smith wrote:
>
> > You should report which version of FreeBSD you are using. It might
> > have tested OK for the committer, but not for you.
>
> I'm watching a tinderbox run right now
On 12 Feb 2012 21:37, "Steve Kargl"
wrote:
>
> On Sun, Feb 12, 2012 at 03:32:52PM -0600, Stephen Montgomery-Smith wrote:
> > >
> > >But, the 2nd issue with too many arguments in a function call is
> > >clearly evident on amd64 because I justed test that on FreeBSD 10.
> >
> > Yes. But the issue i
On 02/12/2012 03:33 PM, Andriy Gapon wrote:
on 12/02/2012 23:22 Stephen Montgomery-Smith said the following:
On 02/12/2012 03:15 PM, Andriy Gapon wrote:
Today I became another user of redports.org. I can definitely recommend it.
Yes, but it is not without its problems. I tried testing math
On Sun, Feb 12, 2012 at 03:32:52PM -0600, Stephen Montgomery-Smith wrote:
> >
> >But, the 2nd issue with too many arguments in a function call is
> >clearly evident on amd64 because I justed test that on FreeBSD 10.
>
> Yes. But the issue isn't whether someone else was correct in why the
> port
on 12/02/2012 23:17 Steve Kargl said the following:
> Empirical evidence suggests that ghostscript9 developers are using
> a newer version of the autotools.
>
> laptop:root[262] find . -name configure | xargs grep -i "freebsd\[1" | more
> ./lcms/configure:freebsd[123].*) objformat=aout ;;
> ./
on 12/02/2012 23:22 Stephen Montgomery-Smith said the following:
> On 02/12/2012 03:15 PM, Andriy Gapon wrote:
>
>> Today I became another user of redports.org. I can definitely recommend it.
>
> Yes, but it is not without its problems. I tried testing math/sage on
> redports.org. It reported
On 02/12/2012 03:17 PM, Steve Kargl wrote:
On Sun, Feb 12, 2012 at 08:52:56PM +, Chris Rees wrote:
On 12 Feb 2012 20:45, "Steve Kargl"
wrote:
laptop:root[252] uname -a
FreeBSD laptop 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r230975M: Sat Feb 4
09:03:27 PST 2012 root@laptop:/usr/obj/usr
On 02/12/2012 03:15 PM, Andriy Gapon wrote:
Today I became another user of redports.org. I can definitely recommend it.
Yes, but it is not without its problems. I tried testing math/sage on
redports.org. It reported an error building the dependency math/atlas,
which built fine on mine and
On Sun, 12 Feb 2012, Stephen Montgomery-Smith wrote:
You should report which version of FreeBSD you are using. It might have
tested OK for the committer, but not for you.
I'm watching a tinderbox run right now and it seems to fail on i386
only; amd64 looks ok.
I just sent a full log to th
On Sun, Feb 12, 2012 at 08:52:56PM +, Chris Rees wrote:
> On 12 Feb 2012 20:45, "Steve Kargl"
> wrote:
> >
> >
> > laptop:root[252] uname -a
> > FreeBSD laptop 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r230975M: Sat Feb 4
> 09:03:27 PST 2012 root@laptop:/usr/obj/usr/src/sys/MOBILE i386
>
>
on 12/02/2012 22:45 Stephen Montgomery-Smith said the following:
> On 02/12/2012 02:41 PM, Steve Kargl wrote:
>> On Sun, Feb 12, 2012 at 10:27:25PM +0200, Andriy Gapon wrote:
>>> on 12/02/2012 22:16 Steve Kargl said the following:
You seem to have the faulty belief that this is the first occur
On 12 Feb 2012 20:45, "Steve Kargl"
wrote:
>
> On Sun, Feb 12, 2012 at 08:44:11PM +, Chris Rees wrote:
> > On 12 Feb 2012 20:41, "Steve Kargl"
> > wrote:
> > >
> > > On Sun, Feb 12, 2012 at 10:27:25PM +0200, Andriy Gapon wrote:
> > > > on 12/02/2012 22:16 Steve Kargl said the following:
> > >
On Sun, 12 Feb 2012 20:35:05 +
Michael Scheidell articulated:
> Public flogging seems to be more enjoyable than a private email to
> the developer, the maintainer, and a committer.
>
> But I suppose it beats doing a backup of your envirement first.
I put it right up there with "Top Posting"
on 12/02/2012 22:41 Steve Kargl said the following:
> On Sun, Feb 12, 2012 at 10:27:25PM +0200, Andriy Gapon wrote:
>> on 12/02/2012 22:16 Steve Kargl said the following:
>>> You seem to have the faulty belief that this is the first occurence
>>> of this type of issue?
>>
>> So instead of proper re
On 02/12/2012 02:41 PM, Steve Kargl wrote:
On Sun, Feb 12, 2012 at 10:27:25PM +0200, Andriy Gapon wrote:
on 12/02/2012 22:16 Steve Kargl said the following:
You seem to have the faulty belief that this is the first occurence
of this type of issue?
So instead of proper report to the port's mai
On Sun, Feb 12, 2012 at 08:44:11PM +, Chris Rees wrote:
> On 12 Feb 2012 20:41, "Steve Kargl"
> wrote:
> >
> > On Sun, Feb 12, 2012 at 10:27:25PM +0200, Andriy Gapon wrote:
> > > on 12/02/2012 22:16 Steve Kargl said the following:
> > > > You seem to have the faulty belief that this is the fir
On 12 Feb 2012 20:41, "Steve Kargl"
wrote:
>
> On Sun, Feb 12, 2012 at 10:27:25PM +0200, Andriy Gapon wrote:
> > on 12/02/2012 22:16 Steve Kargl said the following:
> > > You seem to have the faulty belief that this is the first occurence
> > > of this type of issue?
> >
> > So instead of proper r
On Sun, Feb 12, 2012 at 10:27:25PM +0200, Andriy Gapon wrote:
> on 12/02/2012 22:16 Steve Kargl said the following:
> > You seem to have the faulty belief that this is the first occurence
> > of this type of issue?
>
> So instead of proper report to the port's maintainer (including description of
rgl
Cc: "freebsd-ports@FreeBSD.org" , Chris Rees
Sent: Sun, Feb 12, 2012 20:28:23 GMT+00:00
Subject: Re: Please test your commits
on 12/02/2012 22:16 Steve Kargl said the following:
> You seem to have the faulty belief that this is the first occurence
> of this type of issue?
S
On 02/12/2012 01:39 PM, Steve Kargl wrote:
Is there any reguirement that a ports committer needs
to test their intended commit prior to pulling the
trigger?
http://www.freebsd.org/cgi/cvsweb.cgi/ports/print/ghostscript9/Makefile
You should report which version of FreeBSD you are using. It mi
on 12/02/2012 22:16 Steve Kargl said the following:
> You seem to have the faulty belief that this is the first occurence
> of this type of issue?
So instead of proper report to the port's maintainer (including description of
your environment, possibly full build log, etc), possibly with a CC here
On Sun, Feb 12, 2012 at 08:03:28PM +, Chris Rees wrote:
> On 12 Feb 2012 19:39, "Steve Kargl"
> wrote:
> >
> > Is there any reguirement that a ports committer needs
> > to test their intended commit prior to pulling the
> > trigger?
> >
>
> Could this not have gone directly to the 'offending'
On 12 Feb 2012 19:39, "Steve Kargl"
wrote:
>
> Is there any reguirement that a ports committer needs
> to test their intended commit prior to pulling the
> trigger?
>
Could this not have gone directly to the 'offending' developer?
Chris
___
freebsd-por
Hi,
Ion-Mihai Tetcu wrote:
On Tue, 01 Jul 2008 15:19:29 +0300
Stefan Lambrev <[EMAIL PROTECTED]> wrote:
Greetings Ion-Mihai,
Ion-Mihai Tetcu wrote:
On Tue, 01 Jul 2008 13:38:49 +0300
Stefan Lambrev <[EMAIL PROTECTED]> wrote:
[ .. ]
===> Patching for apcupsd-3.14.4
===>
On Mon, Jun 23, 2008 at 12:19:33AM +0200, Juergen Lock wrote:
> On Fri, Jun 20, 2008 at 11:12:16PM +0200, Juergen Lock wrote:
> > Hi!
> >
> > I've been playing with a qemu-devel update again recently (which also
> > includes a kqemu api change, therefore I have a new kqemu-kmod-devel
> > port too
On Tue, 01 Jul 2008 15:19:29 +0300
Stefan Lambrev <[EMAIL PROTECTED]> wrote:
> Greetings Ion-Mihai,
>
> Ion-Mihai Tetcu wrote:
> > On Tue, 01 Jul 2008 13:38:49 +0300
> > Stefan Lambrev <[EMAIL PROTECTED]> wrote:
> >
> > [ .. ]
> >
> >
> >> ===> Patching for apcupsd-3.14.4
> >> ===> Applying
Greetings Ion-Mihai,
Ion-Mihai Tetcu wrote:
On Tue, 01 Jul 2008 13:38:49 +0300
Stefan Lambrev <[EMAIL PROTECTED]> wrote:
[ .. ]
===> Patching for apcupsd-3.14.4
===> Applying FreeBSD patches for apcupsd-3.14.4
Ignoring previously applied (or reversed) patch.
3 out of 3 hunks ignored--sav
On Tue, 01 Jul 2008 13:38:49 +0300
Stefan Lambrev <[EMAIL PROTECTED]> wrote:
[ .. ]
> ===> Patching for apcupsd-3.14.4
> ===> Applying FreeBSD patches for apcupsd-3.14.4
> Ignoring previously applied (or reversed) patch.
> 3 out of 3 hunks ignored--saving rejects to
> ./src/drivers/usb/bsd/bsd
Hi,
Sorry I didn't reply earlier.
Ion-Mihai Tetcu wrote:
Hi,
At:
http://t32.tecnik93.com/FreeBSD/ports/apcupsd/port/apcupsd-3.14.3_2-to-3.14.4.diff
you'll find a diff (also attached to this mail) which updates
sysutlis/apcupsd to the latest stable version.
cd /usr/ports/sysutils/apcupsd && \
On Fri, Jun 20, 2008 at 6:12 PM, Juergen Lock <[EMAIL PROTECTED]> wrote:
> I've been playing with a qemu-devel update again recently (which also
> includes a kqemu api change, therefore I have a new kqemu-kmod-devel
> port too), and these are the main news:
>
> - Many targets including x86 have b
On Fri, Jun 20, 2008 at 11:12:16PM +0200, Juergen Lock wrote:
> Hi!
>
> I've been playing with a qemu-devel update again recently (which also
> includes a kqemu api change, therefore I have a new kqemu-kmod-devel
> port too), and these are the main news:
>
> - Many targets including x86 have bee
On Tue, 4 Mar 2008 23:38:22 +0100
Juergen Lock <[EMAIL PROTECTED]> wrote:
> On Sun, Mar 02, 2008 at 09:21:20PM +0100, Juergen Lock wrote:
> > Hi!
> >
> > Anyway the update is here (also queued on tb3):
> > http://people.freebsd.org/~nox/qemu/qemu-devel-20080302.patch
>
> Updated patch avail
On Sun, Mar 02, 2008 at 09:21:20PM +0100, Juergen Lock wrote:
> Hi!
>
> Again, interesting things are happening in the qemu development tree,
> among others the ncurses patch has been committed (allowing to see
> vga text output without sdl by passing -curses), e1000 emulation i.e.
> an emulated
Juergen Lock <[EMAIL PROTECTED]> writes:
> Anyway the update is here (also queued on tb3):
> http://people.freebsd.org/~nox/qemu/qemu-devel-20080302.patch
I just gave it a test run with a FreeBSD guest, and it seems to work
like expected.
The curses option is awesome. Now I can run my tex
On Thu, 08 Nov 2007 15:03:37 -0600, Kevin Oberman <[EMAIL PROTECTED]> wrote:
Date: Wed, 7 Nov 2007 22:42:57 -0800
From: "Kevin Downey" <[EMAIL PROTECTED]>
On Nov 7, 2007 10:02 PM, Kevin Downey <[EMAIL PROTECTED]> wrote:
>
> On Nov 7, 2007 8:25 PM, Kevin Oberman <[EMAIL PROTECTED]> wrote:
> > >
> Date: Wed, 7 Nov 2007 22:42:57 -0800
> From: "Kevin Downey" <[EMAIL PROTECTED]>
>
> On Nov 7, 2007 10:02 PM, Kevin Downey <[EMAIL PROTECTED]> wrote:
> >
> > On Nov 7, 2007 8:25 PM, Kevin Oberman <[EMAIL PROTECTED]> wrote:
> > > > Date: Thu, 8 Nov 2007 11:12:49 +0900
> > > > From: "Thomas Zander"
> Date: Thu, 8 Nov 2007 11:12:49 +0900
> From: "Thomas Zander" <[EMAIL PROTECTED]>
>
> On 07/11/2007, Kevin Oberman <[EMAIL PROTECTED]> wrote:
>
> > 'acodec=aac' worked in the version now in ports, although that version
> > failed to write the header with a floating point error. :-(
>
> Does thi
> Date: Wed, 7 Nov 2007 22:42:57 -0800
> From: "Kevin Downey" <[EMAIL PROTECTED]>
>
> On Nov 7, 2007 10:02 PM, Kevin Downey <[EMAIL PROTECTED]> wrote:
> >
> > On Nov 7, 2007 8:25 PM, Kevin Oberman <[EMAIL PROTECTED]> wrote:
> > > > Date: Thu, 8 Nov 2007 11:12:49 +0900
> > > > From: "Thomas Zander"
On Nov 7, 2007 10:02 PM, Kevin Downey <[EMAIL PROTECTED]> wrote:
>
> On Nov 7, 2007 8:25 PM, Kevin Oberman <[EMAIL PROTECTED]> wrote:
> > > Date: Thu, 8 Nov 2007 11:12:49 +0900
> > > From: "Thomas Zander" <[EMAIL PROTECTED]>
> > >
> > > On 07/11/2007, Kevin Oberman <[EMAIL PROTECTED]> wrote:
> > >
On Nov 7, 2007 8:25 PM, Kevin Oberman <[EMAIL PROTECTED]> wrote:
> > Date: Thu, 8 Nov 2007 11:12:49 +0900
> > From: "Thomas Zander" <[EMAIL PROTECTED]>
> >
> > On 07/11/2007, Kevin Oberman <[EMAIL PROTECTED]> wrote:
> >
> > > 'acodec=aac' worked in the version now in ports, although that version
>
> Date: Thu, 8 Nov 2007 11:12:49 +0900
> From: "Thomas Zander" <[EMAIL PROTECTED]>
>
> On 07/11/2007, Kevin Oberman <[EMAIL PROTECTED]> wrote:
>
> > 'acodec=aac' worked in the version now in ports, although that version
> > failed to write the header with a floating point error. :-(
>
> Does thi
On 07/11/2007, Kevin Oberman <[EMAIL PROTECTED]> wrote:
> 'acodec=aac' worked in the version now in ports, although that version
> failed to write the header with a floating point error. :-(
Does this mean it has never been in a really useful state?
Riggs
> Hi,
>
> the mplayer developers recently released the 1.0 rc 2 version of their
> well known product.
> I updated the mplayer and mencoder ports accordingly and attached them
> to this mail.
> Any feedback/patches are appreciated before I'm going to send-pr this.
I built mplayer and mencoder and
On 24/10/2007, Angelo Turetta <[EMAIL PROTECTED]> wrote:
> May I ask you: if the software is at 1.0.rc2, why the port version is
> set at 0.99.xx?
Because a healthy numbering scheme (as in 'numbers') is more useful
for correct version tracking than that ludicrous approach some people
are insisting
Thomas Zander wrote:
There it is:
http://www.rrr.de/~riggs/mplayer/m20071021.tar.bz2
May I ask you: if the software is at 1.0.rc2, why the port version is
set at 0.99.xx?
You might want to make some test on your own, but in my experience using
a version like 1.0.r2 is supported by the port s
Yes sorry, my fault. But after cleaning it there is some break again with
stream_dvd.
Cheers Oliver
On Mon, Oct 22, 2007 at 01:07:38PM +0800, Thomas Zander wrote:
> On 22/10/2007, Oliver Herold <[EMAIL PROTECTED]> wrote:
> > 1 out of 1 hunks ignored--saving rejects to
> > loader/dmo/DMO_VideoD
On 21/10/2007, Thomas Zander <[EMAIL PROTECTED]> wrote:
> http://www.rrr.de/~riggs/mplayer/m20071021.tar.bz2
Thank you for all the reports so far.
That looks like a ridiculous amount of build errors on various
configurarions, much worse than I expected. :-/
I hope to get some of them sorted out a
On 22/10/2007, Oliver Herold <[EMAIL PROTECTED]> wrote:
> 1 out of 1 hunks ignored--saving rejects to loader/dmo/DMO_VideoDecoder.c.rej
> => Patch patch-DMO_VideoDecoder.c failed to apply cleanly.
This patch doesn't exist anymore. Did you clean the mplayer port dir
before extracting the tarball?
On 10/21/07, Thomas Zander <[EMAIL PROTECTED]> wrote:
>
> There it is:
>
> http://www.rrr.de/~riggs/mplayer/m20071021.tar.bz2
on 7.0
cc -O2 -fno-strict-aliasing -pipe -march=prescott -O3 -ffast-math
-fomit-frame-pointer -I/usr/local/include -I./libavcodec -I./libavformat
-Wdisabled-optimization
Thomas Zander píše v ne 21. 10. 2007 v 22:57 +0800:
> There it is:
>
> http://www.rrr.de/~riggs/mplayer/m20071021.tar.bz2
Does not build:
cc -I. -I.. -I../libavutil -O2 -fno-strict-aliasing -pipe -O3
-ffast-math -fomit-frame-pointer -I/usr/local/include
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=
On Sunday 21 October 2007, Thomas Zander wrote:
> Hi,
>
> the mplayer developers recently released the 1.0 rc 2 version of
> their well known product.
> I updated the mplayer and mencoder ports accordingly and attached
> them to this mail.
> Any feedback/patches are appreciated before I'm going to
Hi didn't have success
-clean install
-
=> MPlayer-1.0rc2.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/.
=> Attempting to fetch from http://www1.mplayerhq.hu/MPlayer/releases/.
MPlayer-1.0rc2.tar.bz2100% of 9119 kB 114 kBps 00m00s
===> Extracting for
On Sun, 21 Oct 2007, Thomas Zander wrote:
Hi,
the mplayer developers recently released the 1.0 rc 2 version of their
well known product.
I updated the mplayer and mencoder ports accordingly and attached them
to this mail.
Any feedback/patches are appreciated before I'm going to send-pr this.
Thomas Zander píše v ne 21. 10. 2007 v 20:00 +0800:
> the mplayer developers recently released the 1.0 rc 2 version of their
> well known product.
> I updated the mplayer and mencoder ports accordingly and attached them
> to this mail.
> Any feedback/patches are appreciated before I'm going to sen
There it is:
http://www.rrr.de/~riggs/mplayer/m20071021.tar.bz2
Riggs
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
82 matches
Mail list logo
