public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "John.Parke at alebra dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/102961] New: Build fails for AIX 6.1 Date: Wed, 27 Oct 2021 13:52:32 +0000 [thread overview] Message-ID: <bug-102961-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102961 Bug ID: 102961 Summary: Build fails for AIX 6.1 Product: gcc Version: 11.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: John.Parke at alebra dot com Target Milestone: --- Trying to build gcc-11.2.0 on AIX 6.1 using the following configure options: ../gcc-11.2.0/configure --prefix=/opt/freeware/gcc-11.2.0 --with-as=/usr/bin/as --with-ld=/usr/bin/ld --enable-languages=c,c++ --enable-version-specific-runtime-libs --disable-nls --with-cloog=no --with-ppl=no --disable-libstdcxx-pch --enable-__cxa_atexit --disable-werror --disable-rpath --with-static-standard-libraries --enable-threads --disable-shared --enable-static --enable-threads=aix --enable-libstdcxx-threads --disable-bootstrap --with-libiconv-prefix=/usr/local/lib Output from the build says that >>cp_64: cannot stat '../pthread/libgcc/libgcc_s.a': A file or directory in the path name does not exist. Below are last few lines of build output before the error: gmake[3]: Entering directory '/usr/gcc-11.2.0-build/powerpc-ibm-aix6.1.9.0/libgcc' ../../../gcc-11.2.0/libgcc/config/rs6000/t-slibgcc-aix:105: warning: overriding recipe for target 'all' Makefile:116: warning: ignoring old recipe for target 'all' /bin/sh ../../../gcc-11.2.0/libgcc/../mkinstalldirs ../.././gcc /opt/freeware/bin/install -c -m 644 libgcc.a ../.././gcc/ chmod 644 ../.././gcc/libgcc.a ranlib ../.././gcc/libgcc.a /opt/freeware/bin/install -c -m 644 libgcov.a ../.././gcc/ chmod 644 ../.././gcc/libgcov.a ranlib ../.././gcc/libgcov.a parts="crtcxa.o crtcxa_s.o crtdbase.o crtcxa_64.o crtcxa_64_s.o crtdbase_64.o"; \ for file in $parts; do \ rm -f ../.././gcc/$file; \ /opt/freeware/bin/install -c -m 644 $file ../.././gcc/; \ case $file in \ *.a) \ ranlib ../.././gcc/$file ;; \ esac; \ done gmake[3]: Leaving directory '/usr/gcc-11.2.0-build/powerpc-ibm-aix6.1.9.0/libgcc' cp ../pthread/libgcc/libgcc_s.a ../../gcc/pthread/ >>cp_64: cannot stat '../pthread/libgcc/libgcc_s.a': A file or directory in the path name does not exist. gmake[2]: *** [../../../gcc-11.2.0/libgcc/config/rs6000/t-slibgcc-aix:112: all] Error 1 gmake[2]: Leaving directory '/usr/gcc-11.2.0-build/powerpc-ibm-aix6.1.9.0/libgcc' gmake[1]: *** [Makefile:14084: all-target-libgcc] Error 2 gmake[1]: Leaving directory '/usr/gcc-11.2.0-build' gmake: *** [Makefile:974: all] Error 2 Not sure why this is occurring. I used the identical configure parameters for gcc 10.2.0. Any help would be greatly appreciated. If I need to submit more information, let me know. This is not a high priority issue for me...
next reply other threads:[~2021-10-27 13:52 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-27 13:52 John.Parke at alebra dot com [this message] 2021-10-28 7:58 ` [Bug target/102961] " redi at gcc dot gnu.org 2021-10-28 13:14 ` John.Parke at alebra dot com 2021-11-04 16:34 ` John.Parke at alebra dot com 2022-08-02 9:49 ` John.Parke at alebra dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-102961-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).