Re: snort fails to build

2014-11-06 Thread Christopher Burns
Thanks!  I thought I searched the tickets for snort but obviously missed that 
one.

> On Nov 6, 2014, at 9:44 PM, Marius Schamschula  wrote:
> 
> Chris,
> 
> See https://trac.macports.org/ticket/42531 
>  for the current status of snort.
> 
> On Nov 6, 2014, at 7:51 PM, Christopher Burns  > wrote:
> 
>> Hello All,
>> 
>> I was using snort from macports on Mavericks, however after migrating to 
>> Yosemite and updating/compiling macports, snort no longer installs.
>> 
>> Regrettably, it appears there is no maintainer for snort (port info 
>> --maintainers snort -> maintainers: nomaintai...@macports.org 
>> .)
>> 
>> The failure seems to occur when it is building the plugins, 
>> :info:build make[3]: Entering directory 
>> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_snort/snort/work/snort-2.9.1.2/src/output-plugins'
>> ...
>> DPREPROCESSOR_AND_DECODER_RULE_EVENTS -DPPM_MGR -DENABLE_PAF -DENABLE_REACT 
>> -DENABLE_RESPOND -DENABLE_RESPONSE3 -DSF_WCHAR -DSUP_IP6 -DTARGET_BASED 
>> -DPERF_PROFILING -DSNORT_RELOAD -DNORMALIZER -DACTIVE_RESPONSE  -pipe -Os 
>> -arch x86_64 -DSF_VISIBILITY -fvisibility=hidden -Wall -c 
>> spo_alert_unixsock.c
>> :info:build In file included from spo_alert_syslog.c:70:
>> :info:build ../../src/strlcatu.h:24:8: error: expected parameter declarator
>> :info:build size_t strlcat(char *, const char *, size_t);
>> ...more errors...
>> 
>> Does anyone know of a workaround or if there is a new maintainer of this 
>> port?
>> 
>> Thanks,
>> Chris
>> ___
>> macports-users mailing list
>> macports-users@lists.macosforge.org 
>> 
>> https://lists.macosforge.org/mailman/listinfo/macports-users
> 
> 
> Marius
> --
> Marius Schamschula
> 
> 
> 

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: snort fails to build

2014-11-06 Thread Marius Schamschula
Chris,

See https://trac.macports.org/ticket/42531 for the current status of snort.

On Nov 6, 2014, at 7:51 PM, Christopher Burns  wrote:

> Hello All,
> 
> I was using snort from macports on Mavericks, however after migrating to 
> Yosemite and updating/compiling macports, snort no longer installs.
> 
> Regrettably, it appears there is no maintainer for snort (port info 
> --maintainers snort -> maintainers: nomaintai...@macports.org.)
> 
> The failure seems to occur when it is building the plugins, 
> :info:build make[3]: Entering directory 
> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_snort/snort/work/snort-2.9.1.2/src/output-plugins'
> ...
> DPREPROCESSOR_AND_DECODER_RULE_EVENTS -DPPM_MGR -DENABLE_PAF -DENABLE_REACT 
> -DENABLE_RESPOND -DENABLE_RESPONSE3 -DSF_WCHAR -DSUP_IP6 -DTARGET_BASED 
> -DPERF_PROFILING -DSNORT_RELOAD -DNORMALIZER -DACTIVE_RESPONSE  -pipe -Os 
> -arch x86_64 -DSF_VISIBILITY -fvisibility=hidden -Wall -c spo_alert_unixsock.c
> :info:build In file included from spo_alert_syslog.c:70:
> :info:build ../../src/strlcatu.h:24:8: error: expected parameter declarator
> :info:build size_t strlcat(char *, const char *, size_t);
> ...more errors...
> 
> Does anyone know of a workaround or if there is a new maintainer of this port?
> 
> Thanks,
> Chris
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users


Marius
--
Marius Schamschula



___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


snort fails to build

2014-11-06 Thread Christopher Burns
Hello All,

I was using snort from macports on Mavericks, however after migrating to 
Yosemite and updating/compiling macports, snort no longer installs.

Regrettably, it appears there is no maintainer for snort (port info 
--maintainers snort -> maintainers: nomaintai...@macports.org 
.)

