From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt1-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) by sourceware.org (Postfix) with ESMTPS id 1069D3858C60 for ; Wed, 26 Jan 2022 03:23:25 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 1069D3858C60 Received: by mail-qt1-x82e.google.com with SMTP id w6so25985016qtk.4 for ; Tue, 25 Jan 2022 19:23:25 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent :content-language:to:from:subject:content-transfer-encoding; bh=DiO5mY9Sffvw7RYk4HMwr89MYbnRjJbxmyU80nYt4G8=; b=OEnorCkp+gsK3MzhDAPRm7L5Cc9htXkgq1PNoHqXdbm8dMXN0C85wB5+ZkKVSWnkce g0bijqOWX70sDqKJCay3IizzLC5CUU5CzmjCqLy0TZbsRaeSvXdPC//Lk78aiR610w+V BLUX1rEx+XaA525oYQKgReX4iluFhKfguVGzVma/mOSqBOv4Qn+cQKYqtbk/9nmEcbMN I1FUXDv03/x9bfi323NCYpSJhb06PmXV7NNUvvbUPAhQctXLfPkFhhzO+CvTRA9ivrs9 l59ym972gq/A/bjqhNe0DzoY5YsRwmvrjZ4gQbD6O5I9l/PVMef6TYYGYwQVcpf/VSOH ID7w== X-Gm-Message-State: AOAM532vZN2qkfz/v5RLnu5ZErF7K+VVTs0qj4SBt/ZVp17er+hWfm8M NJjGkiyOxoJjyQafS5nAVdhQivlJLoLeow== X-Google-Smtp-Source: ABdhPJx+7KDKdGrIs3RRXIO31i+LTU+RkSrvXRfvjSSzeka2IaoWH+8Excs8F0kfFN1Yn9dFIIY4Vg== X-Received: by 2002:ac8:5a02:: with SMTP id n2mr17169374qta.26.1643167404369; Tue, 25 Jan 2022 19:23:24 -0800 (PST) Received: from [192.168.0.2] (173-81-38-162.pkbgcmtk01.res.dyn.suddenlink.net. [173.81.38.162]) by smtp.gmail.com with ESMTPSA id p64sm9929061qkf.38.2022.01.25.19.23.23 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 25 Jan 2022 19:23:24 -0800 (PST) Message-ID: Date: Tue, 25 Jan 2022 22:23:23 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Content-Language: en-US To: libc-help@sourceware.org From: Bill Cunningham Subject: gcc and glibc problems Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: libc-help@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-help mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jan 2022 03:23:26 -0000 I compiled a new gcc from my system gcc and glibc. Now to link a new gcc and the glibc. I have not attached any copies of errors and will try to explain the problems and will attach copies if necessary. But, the config.log returns error 77. I can compile working gcc executables by linking with the libc's newer ld-linux-x86-64.so.2. But these executables are not truly linkable, as, gcc -v -Wl,-Map -Wl,mapfile prog.c -o elffile returns ld errors and still links with glibc at /usr/lib64. Now in the path of the freshly made newer glibc that I compile. I try to compile with this, configure --prefix=/installdir --disable-nls --disable-werror --with-build-time-tools=/mnt/path \ LDFLAGS='-Wl,-rpath -Wl/mnt/lib64' CC=/mnt/bin/gcc CXX=/mnt/bin/g++ LD_RUN_LIBRARY=/mnt/lib64 /mnt/lib is a soft link to /mnt/lib64; and all the library are there. This compiles an executable that runs using some dynamic linker. Be it that above mentioned or the elf file linker. But it is still linked to the system libc. /usr/lib64 and not /mnt/lib64. I hope this makes sense. IS there anything I can try? B