From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7172 invoked by alias); 7 Jun 2014 18:48:08 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 32738 Received: (qmail 23855 invoked from network); 7 Jun 2014 18:47:56 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=SW1qZ580vIgHM9QPs/JLuWZQQG54GMia/prJ4pVdato=; b=HZTxsQGLSDwU2HhlOArKolEeTy6V9u7bBH+Nj6Fl+Jv7/rYeql1A1Ge5Z4Ntl6O806 SvUdRWoegEQw+SPON51ZUV5qf+BwNl1rJ+MpjGx7v61avI2wZ1JGSVBn3NTvhmKqgzFW NpCaBpMroEK6rHvcCzZsG4hanOHC3WyOUb7+9fWjsLH0R+DUI/jFb/D7bW6onkel3Dmd JnE4a5mhtRstrEbJMYxAJL7/OVeF9OQrRifobYRIXQTeZocgTfO9TiZF0yW8aQusi7fM BI666i/pCtXtBCkDHwyIPWeh3hnj1Cw7GtJr6j0XFeDHeFBcBxZmmY934kFv33RsFaS4 c+gw== X-Received: by 10.14.246.68 with SMTP id p44mr2381771eer.8.1402166874086; Sat, 07 Jun 2014 11:47:54 -0700 (PDT) Sender: Nikolas Garofil Message-ID: <53935E57.3020704@garofil.be> Date: Sat, 07 Jun 2014 20:47:51 +0200 From: Nikolas Garofil User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: zsh-workers@zsh.org Subject: patches for 6 different (but related) problems Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit The patches I submitted solve 6 different problems that all break the building of zsh in specific cases. I would certainly suggest using my 5th patch because this also fixes the problem of an incorrect build in some cases: The returnvalue of memcpy is used a couple of times but if autoconf can't find memcpy and memmove then memcpy get's defined as memmove and (without the patch) memmove gets defined as a macro using bcopy that doesn't provide this return value. Some (admittedly strange) compilers will still compile this and return a random value.