October 27, 2014
On 10/27/2014 08:28 PM, Andrei Alexandrescu wrote:
> Not sure I understand. So should I change that code in array.d manually
> in order to build the docs? -- Andrei

Until we integrate dlang.org with our CI system things will always break.
_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta
October 27, 2014
On 10/27/14 1:23 PM, Martin Nowak wrote:
> On 10/27/2014 08:24 PM, Andrei Alexandrescu wrote:
>> On 10/27/14 12:09 PM, Martin Nowak wrote:
>>> On 10/27/2014 06:57 AM, Andrei Alexandrescu wrote:
>>>>
>>>> Martin, Sönke, do you think we can bring dub to the point we don't rely
>>>> on machine specifics (i.e. dmd.conf) to build everything? That might
>>>> mean extra options.
>>>
>>> While specifying include and library paths on the dub command line can
>>> definitely be done. Not so sure whether that fits into dub's approach.
>>
>> Fair enough. One possible argument is that setting the compiler entails
>> setting flags, too (because e.g. gdc and dmd have different flags).
>
> Dub has an abstraction shim to unify compiler flags.
> http://code.dlang.org/package-format#build-requirements
> http://code.dlang.org/package-format#build-options
>
> You'd use `dub build -b release` for an optimzed build regardless of
> what compiler you chose.

I see, thanks. That would suggest it would be appropriate to add a -I flag that allows setting the include path for all compilers.

>>> I think it is more a DPL problem setting up a simple build env from
>>> sources requires so many steps.
>>
>> Well the question is how to move forward from where we are.
>
> Improve and use the scripts.
> https://github.com/D-Programming-Language/tools/blob/master/update.sh
> https://github.com/D-Programming-Language/installer/blob/master/bootstrap/bootstrap-dmd.bat
>
>
> The meta repo idea would also help here.
> https://issues.dlang.org/show_bug.cgi?id=11792

Thanks for looking into this.


Andrei
_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta
October 30, 2014
Am 27.10.2014 21:49, schrieb Andrei Alexandrescu:
> On 10/27/14 1:23 PM, Martin Nowak wrote:
>> On 10/27/2014 08:24 PM, Andrei Alexandrescu wrote:
>>> On 10/27/14 12:09 PM, Martin Nowak wrote:
>>>> On 10/27/2014 06:57 AM, Andrei Alexandrescu wrote:
>>>>>
>>>>> Martin, Sönke, do you think we can bring dub to the point we don't rely
>>>>> on machine specifics (i.e. dmd.conf) to build everything? That might
>>>>> mean extra options.
>>>>
>>>> While specifying include and library paths on the dub command line can
>>>> definitely be done. Not so sure whether that fits into dub's approach.
>>>
>>> Fair enough. One possible argument is that setting the compiler entails
>>> setting flags, too (because e.g. gdc and dmd have different flags).
>>
>> Dub has an abstraction shim to unify compiler flags.
>> http://code.dlang.org/package-format#build-requirements
>> http://code.dlang.org/package-format#build-options
>>
>> You'd use `dub build -b release` for an optimzed build regardless of
>> what compiler you chose.
>
> I see, thanks. That would suggest it would be appropriate to add a -I flag that allows setting the include path for all compilers.
>

It's possible to manually set compiler flags using the DFLAGS environment variable:

DFLAGS="-I/some/path -release -O -inline" dub build

It overrides any package specific "build type" settings.

Sönke
_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta
October 31, 2014
On 10/30/14 12:12 AM, Sönke Ludwig via dmd-beta wrote:
>
> It's possible to manually set compiler flags using the DFLAGS
> environment variable:
>
> DFLAGS="-I/some/path -release -O -inline" dub build
>
> It overrides any package specific "build type" settings.

Thanks, Sönke! Next problem :o). I now get this when running "dub build --root=../tools/dpl-docs --compiler=../dmd/src/dmd". Please advise:

