Opened 16 years ago
Closed 11 years ago
#190 closed task (fixed)
Command explanations needed for cross-tools Binutils and GCC
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | minor | Milestone: | CLFS Standard 1.2.0 |
| Component: | BOOK | Version: | CLFS Standard GIT |
| Keywords: | Cc: |
Description
Cross-Binutils uses AR=ar and AS=as. I know it has something to do with binutils automatically defaulting to using cross-tools when cross-compiling, but I don't know the details.
Similarly, there's the AR=ar in GCC Static...I don't know what that's for. Of course there's also several new GCC switches as well...
Change History (2)
comment:1 by , 15 years ago
| Milestone: | → CLFS Standard 1.2.0 |
|---|---|
| Version: | → CLFS Standard SVN |
comment:2 by , 11 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
OK, looks like I added that information some time ago and forgot to come back here and close this ticket. Thanks for the explanation.
Note:
See TracTickets
for help on using tickets.
For Binutils, AR and AS are passed because otherwise the build system will try and use $CLFS_HOST-{ar,as}. Ex, On x86_64 the build would fail with x86_64-cross-linux-gnu-ar: Command not found.
Same thing with GCC Static
If you want to make a list of the GCC flags that need a description, I'll provide what they do.