The failure seems to occur when it is building the plugins, 
:info:build make[3]: Entering directory 
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_snort/snort/work/snort-2.9.1.2/src/output-plugins'
...
DPREPROCESSOR_AND_DECODER_RULE_EVENTS -DPPM_MGR -DENABLE_PAF -DENABLE_REACT 
-DENABLE_RESPOND -DENABLE_RESPONSE3 -DSF_WCHAR -DSUP_IP6 -DTARGET_BASED 
-DPERF_PROFILING -DSNORT_RELOAD -DNORMALIZER -DACTIVE_RESPONSE  -pipe -Os -arch 
x86_64 -DSF_VISIBILITY -fvisibility=hidden -Wall -c spo_alert_unixsock.c
:info:build In file included from spo_alert_syslog.c:70:
:info:build ../../src/strlcatu.h:24:8: error: expected parameter declarator
:info:build size_t strlcat(char *, const char *, size_t);
...more errors...

Does anyone know of a workaround or if there is a new maintainer of this port?

Thanks,
Chris___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: Case-sensitive file system

2014-11-06 Thread Ned Deily
In article <8d2d8233-983b-4edf-bcbb-23431d7f2...@macports.org>,
 Vincent Habchi  wrote:
> Le 6 nov. 2014 à 21:20, Dave Horsfall  a écrit :
> > There was a discussion here on the Mac's case-sensitive-but-not-quite file 
> > system, and I was convinced to leave it the way it is (it breaks something 
> > in MacPorts or something).  Well, I've just been convinced otherwise…
> I’ve been running MacPorts on a case-sensitive HFS+ disk for years now, and 
> it works like a charm. Don’t let you gull by the grapevine!

So have I: since OS X 10.5, in fact.  I don't recall ever encountering a 
MacPorts-related problem with using case-sensitive HFS.  In the past, I 
ran into a few problems with older (non-MacPorts) third-party Mac 
applications that did not work properly on case-sensitive HFS+, usually 
because of some silly mistyped mixed-case file name inside of the app 
bundle.  Some discussion of a few recent apps here:

http://apple.stackexchange.com/questions/46322/what-programs-have-trouble
-with-case-sensitive-hfsx-filesystems-and-how-to-fi

That said, I haven't noticed a problem in years and I use case-sensitive 
HFS as the root file systems on all of my primary systems.  I also use 
default, case-insensitive HFS on other test systems.

-- 
 Ned Deily,
 n...@acm.org

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: Case-sensitive file system

2014-11-06 Thread Lawrence Velázquez
On Nov 6, 2014, at 3:34 PM, Vincent Habchi  wrote:

> Le 6 nov. 2014 à 21:20, Dave Horsfall  a écrit :
>> 
>> There was a discussion here on the Mac's case-sensitive-but-not-quite file 
>> system, and I was convinced to leave it the way it is (it breaks something 
>> in MacPorts or something).  Well, I've just been convinced otherwise…
> 
> I’ve been running MacPorts on a case-sensitive HFS+ disk for years now, and 
> it works like a charm. Don’t let you gull by the grapevine!

And our buildslaves all have HFS+X.

If you encounter an issue using MacPorts on HFS+X, please report it, as we'd 
consider it a bug.

vq
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: Case-sensitive file system

2014-11-06 Thread René J . V . Bertin
On Friday November 07 2014 07:20:43 Dave Horsfall wrote:

> There was a discussion here on the Mac's case-sensitive-but-not-quite file 
> system, and I was convinced to leave it the way it is (it breaks something 
> in MacPorts or something).  Well, I've just been convinced otherwise...

MacPorts works just fine on a case-sensitive fs. The only time things go wrong 
is when a binary package/tarball hasn't been created correctly, in which case 
the same kind of aliasing as you encountered occurs.

For backing up BSD servers to a Mac, you might be interested in this: 
www.o3x.org .

R.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: Case-sensitive file system

2014-11-06 Thread Vincent Habchi
Le 6 nov. 2014 à 21:20, Dave Horsfall  a écrit :
> 
> There was a discussion here on the Mac's case-sensitive-but-not-quite file 
> system, and I was convinced to leave it the way it is (it breaks something 
> in MacPorts or something).  Well, I've just been convinced otherwise…