Building vibe-d 0.7.21-rc.3 configuration "libevent", build type debug.
Running ../dmd/src/dmd...
../../../.dub/packages/vibe-d-0.7.21-rc.3/source/vibe/core/drivers/libevent2.d(864): Warning: instead of C-style syntax, use D-style syntax 'char[64] buf'
../../../.dub/packages/vibe-d-0.7.21-rc.3/source/vibe/stream/openssl.d(59): Warning: instead of C-style syntax, use D-style syntax 'ubyte[64] m_peekBuffer'
../../../.dub/packages/vibe-d-0.7.21-rc.3/source/vibe/core/file.d(17): Deprecation: module std.c.stdio is deprecated - Please import core.stdc.stdio instead. This module will be removed in December 2015.
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/bn.d(342): Warning: instead of C-style syntax, use D-style syntax 'BN_ULONG[2] n0'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/bn.d(658): Warning: instead of C-style syntax, use D-style syntax 'int[] p'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/bn.d(661): Warning: instead of C-style syntax, use D-style syntax 'int[] p'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/bn.d(662): Warning: instead of C-style syntax, use D-style syntax 'int[] p'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/bn.d(664): Warning: instead of C-style syntax, use D-style syntax 'int[] p'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/bn.d(667): Warning: instead of C-style syntax, use D-style syntax 'int[] p'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/bn.d(669): Warning: instead of C-style syntax, use D-style syntax 'int[] p'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/bn.d(671): Warning: instead of C-style syntax, use D-style syntax 'int[] p'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/bn.d(673): Warning: instead of C-style syntax, use D-style syntax 'int[] p'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/bn.d(674): Warning: instead of C-style syntax, use D-style syntax 'int[] p'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/bn.d(675): Warning: instead of C-style syntax, use D-style syntax 'int[] p'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/evp.d(180): Warning: instead of C-style syntax, use D-style syntax 'int[5] required_pkey_type'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/evp.d(364): Warning: instead of C-style syntax, use D-style syntax 'ubyte[EVP_MAX_IV_LENGTH] iv'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/evp.d(375): Warning: instead of C-style syntax, use D-style syntax 'ubyte[EVP_MAX_IV_LENGTH] oiv'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/evp.d(376): Warning: instead of C-style syntax, use D-style syntax 'ubyte[EVP_MAX_IV_LENGTH] iv'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/evp.d(377): Warning: instead of C-style syntax, use D-style syntax 'ubyte[EVP_MAX_BLOCK_LENGTH] buf'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/evp.d(396): Warning: instead of C-style syntax, use D-style syntax 'ubyte[80] enc_data'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/x509.d(311): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SHA_DIGEST_LENGTH] sha1_hash'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/x509.d(486): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SHA_DIGEST_LENGTH] sha1_hash'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ec.d(620): Warning: instead of C-style syntax, use D-style syntax 'const(EC_POINT)*[] p'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ec.d(620): Warning: instead of C-style syntax, use D-style syntax 'const(BIGNUM)*[] m'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/sha.d(111): Warning: instead of C-style syntax, use D-style syntax 'SHA_LONG[SHA_LBLOCK] data'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/sha.d(138): Warning: instead of C-style syntax, use D-style syntax 'SHA_LONG[8] h'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/sha.d(140): Warning: instead of C-style syntax, use D-style syntax 'SHA_LONG[SHA_LBLOCK] data'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/sha.d(183): Warning: instead of C-style syntax, use D-style syntax 'SHA_LONG64[8] h'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/sha.d(186): Warning: instead of C-style syntax, use D-style syntax 'SHA_LONG64[SHA_LBLOCK] d'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/sha.d(187): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SHA512_CBLOCK] p'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl.d(457): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SSL_MAX_KEY_ARG_LENGTH] key_arg'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl.d(459): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SSL_MAX_MASTER_KEY_LENGTH] master_key'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl.d(462): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SSL_MAX_SSL_SESSION_ID_LENGTH] session_id'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl.d(467): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SSL_MAX_SID_CTX_LENGTH] sid_ctx'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl.d(471): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SSL_MAX_KRB5_PRINCIPAL_LENGTH] krb5_client_princ'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl.d(832): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SSL_MAX_SID_CTX_LENGTH] sid_ctx'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl.d(864): Warning: instead of C-style syntax, use D-style syntax 'ubyte[16] tlsext_tick_key_name'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl.d(865): Warning: instead of C-style syntax, use D-style syntax 'ubyte[16] tlsext_tick_hmac_key'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl.d(866): Warning: instead of C-style syntax, use D-style syntax 'ubyte[16] tlsext_tick_aes_key'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl.d(1122): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SSL_MAX_SID_CTX_LENGTH] sid_ctx'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl2.d(200): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SSL2_MAX_CHALLENGE_LENGTH] challenge'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl2.d(202): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SSL2_MAX_CONNECTION_ID_LENGTH] conn_id'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl2.d(204): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SSL2_MAX_KEY_MATERIAL_LENGTH * 2] key_material'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl2.d(216): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SSL2_MAX_CERT_CHALLENGE_LENGTH] ccl'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(351): Warning: instead of C-style syntax, use D-style syntax 'ubyte[8] seq_num'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(389): Warning: instead of C-style syntax, use D-style syntax 'ubyte[8] read_sequence'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(391): Warning: instead of C-style syntax, use D-style syntax 'ubyte[EVP_MAX_MD_SIZE] read_mac_secret'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(392): Warning: instead of C-style syntax, use D-style syntax 'ubyte[8] write_sequence'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(394): Warning: instead of C-style syntax, use D-style syntax 'ubyte[EVP_MAX_MD_SIZE] write_mac_secret'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(396): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SSL3_RANDOM_SIZE] server_random'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(397): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SSL3_RANDOM_SIZE] client_random'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(414): Warning: instead of C-style syntax, use D-style syntax 'ubyte[2] alert_fragment'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(416): Warning: instead of C-style syntax, use D-style syntax 'ubyte[4] handshake_fragment'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(441): Warning: instead of C-style syntax, use D-style syntax 'ubyte[2] send_alert'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(461): Warning: instead of C-style syntax, use D-style syntax 'ubyte[EVP_MAX_MD_SIZE * 2] cert_verify_md'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(464): Warning: instead of C-style syntax, use D-style syntax 'ubyte[EVP_MAX_MD_SIZE * 2] finish_md'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(466): Warning: instead of C-style syntax, use D-style syntax 'ubyte[EVP_MAX_MD_SIZE * 2] peer_finish_md'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(490): Warning: instead of C-style syntax, use D-style syntax 'char[SSL3_CT_NUMBER] ctype'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(512): Warning: instead of C-style syntax, use D-style syntax 'ubyte[EVP_MAX_MD_SIZE] previous_client_finished'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(514): Warning: instead of C-style syntax, use D-style syntax 'ubyte[EVP_MAX_MD_SIZE] previous_server_finished'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/kssl.d(120): Warning: instead of C-style syntax, use D-style syntax 'char[KSSL_ERR_MAX + 1] text'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/hmac.d(81): Warning: instead of C-style syntax, use D-style syntax 'ubyte[HMAC_MAX_MD_CBLOCK] key'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/dtls1.d(118): Warning: instead of C-style syntax, use D-style syntax 'ubyte[8] max_seq_num'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/dtls1.d(181): Warning: instead of C-style syntax, use D-style syntax 'ubyte[DTLS1_COOKIE_LENGTH] cookie'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/dtls1.d(182): Warning: instead of C-style syntax, use D-style syntax 'ubyte[DTLS1_COOKIE_LENGTH] rcvd_cookie'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/dtls1.d(206): Warning: instead of C-style syntax, use D-style syntax 'ubyte[8] last_write_sequence'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/dtls1.d(243): Warning: instead of C-style syntax, use D-style syntax 'ubyte[DTLS1_AL_HEADER_LENGTH] alert_fragment'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/dtls1.d(245): Warning: instead of C-style syntax, use D-style syntax 'ubyte[DTLS1_HM_HEADER_LENGTH] handshake_fragment'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/pqueue.d(72): Warning: instead of C-style syntax, use D-style syntax 'ubyte[8] priority'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/err.d(157): Warning: instead of C-style syntax, use D-style syntax 'int[ERR_NUM_ERRORS] err_flags'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/err.d(158): Warning: instead of C-style syntax, use D-style syntax 'c_ulong[ERR_NUM_ERRORS] err_buffer'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/err.d(159): Warning: instead of C-style syntax, use D-style syntax 'char*[ERR_NUM_ERRORS] err_data'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/err.d(160): Warning: instead of C-style syntax, use D-style syntax 'int[ERR_NUM_ERRORS] err_data_flags'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/err.d(161): Warning: instead of C-style syntax, use D-style syntax 'const(char)*[ERR_NUM_ERRORS] err_file'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/err.d(162): Warning: instead of C-style syntax, use D-style syntax 'int[ERR_NUM_ERRORS] err_line'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/err.d(358): Warning: instead of C-style syntax, use D-style syntax 'ERR_STRING_DATA[] str'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/err.d(359): Warning: instead of C-style syntax, use D-style syntax 'ERR_STRING_DATA[] str'
/Users/aalexandre/code/d/phobos/std/container/array.d(432): Error: cannot implicitly convert expression ((inout inout(Range) __ctmp3067 = 0;
 , __ctmp3067).this(this, 0LU, this.length())) of type inout(Range) to Range
