Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#3303 - gcc package should have CHOST argument in configure
Attached to Project:
Arch Linux
Opened by Daniel YC Lin (dlin) - Friday, 07 October 2005, 01:39 GMT
Last edited by Jan de Groot (JGC) - Friday, 07 October 2005, 06:30 GMT
Opened by Daniel YC Lin (dlin) - Friday, 07 October 2005, 01:39 GMT
Last edited by Jan de Groot (JGC) - Friday, 07 October 2005, 06:30 GMT
|
DetailsI'm doing compile i586 packages, in GCC PKGBUILD, I found there must have a CHOST enviroment to let real i586 compile, otherwise it will use the my compile machine as default.
./configure --host=$CHOST After that, I could assign compile 586 on faster(686) machine. |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Sunday, 09 October 2005, 18:30 GMT
Reason for closing: Implemented
Sunday, 09 October 2005, 18:30 GMT
Reason for closing: Implemented
Comment by Jan de Groot (JGC) -
Friday, 07 October 2005, 06:29 GMT
I agree on this one. Actually, providing --host="${CHOST}" --build "${CHOST}" for every PKGBUILD that uses ./configure and compiles native machine code, would be a good idea.