Paul Schmehl wrote:
I'm working on a port update for one of the ports that I maintain, and I've run
into a problem that I can't seem to solve.
I use this construction to ensure that the port doesn't overwrite the conf
file, if one exists:
.for f in barnyard2.conf
${INSTALL_DATA} ${WR
Boris Kochergin wrote:
Eitan Adler wrote:
Can anyone with FreeBSD 8.1-RC1 i386 or FreeBSD 8.1-RC2 i386 confirm
that the following code compiles and fails with the version of clang++
from ports?
This works with g++ and fails with clang++ for me.
Here is the original code
#include
int main()
{
Eitan Adler wrote:
Can anyone with FreeBSD 8.1-RC1 i386 or FreeBSD 8.1-RC2 i386 confirm
that the following code compiles and fails with the version of clang++
from ports?
This works with g++ and fails with clang++ for me.
Here is the original code
#include
int main()
{
std::cout << 1;
r
Can anyone with FreeBSD 8.1-RC1 i386 or FreeBSD 8.1-RC2 i386 confirm
that the following code compiles and fails with the version of clang++
from ports?
This works with g++ and fails with clang++ for me.
Here is the original code
#include
int main()
{
std::cout << 1;
return 1;
}
My bug re
See below for the changes to sudo 1.7.3 which is set to be released
soon. If you want to test out the 1.7.3rc1 update please fetch the patch
from http://people.freebsd.org/~wxs/sudo.diff, apply it and rebuild.
Please reply back to me privately with reports of success or failures.
I'll probably get
Em 2010.06.29. 0:24, Paul Schmehl escreveu:
I'm working on a port update for one of the ports that I maintain, and
I've run into a problem that I can't seem to solve.
I use this construction to ensure that the port doesn't overwrite the
conf file, if one exists:
.for f in barnyard2.conf
I'm working on a port update for one of the ports that I maintain, and I've run
into a problem that I can't seem to solve.
I use this construction to ensure that the port doesn't overwrite the conf
file, if one exists:
.for f in barnyard2.conf
${INSTALL_DATA} ${WRKSRC}/etc/${f} ${PREFI
On Mon, Jun 28, 2010 at 09:19:05PM +0200, Andrea Venturoli wrote:
> Any news on updating this port?
They're unmaintained, so it's probably up to you to do it :-)
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/fr
Hello.
Any news on updating this port?
Latest version is 2.3.9.2.
We have:
net/Sockets = 2.1.4
net/Sockets-devel = 1.9.9 (!!!)
Is anyone working on this?
If not I might give a try at updating this port.
bye & Thanks
av.
___
freebsd-ports@free
On Sun, 27 Jun 2010 23:09:47 -0400
Eitan Adler wrote:
> I'd like to add a flag to tell ports that you are building only for
> yourself that and optimizations that typically are not enabled could
> be turned on.
You can do this yourself. If you add in make.conf something like
.if defined(BUILD_F
> Any case where it would be useful besides -march/-mtune/-mmmx/-msse*?
>
Not that I could think of at the moment. I think this solution works better.
--
Eitan Adler
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/
2010/6/28 Olivier Cochard-Labbé :
> patch ../../UIDs UIDs.diff
> patch ../../GIDs GIDs.diff
>
> For information:
> I've used the UID/GID 139 that seem available.
Oh, bother. I was getting ready to use that for mail/ecartis
(ecartis:ecartis). OK, I'll find another slot.
Jim
_
Olivier Cochard-Labbé wrote:
> Thanks for your tips, I've updated the port
Looks good. Works with --disable-ssl on my VirtualBox (but, as before,
not without it).
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebs
2010/6/28 Vitaly Magerya :
>
> So what I propose is this:
> 1. Create "shellinabox" user and group (via USERS and GROUPS).
> 2. Update rc script to start shellinaboxd with that user and group.
> 3. Make the certificate directory 700, owned by shellinabox:shellinabox.
Thanks for your tips, I've up
> From: Vitaly Magerya
[SNIP]
> 4. Move the certificate directory to /var/shellinabox or similar
>(what's our conventional location for this kind of files?).
>
> I'm not sure on the 4 though. Any thoughts?
Id say possibly /var/db/shellinabox
/var/db/ seems to be used by a fair number of ser
(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 27/06/2010 20:04, Lev Serebryakov wrote:
> Hello, Freebsd-ports.
>
> I understand, that this change (ports/137855, bsd.port.mk:1.632) was
> made 6 months ago, but I've
> noticed it only now (twice in one day!).
>
> Am I only person, who thinks, that this change is HUGE POL
Dear porters,
This is just a reminder to please periodically check the list of
unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ .
A list by MAINTAINER is
http://people.freebsd.org/~fenner/errorlogs/
so you can easily check the status of ports that you maintain. In
addition, the li
Olivier Cochard-Labbé wrote:
> I've just finished my port of Shell in a Box: It's a secure web server
> that provide ajax terminal emulator.
> More information on the official website:
> http://code.google.com/p/shellinabox/
After looking at the port for a while, I have some suggestions.
The por
19 matches
Mail list logo