../../../.dub/packages/vibe-d-0.7.21-rc.3/source/vibe/core/drivers/timerqueue.d(29):        while looking for match for BinaryHeap!(Array!(TimeoutEntry), "a.timeout > b.timeout")
../../../.dub/packages/vibe-d-0.7.21-rc.3/source/vibe/core/drivers/libevent2.d(75): Error: template instance vibe.core.drivers.timerqueue.TimerQueue!(TimerInfo, 10000L) error instantiating
FAIL ../../../.dub/packages/vibe-d-0.7.21-rc.3/.dub/build/libevent-debug-posix.osx-x86_64-dmd_2067-86DCE9509628285A97A5E70118DEE27C/ vibe-d staticLibrary
Error executing command build: ../dmd/src/dmd failed with exit code 1.



_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta
October 31, 2014
Correction. I just rebuilt all of dmd/druntime/phobos from git head and now I get fewer errors - essentially only C-style stuff:

./../../.dub/packages/vibe-d-0.7.21-rc.3/source/vibe/core/drivers/libevent2.d(864): Warning: instead of C-style syntax, use D-style syntax 'char[64] buf'
../../../.dub/packages/vibe-d-0.7.21-rc.3/source/vibe/stream/openssl.d(59): Warning: instead of C-style syntax, use D-style syntax 'ubyte[64] m_peekBuffer'
../../../.dub/packages/vibe-d-0.7.21-rc.3/source/vibe/core/file.d(17): Deprecation: module std.c.stdio is deprecated - Please import core.stdc.stdio instead. This module will be removed in December 2015.
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/bn.d(342): Warning: instead of C-style syntax, use D-style syntax 'BN_ULONG[2] n0'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/bn.d(658): Warning: instead of C-style syntax, use D-style syntax 'int[] p'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/bn.d(661): Warning: instead of C-style syntax, use D-style syntax 'int[] p'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/bn.d(662): Warning: instead of C-style syntax, use D-style syntax 'int[] p'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/bn.d(664): Warning: instead of C-style syntax, use D-style syntax 'int[] p'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/bn.d(667): Warning: instead of C-style syntax, use D-style syntax 'int[] p'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/bn.d(669): Warning: instead of C-style syntax, use D-style syntax 'int[] p'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/bn.d(671): Warning: instead of C-style syntax, use D-style syntax 'int[] p'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/bn.d(673): Warning: instead of C-style syntax, use D-style syntax 'int[] p'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/bn.d(674): Warning: instead of C-style syntax, use D-style syntax 'int[] p'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/bn.d(675): Warning: instead of C-style syntax, use D-style syntax 'int[] p'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/evp.d(180): Warning: instead of C-style syntax, use D-style syntax 'int[5] required_pkey_type'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/evp.d(364): Warning: instead of C-style syntax, use D-style syntax 'ubyte[EVP_MAX_IV_LENGTH] iv'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/evp.d(375): Warning: instead of C-style syntax, use D-style syntax 'ubyte[EVP_MAX_IV_LENGTH] oiv'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/evp.d(376): Warning: instead of C-style syntax, use D-style syntax 'ubyte[EVP_MAX_IV_LENGTH] iv'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/evp.d(377): Warning: instead of C-style syntax, use D-style syntax 'ubyte[EVP_MAX_BLOCK_LENGTH] buf'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/evp.d(396): Warning: instead of C-style syntax, use D-style syntax 'ubyte[80] enc_data'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/x509.d(311): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SHA_DIGEST_LENGTH] sha1_hash'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/x509.d(486): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SHA_DIGEST_LENGTH] sha1_hash'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ec.d(620): Warning: instead of C-style syntax, use D-style syntax 'const(EC_POINT)*[] p'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ec.d(620): Warning: instead of C-style syntax, use D-style syntax 'const(BIGNUM)*[] m'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/sha.d(111): Warning: instead of C-style syntax, use D-style syntax 'SHA_LONG[SHA_LBLOCK] data'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/sha.d(138): Warning: instead of C-style syntax, use D-style syntax 'SHA_LONG[8] h'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/sha.d(140): Warning: instead of C-style syntax, use D-style syntax 'SHA_LONG[SHA_LBLOCK] data'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/sha.d(183): Warning: instead of C-style syntax, use D-style syntax 'SHA_LONG64[8] h'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/sha.d(186): Warning: instead of C-style syntax, use D-style syntax 'SHA_LONG64[SHA_LBLOCK] d'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/sha.d(187): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SHA512_CBLOCK] p'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl.d(457): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SSL_MAX_KEY_ARG_LENGTH] key_arg'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl.d(459): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SSL_MAX_MASTER_KEY_LENGTH] master_key'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl.d(462): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SSL_MAX_SSL_SESSION_ID_LENGTH] session_id'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl.d(467): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SSL_MAX_SID_CTX_LENGTH] sid_ctx'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl.d(471): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SSL_MAX_KRB5_PRINCIPAL_LENGTH] krb5_client_princ'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl.d(832): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SSL_MAX_SID_CTX_LENGTH] sid_ctx'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl.d(864): Warning: instead of C-style syntax, use D-style syntax 'ubyte[16] tlsext_tick_key_name'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl.d(865): Warning: instead of C-style syntax, use D-style syntax 'ubyte[16] tlsext_tick_hmac_key'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl.d(866): Warning: instead of C-style syntax, use D-style syntax 'ubyte[16] tlsext_tick_aes_key'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl.d(1122): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SSL_MAX_SID_CTX_LENGTH] sid_ctx'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl2.d(200): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SSL2_MAX_CHALLENGE_LENGTH] challenge'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl2.d(202): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SSL2_MAX_CONNECTION_ID_LENGTH] conn_id'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl2.d(204): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SSL2_MAX_KEY_MATERIAL_LENGTH * 2] key_material'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl2.d(216): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SSL2_MAX_CERT_CHALLENGE_LENGTH] ccl'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(351): Warning: instead of C-style syntax, use D-style syntax 'ubyte[8] seq_num'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(389): Warning: instead of C-style syntax, use D-style syntax 'ubyte[8] read_sequence'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(391): Warning: instead of C-style syntax, use D-style syntax 'ubyte[EVP_MAX_MD_SIZE] read_mac_secret'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(392): Warning: instead of C-style syntax, use D-style syntax 'ubyte[8] write_sequence'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(394): Warning: instead of C-style syntax, use D-style syntax 'ubyte[EVP_MAX_MD_SIZE] write_mac_secret'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(396): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SSL3_RANDOM_SIZE] server_random'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(397): Warning: instead of C-style syntax, use D-style syntax 'ubyte[SSL3_RANDOM_SIZE] client_random'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(414): Warning: instead of C-style syntax, use D-style syntax 'ubyte[2] alert_fragment'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(416): Warning: instead of C-style syntax, use D-style syntax 'ubyte[4] handshake_fragment'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(441): Warning: instead of C-style syntax, use D-style syntax 'ubyte[2] send_alert'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(461): Warning: instead of C-style syntax, use D-style syntax 'ubyte[EVP_MAX_MD_SIZE * 2] cert_verify_md'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(464): Warning: instead of C-style syntax, use D-style syntax 'ubyte[EVP_MAX_MD_SIZE * 2] finish_md'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(466): Warning: instead of C-style syntax, use D-style syntax 'ubyte[EVP_MAX_MD_SIZE * 2] peer_finish_md'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(490): Warning: instead of C-style syntax, use D-style syntax 'char[SSL3_CT_NUMBER] ctype'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(512): Warning: instead of C-style syntax, use D-style syntax 'ubyte[EVP_MAX_MD_SIZE] previous_client_finished'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/ssl3.d(514): Warning: instead of C-style syntax, use D-style syntax 'ubyte[EVP_MAX_MD_SIZE] previous_server_finished'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/kssl.d(120): Warning: instead of C-style syntax, use D-style syntax 'char[KSSL_ERR_MAX + 1] text'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/hmac.d(81): Warning: instead of C-style syntax, use D-style syntax 'ubyte[HMAC_MAX_MD_CBLOCK] key'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/dtls1.d(118): Warning: instead of C-style syntax, use D-style syntax 'ubyte[8] max_seq_num'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/dtls1.d(181): Warning: instead of C-style syntax, use D-style syntax 'ubyte[DTLS1_COOKIE_LENGTH] cookie'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/dtls1.d(182): Warning: instead of C-style syntax, use D-style syntax 'ubyte[DTLS1_COOKIE_LENGTH] rcvd_cookie'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/dtls1.d(206): Warning: instead of C-style syntax, use D-style syntax 'ubyte[8] last_write_sequence'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/dtls1.d(243): Warning: instead of C-style syntax, use D-style syntax 'ubyte[DTLS1_AL_HEADER_LENGTH] alert_fragment'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/dtls1.d(245): Warning: instead of C-style syntax, use D-style syntax 'ubyte[DTLS1_HM_HEADER_LENGTH] handshake_fragment'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/pqueue.d(72): Warning: instead of C-style syntax, use D-style syntax 'ubyte[8] priority'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/err.d(157): Warning: instead of C-style syntax, use D-style syntax 'int[ERR_NUM_ERRORS] err_flags'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/err.d(158): Warning: instead of C-style syntax, use D-style syntax 'c_ulong[ERR_NUM_ERRORS] err_buffer'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/err.d(159): Warning: instead of C-style syntax, use D-style syntax 'char*[ERR_NUM_ERRORS] err_data'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/err.d(160): Warning: instead of C-style syntax, use D-style syntax 'int[ERR_NUM_ERRORS] err_data_flags'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/err.d(161): Warning: instead of C-style syntax, use D-style syntax 'const(char)*[ERR_NUM_ERRORS] err_file'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/err.d(162): Warning: instead of C-style syntax, use D-style syntax 'int[ERR_NUM_ERRORS] err_line'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/err.d(358): Warning: instead of C-style syntax, use D-style syntax 'ERR_STRING_DATA[] str'
../../../.dub/packages/openssl-1.0.0_1.0.0e/deimos/openssl/err.d(359): Warning: instead of C-style syntax, use D-style syntax 'ERR_STRING_DATA[] str'
FAIL ../../../.dub/packages/vibe-d-0.7.21-rc.3/.dub/build/libevent-$DFLAGS-posix.osx-x86_64-dmd_2067-9DD7EE1E6ADA9E08958D1AE68E2DEEC9/ vibe-d staticLibrary
_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta
November 01, 2014
Well here's a problem I'm encountering. I download .tar.gz stuff for the previous months. Right now it's Nov 1 0:27 so my system is looking for https://issues.dlang.org/s3logs/previous/2014-10.tar.gz. That's not yet there, which is fine. However, when I download (with curl) I don't get a nice error, I get an HTML page containing the error as text instead of the .tar.gz file. Subsequently my automated code attempts to untar the file and obviously fails.

