(Note: an HTML version of this report is available at
http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .)
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsol
On 2008-Dec-28 19:43:37 -0600, Scott D Friedemann wrote:
>I'm not sure how to enable compat.sigaction and would appreciate any
>assistance that can be given. I have a.out compiled into the kernel.
You need COMPAT_43 in your kernel. Any code calling compat.sigaction
is _really_ old - that
Hello,
Real life got in the way, and my amule2 porting efforts had to be put
on hold. Buttime waits for no man, and now aMule 2.2.3 has been
released. So I wil restart my efforts with the newest version.
On Sat, Aug 23, 2008 at 3:05 AM, Dmitry Marakasov wrote:
> No, they are automake's macro lan
Michal Varga wrote:
On Tue, Dec 23, 2008 at 1:48 AM, Garrett Cooper wrote:
On 12/22/08, Gonzalo Martínez-Sanjuan Sánchez wrote:
Hi there!
I have a problem with the enemyterritory port using linux compat layer. The
game has no sound. The only problem I get its this messagge:
--- sound in
I'm building a new machine which I cvsup'd yesterday. I am having trouble
getting the amarok port to compile. here is the end of the compile
failure:
/usr/local/bin/moc ./njbmediadevice.h -o njbmediadevice.moc.cpp
/bin/sh /usr/local/bin/libtool --silent --tag=CXX --mode=compile c++
-DHAVE_CONF
Hello,
Just so it won't be forgotten - the annoying bug in the latest version
(2.4.6*) of portupgrade is still there:
r...@kg-v2# portupgrade -R xterm xscreensaver smartmontools
[Gathering depends for x11/xterm
...
On Mon, 29 Dec 2008 11:47:49 -0500, stan wrote:
> I'm building a new machine which I cvsup'd yesterday. I am having trouble
> getting the amarok port to compile. here is the end of the compile
> failure:
> Can anyne sugest how to resolve this?
amarok was broken with libmtp update to 0.3.1 (ports/12
On Mon, 29 Dec 2008 22:18:04 +0300, Max Brazhnikov wrote:
> On Mon, 29 Dec 2008 11:47:49 -0500, stan wrote:
> > I'm building a new machine which I cvsup'd yesterday. I am having trouble
> > getting the amarok port to compile. here is the end of the compile
> > failure:
> > Can anyne sugest how to r
On Mon, Dec 29, 2008 at 8:18 PM, Max Brazhnikov wrote:
> On Mon, 29 Dec 2008 11:47:49 -0500, stan wrote:
>> I'm building a new machine which I cvsup'd yesterday. I am having trouble
>> getting the amarok port to compile. here is the end of the compile
>> failure:
>> Can anyne sugest how to resolve
* Torfinn Ingolfsen (tin...@gmail.com) wrote:
> >> +USE_GETTEXT= yes
> > Using gettext conditionally like before no longer work?
> I don't really know. What exactly do we gain by using gettext conditionally?
Optional NLS support. Less depends, not installing unneeded locales if
NLS is not needed.
Ok, I have passed the first milestone or two - the aMule 2.2.3 port
now compiles and installs.
During the install step I see this:
if test "amule" = "gettext" \
&& test '' = 'intl-compat.o'; then \
/bin/sh `case "./mkinstalldirs" in /*) echo "./mkinstalldirs" ;; *)
echo ".././m
Hi,
The build which triggered this email is done under tinderbox-2.4.3, on
7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly"
and ccache support, with the "official" up-to-date Ports Tree, with the
following vars set:
NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_
Hi,
The build which triggered this email is done under tinderbox-2.4.3, on
7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly"
and ccache support, with the "official" up-to-date Ports Tree, with the
following vars set:
NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_
Another question: how do I create a diff that removes one of the files
in amule2/files?
I tried
diff -u amule2.org/files/patch-amuleDlg.cpp /dev/null >> amule2.diff
And the diff looks ok:
--- amule2.org/files/patch-amuleDlg.cpp 2006-01-04 06:59:25.0 +0100
+++ /dev/null 2008-12-29 23:22:0
On Mon, Dec 29, 2008 at 1:34 PM, Ricardo Jesus
wrote:
> No need for a patch. It's simply a matter of sysctl.
>
> Take a look here:
> http://linux-bsd-sharing.blogspot.com/2008/12/tip-enable-sound-on-enemy-territory.html
>
Interesting, so it actually got fixed at around the same time. My
apologies
Hello,
I am updating the amule2 port to version 2.2.3, this is the first try.
The patch is attached.
There is (at least) one problem with the patch: it doesn't remove the
file ./files/patch-amuleDlg.cpp. For now, just remove the file
manually.
Doesn't FreeBSDs diff have an option to remove files? I
Which ISC DHCP serverr port should I install? The 2 that I tried are both
marked as broken.
--
One of the main causes of the fall of the roman empire was that, lacking
zero, they had no way to indicate successful termination of their C
programs.
___
fre
stan wrote:
Which ISC DHCP serverr port should I install? The 2 that I tried are both
marked as broken.
I have multiple installations of net/isc-dhcp30-server and find them all
to work fine. Needless to say, it's not marked as broken.
-Boris
___
Boris Kochergin wrote:
> stan wrote:
>> Which ISC DHCP serverr port should I install? The 2 that I tried are both
>> marked as broken.
Update ports, run make config, ensure that you have one and only one
openSSL version selected, try again.
--
Eitan Adler
"Security is increased by designing for
Eitan Adler wrote:
Boris Kochergin wrote:
stan wrote:
Which ISC DHCP serverr port should I install? The 2 that I tried are both
marked as broken.
Update ports, run make config, ensure that you have one and only one
openSSL version selected, try again.
He probably means the
Small update.
On Tue, Dec 30, 2008 at 12:39 AM, Torfinn Ingolfsen wrote:
> Testing: I have tested this patch on FreeBSD 7.1-prerelease / amd64,
> and the amule 2.2.3 port compiles and installs fine.
FWIW, It also compiled, installed and is currently running on FreeBSD
6.4-stable / amd64.
--
Reg
Hi,
The build which triggered this email is done under tinderbox-2.4.3, on
7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly"
and ccache support, with the "official" up-to-date Ports Tree, with the
following vars set:
NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_
Hi,
The build which triggered this email is done under tinderbox-2.4.3, on
7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly"
and ccache support, with the "official" up-to-date Ports Tree, with the
following vars set:
NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_
On Dec 29, 2008, at 6:30 PM, stan wrote:
Which ISC DHCP serverr port should I install? The 2 that I tried are
both
marked as broken.
I've been using
isc-dhcp30-server
without difficulty. It is not marked as broken in my instance of it.
-j
___
Hi,
The build which triggered this email is done under tinderbox-2.4.3, on
7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly"
and ccache support, with the "official" up-to-date Ports Tree, with the
following vars set:
NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_
25 matches
Mail list logo