From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wm1-x342.google.com (mail-wm1-x342.google.com [IPv6:2a00:1450:4864:20::342]) by hurricane.the-brannons.com (Postfix) with ESMTPS id DEED877AA1 for ; Mon, 2 Sep 2019 11:38:05 -0700 (PDT) Received: by mail-wm1-x342.google.com with SMTP id k2so14101980wmj.4 for ; Mon, 02 Sep 2019 11:38:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=geoffair-info.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=u5fVRi7Cz6qK31N8hc4VbekoPxp9sueV9qEXBpRDKBU=; b=smIPd+jjcSWtS5CNGV0jNXSBwEGx3FoM8QVYxyruzlJQgrd9+sHAd0wxHhuIbDnP2a v0L8uCfO5W237R5pcLhk/3oJIfFWcHPF57kX2CSTQjKLtD8qm1GBFa7maaPll4uV2Uza jFqd7mfW8f553g+RcUfVvzg9dG2A2W3WYeopaFMnHNDeCbsnEkT2oVX+YwFhikHYB/v/ EdTG/u0gEqXvoe1UM2/ZmdVMN5EatTuWmU0zaIG83RmeXDHdOEc9tpFMwgnJd0pwklpg E9ocRjr9Z4ndx1z/ZEbTIXKlfSAvXihjH9TQuuisTlF/T5UgdjUGbHcaMYDDTBZh36/f jgxg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=u5fVRi7Cz6qK31N8hc4VbekoPxp9sueV9qEXBpRDKBU=; b=q8oVpw06zvZIG5iknsxrKxgx3Bkaz6T2rGhZzke4gsHO7yLi4V5E+8a51xd+t+v0n5 O1X1gE0RuXsbY1nH1Jyvo8rDuuweYX8/fOrMjXti7jtTWKHCZoPl1h8ZtWfaLMXNSnSe JlLtAzGKZb7bPssGS9oY+fu26DACA4ndCdYc5iltxCpKPnltxElT6W2OdBSMoLdj/jVL 7B4AGJvZc0aAo7azi3fyGWyidZbxvjibxLt4BJcuY7EIr2F2Wsx3Icsx/P3sR4gIrNd3 /hnqdYFq3Rgy408biD7piwsFARngVB/df68024zRwu62/k1I17+sZJC0UPcOP9suc8D4 /SsQ== X-Gm-Message-State: APjAAAXqThzk1RYdt9XPz7avMW/uKJwVWO4FqlQNkxC3nQmAdj0VjABg Tk6JeKQSkM+hOGA+cL8vckh/sMsuG98= X-Google-Smtp-Source: APXvYqysPWdaKvWgOe5zd7iMnQV/0+ZjC7jDhTbNXSTwjlnHSUYj9Awp60Dxjf/DU/YbzSFhAySpDA== X-Received: by 2002:a1c:a011:: with SMTP id j17mr11807904wme.97.1567449483900; Mon, 02 Sep 2019 11:38:03 -0700 (PDT) Received: from [192.168.1.16] (lfbn-idf2-1-265-150.w82-123.abo.wanadoo.fr. [82.123.105.150]) by smtp.googlemail.com with ESMTPSA id j26sm7324130wrd.2.2019.09.02.11.38.02 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Sep 2019 11:38:03 -0700 (PDT) Subject: Re: [edbrowse-dev] Threads (fwd) To: Edbrowse-dev@lists.the-brannons.com References: <20190801224821.eklhad@comcast.net> From: Geoff McLane Message-ID: <17349a8a-4eda-3146-1514-568b74c09594@geoffair.info> Date: Mon, 2 Sep 2019 20:38:02 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 X-BeenThere: edbrowse-dev@edbrowse.org List-Id: Edbrowse Development List MIME-Version: 1.0 In-Reply-To: <20190801224821.eklhad@comcast.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Hi Karl, Kevin, Re: .ebrc: certfile = /etc/ssl/certs/ComSign_CA.pem curl errors =============================================================== Just commented out that line, and everything worked fine... at least in my little tests... thanks... And I have had the SSL problems you sort of describe Kevin, particularly in the Windows build. When building curl, from source, you have to take care that it finds your build and install of SSL, plus OTHER things... or else you get a very broken library... but that's another topic... But generally, in linux, I usually depend that is is already installed, or is available thru the package manager, or apt, or ... and try to NEVER get into building from source, and installing, especially a system wide install... Trying $ curl https://weloveanimals.me looks like it runs fine... in both ubuntu, and windows... so I think I am good on the 'curl' front... thanks for the inputs... Re: CMakeLists.txt changes - 2 ============================== Yes, I have mentioned TWO (2), separate, CMakeLists.txt changes - one for Windows, and one for Unix... The change for Windows is only to get rid of a warning, since I upgraded my pthreads w32 installation... NOT important, and yes, could be included in a PR, if/when I get that far... But the change for Unix is critical to get the cmake build to work there... patch given in previous... This suggests other linux/unix people are `NOT` using 'cmake'! Or they would be shouting EEEEEK!... On reading the README, I can see your continue to support, and obviously use, of the src/makefile, or something... to me that is sad... maintaining TWO (2), or 3?, separate, build systems is always tricky... And the only way to maintain cmake, which is supposed to be for ALL systems, is to use it, play with modifying it, get to understand, and above ALL, trust that it will do the right thing... in ALL cases... make it the /ONLY/ build option... Karl, you are obviously maintaining the src/makefiles... and recently must have added '-lpthreads'... this has to be also done in CMakeLists.txt... just a few line of cmake script, as per my diff, and done... I await your decision on which way to jump on this ;=)) Re: ftruncate/truncate WIN32 replacements - w32 =============================================== For testing, I have used a compile time #ifdef DOSLIKE, but when, if, these w32 replacements work fine, then I would probably add something like a win32/wtrunc.c src file, like dirent.c and vsprtf.c... so the ugly #ifdef's can be removed from the main code... But at the same time, would like you to have a look at my forks, pthreads-w32 branch, and really ask is there not another way to do this... in a more portable way... Like not using ftruncate/truncate... maybe close and delete... or other ways... but maybe not... So I will try to get around to my very quick, kludgy, ugly, replacements... at least to try and determine for sure that equivalence has been achieved... soonest... Re: create(), open(), - possible invalid pmode parameters - w32 =============================================================== Will also try to get to the latest pull... and try retesting some of the open() changes... thanks for these... Re: sorry about mixed topics in 1 email ======================================= I can see you prefer separation... but I prepare all my replies in an editor, like gedit, offline, so to speak... so I like one file, like this ~/Documents/edbrowse/ebd-25-threads.txt, covering ALL the latest I have received, at the time of dispatch... I suppose I could try dispatching it topic by topic... but so could you split it up on receipt, separate on 'Re:', and reply to each separately... that is also ok by me... no probs... Regards, Geoff.