That's why I think ftp or ssh would be better. Any solution with what we have?


Andrei

On 10/16/14 12:58 AM, Brad Roberts via dmd-beta wrote:
> It's semi-automated.  None of the issues between current and more
> automated are difficult, but there's a bunch of little things.  It's
> really pretty easy for me to do the syncing, so I haven't really
> bothered to invest in it.
>
> The largest stumbling block, not for automation, but long term single
> point of failure issues is that the s3 bucket is owned by my personal
> account along with a bunch of other things.  It'd be better to have a
> standalone account for just that bucket.  Also not hard to change, but
> requires effort and some down time.  Just hasn't been worth doing.
>
> Really, it takes me just a couple minutes to do, which is dominated by
> network file transfers.
>
> On 10/15/2014 11:14 PM, Jacob Carlborg via dmd-beta wrote:
>> On Oct 15, 2014, at 10:36 PM, Martin Nowak via dmd-beta
>> <dmd-beta@puremagic.com> wrote:
>>
>>> Files are uploaded to my webserver, someone needs to copy them to
>>> ftp.digitalmars.com and the S3 server.
>>
>> How automated is this process now? What's missing to make it completely
>> automatic except for entering passwords/API keys and similar?
>>
>> --
>> /Jacob Carlborg
>>
>>
>> _______________________________________________
>> dmd-beta mailing list
>> dmd-beta@puremagic.com
>> http://lists.puremagic.com/mailman/listinfo/dmd-beta
>>
> _______________________________________________
> dmd-beta mailing list
> dmd-beta@puremagic.com
> http://lists.puremagic.com/mailman/listinfo/dmd-beta
_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta
November 01, 2014
What http library are you using that can't tell you that the status code isn't 200 but instead is a 404?