I’ve been running MacPorts on a case-sensitive HFS+ disk for years now, and it 
works like a charm. Don’t let you gull by the grapevine!

> Dave Horsfall DTM (VK2KFU)  "Bliss is a MacBook with a FreeBSD server. »

73s de F5RCS!


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: Case-sensitive file system

2014-11-06 Thread Clemens Lang
Hi,

- On 6 Nov, 2014, at 21:20, Dave Horsfall d...@horsfall.org wrote:


> I am backing up my FreeBSD server to the MacBook (don't ask) and amongst
> the detritus accumulated last century I found this:
> 
> aneurin% ls -l
> total 60
> -rw-r--r--  1 dave  wheel  14414 Jul 18  2000 CHANGES
> -rw-r--r--  1 dave  wheel   5510 Jul 18  2000 EXAMPLES
> -rw-r--r--  1 dave  wheel  23253 Jul 18  2000 README
> -rw-r--r--  1 dave  wheel   5973 Jul 18  2000 UPDATE
> drwxr-xr-x  3 dave  wheel512 Jul 18  2000 examples
> drwxr-xr-x  2 dave  wheel512 Jul 18  2000 hack
> drwxr-xr-x  2 dave  wheel512 Jul 18  2000 html
> drwxr-xr-x  2 dave  wheel512 Jul 18  2000 patch
> 
> See the problem?  Sigh...

You can always use a sparse disk image with case-sensitive HFS+ (or a
completely different case-sensitive file system, for that matter) as
backup target. In fact, due to OS X' somewhat weird choices on UTF-8
normalization that might in fact not be a bad idea.

-- 
Clemens Lang
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Case-sensitive file system

2014-11-06 Thread Dave Horsfall
There was a discussion here on the Mac's case-sensitive-but-not-quite file 
system, and I was convinced to leave it the way it is (it breaks something 
in MacPorts or something).  Well, I've just been convinced otherwise...

I am backing up my FreeBSD server to the MacBook (don't ask) and amongst 
the detritus accumulated last century I found this:

aneurin% ls -l
total 60
-rw-r--r--  1 dave  wheel  14414 Jul 18  2000 CHANGES
-rw-r--r--  1 dave  wheel   5510 Jul 18  2000 EXAMPLES
-rw-r--r--  1 dave  wheel  23253 Jul 18  2000 README
-rw-r--r--  1 dave  wheel   5973 Jul 18  2000 UPDATE
drwxr-xr-x  3 dave  wheel512 Jul 18  2000 examples
drwxr-xr-x  2 dave  wheel512 Jul 18  2000 hack
drwxr-xr-x  2 dave  wheel512 Jul 18  2000 html
drwxr-xr-x  2 dave  wheel512 Jul 18  2000 patch

See the problem?  Sigh...

-- 
Dave Horsfall DTM (VK2KFU)  "Bliss is a MacBook with a FreeBSD server."
http://www.horsfall.org/spam.html (and check the home page whilst you're there)
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: Yosemite buildbot?

2014-11-06 Thread Ryan Schmidt
On Nov 6, 2014, at 12:27 PM, Sean Farley wrote:

> Brandon Allbery writes:
> 
>> On Sun, Oct 19, 2014 at 8:52 PM, Jason Mitchell wrote:
>> 
>>> Is there a buildbot in the works for Yosemite ports?  I checked
>>> https://build.macports.org/buildslaves but didn't see anything for
>>> Yosemite yet.  Maybe I've  misunderstood the process, or am just being
>>> greedy?
>> 
>> It was requested; they're waiting on Apple to provision it.
> 
> Any update on this?

We were told yesterday that Apple provided the necessary resources, and Shree 
was working on setting it up. Of course, once it's set up and building, it'll 
still take several weeks to build everything.

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: Yosemite buildbot?

2014-11-06 Thread Sean Farley

Brandon Allbery writes:

> On Sun, Oct 19, 2014 at 8:52 PM, Jason Mitchell 
> wrote:
>
>> Is there a buildbot in the works for Yosemite ports?  I checked
>> https://build.macports.org/buildslaves but didn't see anything for
>> Yosemite yet.  Maybe I've  misunderstood the process, or am just being
>> greedy?
>>
>
> It was requested; they're waiting on Apple to provision it.

Any update on this?
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users