Hello Chris,
I think I really have to start reading through this waf book. Thanks
again for the hint. You can find a second version of the patch which
uses the subst rule as a reply to this mail.
But before the patch gets merged, we maybe should wait till Sichen has
the port of openssl ready. I'l
Am 25.07.2017 um 00:16 schrieb Chris Johns:
> On 25/07/2017 03:09, Christian Mauderer wrote:
>> Hm. It seems for me that the subst would substitute some text in a
>> source file with some other text and generate a target from it. So that
>> most likely could be a nice replacement for the network-co
On 25/07/2017 03:09, Christian Mauderer wrote:
> Hm. It seems for me that the subst would substitute some text in a
> source file with some other text and generate a target from it. So that
> most likely could be a nice replacement for the network-config.h (which
> is just above my new rule and use
Am 24.07.2017 um 09:11 schrieb Christian Mauderer:
>
>
> Am 24.07.2017 um 08:59 schrieb Chris Johns:
>> On 24/07/2017 00:20, Christian Mauderer wrote:
>>> Am 23.07.2017 um 15:57 schrieb Gedare Bloom:
On Sun, Jul 23, 2017 at 8:38 AM, Christian Mauderer
wrote:
> The problem here i
Am 24.07.2017 um 08:59 schrieb Chris Johns:
> On 24/07/2017 00:20, Christian Mauderer wrote:
>> Am 23.07.2017 um 15:57 schrieb Gedare Bloom:
>>> On Sun, Jul 23, 2017 at 8:38 AM, Christian Mauderer
>>> wrote:
The problem here is that the opensslv.h is in the directory
freebsd/crypto/op
On 24/07/2017 00:20, Christian Mauderer wrote:
> Am 23.07.2017 um 15:57 schrieb Gedare Bloom:
>> On Sun, Jul 23, 2017 at 8:38 AM, Christian Mauderer
>> wrote:
>>> The problem here is that the opensslv.h is in the directory
>>> freebsd/crypto/openssl/crypto. It seems that some makefile magic would
Am 23.07.2017 um 15:57 schrieb Gedare Bloom:
> On Sun, Jul 23, 2017 at 8:38 AM, Christian Mauderer
> wrote:
>> Am 23.07.2017 um 14:05 schrieb Gedare Bloom:
>>> On Sun, Jul 23, 2017 at 8:04 AM, Gedare Bloom wrote:
On Sun, Jul 23, 2017 at 7:49 AM, Gedare Bloom wrote:
> On Sat, Jul 22,
On Sun, Jul 23, 2017 at 8:38 AM, Christian Mauderer wrote:
> Am 23.07.2017 um 14:05 schrieb Gedare Bloom:
>> On Sun, Jul 23, 2017 at 8:04 AM, Gedare Bloom wrote:
>>> On Sun, Jul 23, 2017 at 7:49 AM, Gedare Bloom wrote:
On Sat, Jul 22, 2017 at 1:30 PM, Christian Mauderer
wrote:
>
Am 23.07.2017 um 14:05 schrieb Gedare Bloom:
> On Sun, Jul 23, 2017 at 8:04 AM, Gedare Bloom wrote:
>> On Sun, Jul 23, 2017 at 7:49 AM, Gedare Bloom wrote:
>>> On Sat, Jul 22, 2017 at 1:30 PM, Christian Mauderer
>>> wrote:
Hello Sichen,
as discussed in our private chat I'm quite
On Sun, Jul 23, 2017 at 8:04 AM, Gedare Bloom wrote:
> On Sun, Jul 23, 2017 at 7:49 AM, Gedare Bloom wrote:
>> On Sat, Jul 22, 2017 at 1:30 PM, Christian Mauderer
>> wrote:
>>> Hello Sichen,
>>>
>>> as discussed in our private chat I'm quite convinced that your problem
>>> is that the source fi
On Sun, Jul 23, 2017 at 7:49 AM, Gedare Bloom wrote:
> On Sat, Jul 22, 2017 at 1:30 PM, Christian Mauderer
> wrote:
>> Hello Sichen,
>>
>> as discussed in our private chat I'm quite convinced that your problem
>> is that the source file is in "freebsd/crypto/openssl/crypto" which
>> doesn't end
On Sat, Jul 22, 2017 at 1:30 PM, Christian Mauderer wrote:
> Hello Sichen,
>
> as discussed in our private chat I'm quite convinced that your problem
> is that the source file is in "freebsd/crypto/openssl/crypto" which
> doesn't end on a path called "openssl".
>
> As far as I can see, there is cu
Hello Sichen,
as discussed in our private chat I'm quite convinced that your problem
is that the source file is in "freebsd/crypto/openssl/crypto" which
doesn't end on a path called "openssl".
As far as I can see, there is currently no support in our build system
for such cases. I created a (stil
13 matches
Mail list logo
