From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from fgw20-4.mail.saunalahti.fi (fgw20-4.mail.saunalahti.fi [62.142.5.107]) by sourceware.org (Postfix) with ESMTPS id C6D2E3858D1E for ; Wed, 11 Oct 2023 13:36:08 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org C6D2E3858D1E Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=wippies.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=wippies.com Received: from [10.0.0.41] (mobile-access-56737b-215.dhcp.inet.fi [86.115.123.215]) by fgw20.mail.saunalahti.fi (Halon) with ESMTPSA id 20a4a7d0-683b-11ee-b3cf-005056bd6ce9; Wed, 11 Oct 2023 16:36:06 +0300 (EEST) Message-ID: <2dd446fb-8fbc-b899-a42c-b00d198b9607@wippies.com> Date: Wed, 11 Oct 2023 16:36:03 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1 Subject: Re: How to fix these errors with glibc 2.37? To: Dingjun Chen , "gcc-help@gcc.gnu.org" References: From: Kai Ruottu In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,KAM_DMARC_STATUS,KAM_SHORT,NICE_REPLY_A,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Dingjun Chen kirjoitti 11.10.2023 klo 15.20: > Hi, guys, > > I want to install glibc 2.37 for 32-bit applications. Is this unrelated to your goal to produce a crosscompiler for the "RTD single board computer with Linux 2.4.36.1 2009, i686"? If not, why you are trying to produce a new glibc from scratch? Doesn't the RTD Linux system already have its own glibc-, prebuilt and "acid tested"? If it has, why you don't want to use it in the crosscompiler as the target C library? > However, there are some errors occurred and please see below for details. > > I enter the following command in the build directory: build_glibc > > ../glibc-2.37/configure --prefix=/usr/glibc2.37 CC="gcc -m32" CFLAGS="-O3" Using some other $prefix than the '/usr' in glibc build is rare. Most people want it to serve as the 'run-time library' in the produced "own Linux distro" and also as the 'development library' in the native tools on the 'own Linux distro' and in the crosstools for this 'own Linux distro' on other development hosts. If you still want crosstools for producing executables for the existing RTD Linux system "as it is now", then just copy its own glibc into your crosstoolchain as the "target C library", and not try to replace it with something "self-made". Whatever the "we want to make a better world"-people in the net are trying to suggest - "destroy everything created by the capitalism and start everything from absolute scratch!", please don't believe them. Ok, via the document : https://www.rtd.com/NEW_appnote/LinuxSupport_SWM640000020F.pdf I understood that RTD doesn't provide any "RTD Linux distro" but trusts the common Linux distros like Debian, RedHat, SuSE etc being installable on its single board computers. So your first task would be to find out which Linux distro you have on your target system.