Hi Steven,
thanks for that fast help.
> undefined reference to `__stack_chk_guard'
Mmh google points me to that code example [1], that looks like thy symbol
should be defined in stdio.h - strange
Futher searching around I also found the svn of freebsd port for ocsync and
their patches [2]. I a
So I don't forget, and for anyone else interested, here were some
suggestions recently from DSA when I asked how we could make life easier
for them.
Missing features / things to document better in the Wiki FAQ:
http://dsa.debian.org/ports/kfreebsd/
also pflogd was mentioned in the past, I may wor
On 00:04, Sandro Knauß wrote:
> /«PKGBUILDDIR»/src/std/c_private.h:74:19: error: expected identifier before
> numeric constant
> #define O_NOATIME 0
Hi Sandro,
This should help:
--- src/std/c_private.h.orig2013-09-04 10:15:42.0 +0100
+++ src/std/c_private.h 2013-09-19 00:16:47.3778
On 19/09/13 00:07, Robert Millan wrote:
> How does pre-processed source look like?
I didn't see anything odd about it...
But never mind. I tried with Clang and got a different error that makes
more sense. Probably fcntl.h isn't being included until later:
> In file included from /home/steven/o
Steven Chamberlain:
> Hi!
>
> On 18/09/13 23:04, Sandro Knauß wrote:
>> /«PKGBUILDDIR»/src/std/c_private.h:74:19: error: expected identifier before
>> numeric constant
>> #define O_NOATIME 0
>
> I must be missing something obvious... how could it fail here?
>
> src/std/c_private.h:73:
>> #ifnd
Hi!
On 18/09/13 23:04, Sandro Knauß wrote:
> /«PKGBUILDDIR»/src/std/c_private.h:74:19: error: expected identifier before
> numeric constant
> #define O_NOATIME 0
I must be missing something obvious... how could it fail here?
src/std/c_private.h:73:
> #ifndef O_NOATIME
> #define O_NOATIME 0
> #
Hey,
I really like to get owncloud-client running in bsd. Two build-deps are not
build in freebsd.
till now building ocsync fails with [1]:
/«PKGBUILDDIR»/src/std/c_private.h:74:19: error: expected identifier before
numeric constant
#define O_NOATIME 0
Maybe you can help developing a patch
Hi Steven,
Steven Chamberlain:
> For our kernels and maybe more, perhaps it would be beneficial to make
> sure builds are deterministic, or at least, try to produce identical
> output on every build from the same source.
>
> The security rationale is that the build system can be audited this way
Hi,
For our kernels and maybe more, perhaps it would be beneficial to make
sure builds are deterministic, or at least, try to produce identical
output on every build from the same source.
The security rationale is that the build system can be audited this way,
by someone else running a build on t
On 17/09/13 17:59, Petr Salinger wrote:
> Just give it a try and plug/unplug USB keyboard ;-)
Hah. This is something I never would have thought to test for, and a
lot of my systems don't use a USB keyboard anyway. It's surprising if
this were some risky optimisation that it didn't affect somethi
Petr Salinger:
>> I presume that using -O2 shouldn't be an issue with kfreebsd-10 now that
>> it is using clang (thinking about #718250 et al).
>>
>> Is there any concern about doing this?
>> Some advice would be appreciated (specially from Petr)
>
> Just give it a try and plug/unplug USB keyboard
11 matches
Mail list logo