From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,MAILING_LIST_MULTI,NICE_REPLY_A, RCVD_IN_MSPIKE_H2 autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 26471 invoked from network); 11 Apr 2023 17:04:44 -0000 Received: from second.openwall.net (193.110.157.125) by inbox.vuxu.org with ESMTPUTF8; 11 Apr 2023 17:04:44 -0000 Received: (qmail 19787 invoked by uid 550); 11 Apr 2023 17:04:41 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 19749 invoked from network); 11 Apr 2023 17:04:40 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1681232669; x=1683824669; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id:from :to:cc:subject:date:message-id:reply-to; bh=Gl8DxOGd754wWMq4Y7TyiJ4qRqGWLGoe6SQNwJ1c2Eg=; b=FUcOFxx6jTjQ0kveQdvH9igSgXu8dY3u8A8yJ/oLS2Ho80aIv6eev3r3ei7AMresRH BgUrN3tUAgw3x2NVlSs9fP2PP4x6deCwmERteK4xGcCLWkzDovpkKWBeykeuXW7KG8Zs zZMMWyx2G7irXMAPFji+vp1rdX8f+Lv0VySo47hNmqnnnZcRwduP90Xn//Hw8Sq/VqwG WsGD4H4nQJOiQfd1pBXnn1mAlAVBsaFeZfA6agtWZZhEPC+oXshkkCQbfpwNzZhNGFNg HFiwSwPh5uOZz+BHyzSy7K/Hpn3uHlm5EKUFvIsC1lD6hU0cPxJIq7x5NsCdgTYiV6CV YqyA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681232669; x=1683824669; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Gl8DxOGd754wWMq4Y7TyiJ4qRqGWLGoe6SQNwJ1c2Eg=; b=eGQwRdzMtRt03dt+0uP0BCC/aqnxmS/s/baR9QjH9Er01tN8eSwdkAAJNjw5qmKjks 2g73LxXS1nRyrLi5fK4lzGqjCyu/fHdFs9tyYkCQPDz3ptj6bxPruM2CZFCH99lQFbHH gc18GiHXidrN/T13w4tzM+B7yE8Qp4a6wz2tgGk5F6EIuxYkpyq5J8VBTZ5YTvx5FzUk ikqE6rXwQRek9/3VA8pyeYzsmwm+Zf/hfNQ9YT6uNs/aqg3iikPBug4SHdarb2LGQT7q pw858I8hlDjE3OmsM7WJZexoZfrJo8+5aaEhBJDv4+AmRM5wv/Qrdw3PPb9bYV2ozrFu xSuQ== X-Gm-Message-State: AAQBX9cl1s/v5mYEGdmMxGKasoX4EssA1q7+o4W54ef/QDlqNG62pZxV eXjC2B+FLSmlrFCoYA39dxNUmZ7DPp3naeJS X-Google-Smtp-Source: AKy350amQMHLRjlF89juvypw0NM12N9Why+KnFSPzAsLdHNL9vVspjorEq4nh74IP04v82LoaMBljg== X-Received: by 2002:a1c:f70e:0:b0:3f0:41b3:9256 with SMTP id v14-20020a1cf70e000000b003f041b39256mr9516146wmh.10.1681232668589; Tue, 11 Apr 2023 10:04:28 -0700 (PDT) Message-ID: <66276879-a71d-1519-77e0-34b3bae00693@gmail.com> Date: Tue, 11 Apr 2023 19:04:26 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.9.1 To: musl@lists.openwall.com, Darjan Krijan References: <114dbabd-9745-3655-9c21-486afa2b8d7c@gmx.de> Content-Language: en-US From: Gabriel Ravier In-Reply-To: <114dbabd-9745-3655-9c21-486afa2b8d7c@gmx.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [musl] musl-clang wrapper chokes on (Linux x86_64) On 4/11/23 12:05, Darjan Krijan wrote: > Hello, > > (Mostly copying the bug description I filed in the Arch Linux > Bugtracker. Was suggested to report upstream.) > > The musl-clang wrapper breaks when a C file includes (and > the likes). > This is due to the wrapper disabling both system and compiler include > paths entirely with '-nolibinc'. > > Additional info: > * musl 1.2.3-1 on Arch Linux, built like this: > https://github.com/archlinux/svntogit-community/blob/5af625a2c6e62f211fd59d8df974e457d615613d/trunk/PKGBUILD > > > Steps to reproduce: > - Install 'musl' and 'clang' packages and try: > $ echo -e "#include \nint main(){return 0;}" | clang -x c - > ^ works > $ echo -e "#include \nint main(){return 0;}" | musl-clang > -x c - > ^ breaks > > Steps to fix: > Replace '-nolibinc' with '-nostdlibinc' (description in clang manpage) > in wrapper so system include directories like '/usr/include' are still > not searched, but compiler ones like '/usr/lib/clang/$clang_ver/include' > that contain immintrin.h, etc. are. > > I am not sure if this could break something else, but in my opinion > compiler include directories should be essential for the compiler to > work properly. > > Regards, > Darjan > I can second this bug report, as I've just encountered a bug that seems to be exactly this on my Fedora laptop and was myself thinking about making a bug report, but this one sums it up quite well.