On 11/1/2014 12:30 AM, Andrei Alexandrescu wrote:
> Well here's a problem I'm encountering. I download .tar.gz stuff for the
> previous months. Right now it's Nov 1 0:27 so my system is looking for
> https://issues.dlang.org/s3logs/previous/2014-10.tar.gz. That's not yet
> there, which is fine. However, when I download (with curl) I don't get a
> nice error, I get an HTML page containing the error as text instead of
> the .tar.gz file. Subsequently my automated code attempts to untar the
> file and obviously fails.
>
> That's why I think ftp or ssh would be better. Any solution with what we
> have?
>
>
> Andrei
>
> On 10/16/14 12:58 AM, Brad Roberts via dmd-beta wrote:
>> It's semi-automated.  None of the issues between current and more
>> automated are difficult, but there's a bunch of little things.  It's
>> really pretty easy for me to do the syncing, so I haven't really
>> bothered to invest in it.
>>
>> The largest stumbling block, not for automation, but long term single
>> point of failure issues is that the s3 bucket is owned by my personal
>> account along with a bunch of other things.  It'd be better to have a
>> standalone account for just that bucket.  Also not hard to change, but
>> requires effort and some down time.  Just hasn't been worth doing.
>>
>> Really, it takes me just a couple minutes to do, which is dominated by
>> network file transfers.
>>
>> On 10/15/2014 11:14 PM, Jacob Carlborg via dmd-beta wrote:
>>> On Oct 15, 2014, at 10:36 PM, Martin Nowak via dmd-beta
>>> <dmd-beta@puremagic.com> wrote:
>>>
>>>> Files are uploaded to my webserver, someone needs to copy them to
>>>> ftp.digitalmars.com and the S3 server.
>>>
>>> How automated is this process now? What's missing to make it completely
>>> automatic except for entering passwords/API keys and similar?
>>>
>>> --
>>> /Jacob Carlborg
>>>
>>>
>>> _______________________________________________
>>> dmd-beta mailing list
>>> dmd-beta@puremagic.com
>>> http://lists.puremagic.com/mailman/listinfo/dmd-beta
>>>
>> _______________________________________________
>> dmd-beta mailing list
>> dmd-beta@puremagic.com
>> http://lists.puremagic.com/mailman/listinfo/dmd-beta
_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta
November 01, 2014
He's using curl.

