Bug 914351

Summary:	sys-devel/gcc-11.3.1_p20230427 +jit fails to configure if clang profile + -glldb ( ebuild problem ? )
Product:	Gentoo Linux	Reporter:	Arniii <lg3dx6fd>
Component:	Current packages	Assignee:	Gentoo Toolchain Maintainers <toolchain>
Status:	UNCONFIRMED ---
Severity:	normal	CC:	arsen
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	make.conf ( it's on clang profile ) config log at gcc-jit

Description Arniii 2023-09-17 11:18:27 UTC

/var/tmp/portage/sys-devel/gcc-11.3.1_p20230427/work/build-jit/x86_64-pc-linux-gnu/libgcc/config.log
http://0x0.st/HOm1.log

/etc/portage/make.conf
http://0x0.st/HOmA.conf

it seems the problem is that it gets compile flags from CXXFLAGS and try filters them, but not deleting all unnecessary flags. 

Furthermore, it uses the filtered flags at xgcc , which is totally wrong, because the CXXFLAGS can be clang-specific written.


from config.log:
configure:3539: /var/tmp/portage/sys-devel/gcc-11.3.1_p20230427/work/build-jit/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-11.3.1_p20230427/work/build-jit/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include    -V >&5
xgcc: error: unrecognized command-line option '-V'
xgcc: fatal error: no input files
compilation terminated.
configure:3550: $? = 1
configure:3539: /var/tmp/portage/sys-devel/gcc-11.3.1_p20230427/work/build-jit/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-11.3.1_p20230427/work/build-jit/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include    -qversion >&5
xgcc: error: unrecognized command-line option '-qversion'; did you mean '--version'?
xgcc: fatal error: no input files
compilation terminated.
configure:3550: $? = 1
configure:3566: /var/tmp/portage/sys-devel/gcc-11.3.1_p20230427/work/build-jit/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-11.3.1_p20230427/work/build-jit/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include    -o conftest -pipe -march=skylake -g -glldb -gdwarf-4 -O2   conftest.c  >&5
xgcc: error: unrecognized debug output level 'lldb'
configure:3569: $? = 1
configure:3782: checking for suffix of object files
configure:3804: /var/tmp/portage/sys-devel/gcc-11.3.1_p20230427/work/build-jit/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-11.3.1_p20230427/work/build-jit/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include    -c -pipe -march=skylake -g -glldb -gdwarf-4 -O2  conftest.c >&5
xgcc: error: unrecognized debug output level 'lldb'
configure:3808: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "GNU C Runtime Library"
| #define PACKAGE_TARNAME "libgcc"
| #define PACKAGE_VERSION "1.0"
| #define PACKAGE_STRING "GNU C Runtime Library 1.0"
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE_URL "http://www.gnu.org/software/libgcc/"
| /* end confdefs.h.  */
| 
| int
| main ()
| {
| 
|   ;
|   return 0;
| }
configure:3822: error: in `/var/tmp/portage/sys-devel/gcc-11.3.1_p20230427/work/build-jit/x86_64-pc-linux-gnu/libgcc':
configure:3824: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details

Comment 1 Arniii 2023-09-17 17:14:07 UTC

Created attachment 870816 [details]
make.conf  ( it's on clang profile )

Comment 2 Arniii 2023-09-17 17:15:05 UTC

Created attachment 870817 [details]
config log at gcc-jit

Comment 3 Arsen Arsenović gentoo-dev

2023-09-17 20:32:47 UTC

That last build log appears to be the wrong one.

I suppose a fix would be to translate -glldb* to -ggdb* in this case.

Comment 4 Arniii 2023-09-18 08:20:19 UTC

(In reply to Arsen Arsenović from comment #3)
> That last build log appears to be the wrong one.
> 
> I suppose a fix would be to translate -glldb* to -ggdb* in this case.

yep, that works. though, I guess, it should be somehow solve.

Comment 5 Sam James archtester

2023-09-18 08:25:08 UTC

(In reply to Arniii from comment #4)
> (In reply to Arsen Arsenović from comment #3)
> > That last build log appears to be the wrong one.
> > 
> > I suppose a fix would be to translate -glldb* to -ggdb* in this case.
> 
> yep, that works. though, I guess, it should be somehow solve.

that's not possible, because GCC doesn't support it.

Comment 6 Arniii 2023-09-18 08:35:30 UTC

(In reply to Sam James from comment #5)
> (In reply to Arniii from comment #4)
> > (In reply to Arsen Arsenović from comment #3)
> > > That last build log appears to be the wrong one.
> > > 
> > > I suppose a fix would be to translate -glldb* to -ggdb* in this case.
> > 
> > yep, that works. though, I guess, it should be somehow solve.
> 
> that's not possible, because GCC doesn't support it.

I mean make a better filter of options. I don't know where it happens, but I guess it happens to try get only native flags.

Comment 7 Sam James archtester

2023-09-18 08:40:06 UTC

(In reply to Arniii from comment #6)
> (In reply to Sam James from comment #5)
> > (In reply to Arniii from comment #4)
> > > (In reply to Arsen Arsenović from comment #3)
> > > > That last build log appears to be the wrong one.
> > > > 
> > > > I suppose a fix would be to translate -glldb* to -ggdb* in this case.
> > > 
> > > yep, that works. though, I guess, it should be somehow solve.
> > 
> > that's not possible, because GCC doesn't support it.
> 
> I mean make a better filter of options. I don't know where it happens, but I
> guess it happens to try get only native flags.

ah, sorry. Yeah, Arsen was suggesting we do that in the ebuild, not that you should have to do it yourself.