Opened 10 years ago

Closed 9 years ago

#977 closed defect (wontfix)

GCC Configure Options Need Checked

Reported by: William Harrington Owned by: clfs-commits@…
Priority: major Milestone: CLFS Standard 3.1.0
Component: BOOK Version: CLFS Standard GIT
Keywords: Cc: berzerkula@…, jonathan@…, chris@…

Description

Greetings.

We need to check through the GCC configure options. Some have been around forever, and some added because of 4.6 or 4.7 or 4.8. Some are now auto enabled by default and some may not be required anymore or maybe some have been added.

commit 5e6856493bd0c291867288b7b07af45d8f625dec is from Chris and he has removed: --enable-shared --enable-c99 --enable-long-long as they are enabled by default.

It is critical we don't mess with the cross tools compiler options as much as possible as the host may not be a GNU/Linux host and some options may react different.

Change History (6)

comment:1 by Martin Ward, 10 years ago

Working my way through with gcc-4.9.1, can't really see anything else at the moment, need to remove --disable-mudflap as it's been depreciated and add --disable-libvtv --disable-libcilkrts --disable-target-libiberty to chap 5.13, and possibly --disable-isl-version-check if we move to isl-0.13

Also need to add --enable-install-libiberty to chap 5.15 and 10.19 ?

comment:2 by Martin Ward, 10 years ago

Needless to say the specs patch needs redoing, will post that to the list later

comment:3 by William Harrington, 10 years ago

We need to create separate tickets for changes required for ISL 0.13 upgrade and GCC 4.9 upgrades. This ticket is just for cleaning up our current book's configure options for GCC.

comment:4 by William Harrington, 10 years ago

blackadder mentioned "need to remove --disable-mudflap as it's been depreciated and add --disable-libvtv --disable-libcilkrts --disable-target-libiberty to chap 5.13"

Have a build going right now as I need to test some other things Chris and I have discussed at the IRC channel.

in reply to:  3 comment:5 by Martin Ward, 10 years ago

Replying to kb0iic:

We need to create separate tickets for changes required for ISL 0.13 upgrade and GCC 4.9 upgrades. This ticket is just for cleaning up our current book's configure options for GCC.

ok will do, looked generic to me

comment:6 by William Harrington, 9 years ago

Resolution: wontfix
Status: newclosed

We'll keep the gcc configuration option checks in the gcc 5.2 ticket. Makes more sense to be there than have a separate ticket.

Note: See TracTickets for help on using tickets.