On Sat, Nov 1, 2014 at 7:17 PM, Brad Roberts via dmd-beta <dmd-beta@puremagic.com> wrote:
> What http library are you using that can't tell you that the status code isn't 200 but instead is a 404?
>
>
> On 11/1/2014 12:30 AM, Andrei Alexandrescu wrote:
>>
>> Well here's a problem I'm encountering. I download .tar.gz stuff for the previous months. Right now it's Nov 1 0:27 so my system is looking for https://issues.dlang.org/s3logs/previous/2014-10.tar.gz. That's not yet there, which is fine. However, when I download (with curl) I don't get a nice error, I get an HTML page containing the error as text instead of the .tar.gz file. Subsequently my automated code attempts to untar the file and obviously fails.
>>
>> That's why I think ftp or ssh would be better. Any solution with what we have?
>>
>>
>> Andrei
>>
>> On 10/16/14 12:58 AM, Brad Roberts via dmd-beta wrote:
>>>
>>> It's semi-automated.  None of the issues between current and more automated are difficult, but there's a bunch of little things.  It's really pretty easy for me to do the syncing, so I haven't really bothered to invest in it.
>>>
>>> The largest stumbling block, not for automation, but long term single point of failure issues is that the s3 bucket is owned by my personal account along with a bunch of other things.  It'd be better to have a standalone account for just that bucket.  Also not hard to change, but requires effort and some down time.  Just hasn't been worth doing.
>>>
>>> Really, it takes me just a couple minutes to do, which is dominated by network file transfers.
>>>
>>> On 10/15/2014 11:14 PM, Jacob Carlborg via dmd-beta wrote:
>>>>
>>>> On Oct 15, 2014, at 10:36 PM, Martin Nowak via dmd-beta <dmd-beta@puremagic.com> wrote:
>>>>
>>>>> Files are uploaded to my webserver, someone needs to copy them to ftp.digitalmars.com and the S3 server.
>>>>
>>>>
>>>> How automated is this process now? What's missing to make it completely automatic except for entering passwords/API keys and similar?
>>>>
>>>> --
>>>> /Jacob Carlborg
>>>>
>>>>
>>>> _______________________________________________
>>>> dmd-beta mailing list
>>>> dmd-beta@puremagic.com
>>>> http://lists.puremagic.com/mailman/listinfo/dmd-beta
>>>>
>>> _______________________________________________
>>> dmd-beta mailing list
>>> dmd-beta@puremagic.com
>>> http://lists.puremagic.com/mailman/listinfo/dmd-beta
>
> _______________________________________________
> dmd-beta mailing list
> dmd-beta@puremagic.com
> http://lists.puremagic.com/mailman/listinfo/dmd-beta
_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta
November 01, 2014
Ah.. sorry, read too fast, curl.  To get it to acctually fail when the server fails the request, add --fail.

