Opened 2 years ago

Last modified 2 years ago

#65083 new defect

libgcc11: error: 'long type-name' is invalid

Reported by: prtouatisid (S. Touati) Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.7.2
Keywords: Cc:
Port: libgcc11

Description (last modified by ryandesign (Ryan Carsten Schmidt))

Hi guys, I have this problem since long time, I do not suceed to solve it. Any help ? I put join log file Thanks:

> port upgrade outdated
....
--->  Verifying checksums for libgcc11                                          
--->  Extracting libgcc11
--->  Applying patches to libgcc11
--->  Configuring libgcc11
--->  Building libgcc11                                  
Error: Failed to build libgcc11: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc11/libgcc11/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.

Attachments (1)

main.log (984.4 KB) - added by prtouatisid (S. Touati) 2 years ago.
main.log file

Download all attachments as: .zip

Change History (6)

Changed 2 years ago by prtouatisid (S. Touati)

Attachment: main.log added

main.log file

comment:1 Changed 2 years ago by ryandesign (Ryan Carsten Schmidt)

Description: modified (diff)
Port: libgcc11 added; port upgrade outdated removed
Summary: mac port : Failed to build libgcc11: command execution failedlibgcc11: error: 'long type-name' is invalid

comment:2 Changed 2 years ago by ryandesign (Ryan Carsten Schmidt)

I also see several peculiar "File name too long" errors:

:info:build /bin/sh: =/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc11/libgcc11/work/build/x86_64-apple-darwin21/libstdc++-v3/src/.libs:/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc11/libgcc11/work/build/x86_64-apple-darwin21/libsanitizer/.libs:/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc11/libgcc11/work/build/x86_64-apple-darwin21/libssp/.libs:/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc11/libgcc11/work/build/x86_64-apple-darwin21/libgomp/.libs:/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc11/libgcc11/work/build/x86_64-apple-darwin21/libitm/.libs:/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc11/libgcc11/work/build/x86_64-apple-darwin21/libatomic/.libs:/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc11/libgcc11/work/build/./gcc:/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc11/libgcc11/work/build/./prev-gcc:$: File name too long

comment:3 in reply to:  2 Changed 2 years ago by ryandesign (Ryan Carsten Schmidt)

Replying to ryandesign:

I also see several peculiar "File name too long" errors:

However these also occur in our successful builds (like this one).

comment:4 Changed 2 years ago by ryandesign (Ryan Carsten Schmidt)

A similar error is discussed here but they didn't find the solution yet:

https://github.com/jbruchon/elks/issues/774#issuecomment-843082908

Could you attach any config.log files that are anywhere within the work directory? Maybe they will provide some insight.

Last edited 2 years ago by ryandesign (Ryan Carsten Schmidt) (previous) (diff)

comment:5 Changed 2 years ago by ajdudman

I had a problem like this. It was a build conflict with binutils. Its /opt/local/include/ansidecl.h is older and lacks some definitions. Autoconf tests failed in a cascade as they repeatedly chose binutils over gcc11 for the header. Prominently it yielded build issues with rlim_t and strsignal().

Note: See TracTickets for help on using tickets.