1 |
> Does the resulting cross toolchain work for you? |
2 |
Yes, It is. |
3 |
|
4 |
> On CrOS we are building natively, why a cross toolchain is needed? |
5 |
I have just changed the vendor name. Architecture, OS and C Libraries are |
6 |
the same |
7 |
|
8 |
On Wed, 1 Jul 2020, 13:54 Benda Xu, <heroxbd@g.o> wrote: |
9 |
|
10 |
> Ashwin Kumar <ashwinkumar3098@×××××.com> writes: |
11 |
> |
12 |
> >> What prevents you from using Gentoo native toolchain binary package? |
13 |
> > When I tried to emerge binary package, crOS was missing make and patch |
14 |
> > which again puts in circular dependencies. |
15 |
> |
16 |
> No, Gentoo binary packages do not need make and patch. Please study: |
17 |
> |
18 |
> https://wiki.gentoo.org/wiki/Binary_package_guide |
19 |
> |
20 |
> >> Why is crosstool necessary? |
21 |
> |
22 |
> > Crosstool-ng produces toolchain directory and can just be moved to |
23 |
> > crOS (easier than building packages individually) |
24 |
> |
25 |
> Does the resulting cross toolchain work for you? |
26 |
> |
27 |
> On CrOS we are building natively, why a cross toolchain is needed? |
28 |
> |
29 |
> Benda |
30 |
> |