example:

braddr@redmond:~$ curl --silent --fail --output /tmp/foo.tar.gz \
      https://issues.dlang.org/s3logs/previous/2014-10.tar.gz
braddr@redmond:~$ echo $?
22


On 11/1/2014 1:17 AM, Brad Roberts via dmd-beta wrote:
> What http library are you using that can't tell you that the status code
> isn't 200 but instead is a 404?
>
> On 11/1/2014 12:30 AM, Andrei Alexandrescu wrote:
>> Well here's a problem I'm encountering. I download .tar.gz stuff for the
>> previous months. Right now it's Nov 1 0:27 so my system is looking for
>> https://issues.dlang.org/s3logs/previous/2014-10.tar.gz. That's not yet
>> there, which is fine. However, when I download (with curl) I don't get a
>> nice error, I get an HTML page containing the error as text instead of
>> the .tar.gz file. Subsequently my automated code attempts to untar the
>> file and obviously fails.
>>
>> That's why I think ftp or ssh would be better. Any solution with what we
>> have?
>>
>>
>> Andrei
>>
>> On 10/16/14 12:58 AM, Brad Roberts via dmd-beta wrote:
>>> It's semi-automated.  None of the issues between current and more
>>> automated are difficult, but there's a bunch of little things.  It's
>>> really pretty easy for me to do the syncing, so I haven't really
>>> bothered to invest in it.
>>>
>>> The largest stumbling block, not for automation, but long term single
>>> point of failure issues is that the s3 bucket is owned by my personal
>>> account along with a bunch of other things.  It'd be better to have a
>>> standalone account for just that bucket.  Also not hard to change, but
>>> requires effort and some down time.  Just hasn't been worth doing.
>>>
>>> Really, it takes me just a couple minutes to do, which is dominated by
>>> network file transfers.
>>>
>>> On 10/15/2014 11:14 PM, Jacob Carlborg via dmd-beta wrote:
>>>> On Oct 15, 2014, at 10:36 PM, Martin Nowak via dmd-beta
>>>> <dmd-beta@puremagic.com> wrote:
>>>>
>>>>> Files are uploaded to my webserver, someone needs to copy them to
>>>>> ftp.digitalmars.com and the S3 server.
>>>>
>>>> How automated is this process now? What's missing to make it completely
>>>> automatic except for entering passwords/API keys and similar?
>>>>
>>>> --
>>>> /Jacob Carlborg
>>>>
>>>>
>>>> _______________________________________________
>>>> dmd-beta mailing list
>>>> dmd-beta@puremagic.com
>>>> http://lists.puremagic.com/mailman/listinfo/dmd-beta
>>>>
>>> _______________________________________________
>>> dmd-beta mailing list
>>> dmd-beta@puremagic.com
>>> http://lists.puremagic.com/mailman/listinfo/dmd-beta
> _______________________________________________
> dmd-beta mailing list
> dmd-beta@puremagic.com
> http://lists.puremagic.com/mailman/listinfo/dmd-beta
_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta
November 01, 2014
On 11/1/14 1:17 AM, Brad Roberts wrote:
> What http library are you using that can't tell you that the status code
> isn't 200 but instead is a 404?

The curl binary. -- Andrei
_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta