ibotlog2html for #crosstool-ng on 2024-02-01

ibotlog2html for #crosstool-ng

<< Previous 2024-02-01 Next >>

# 01:46:58 cpackham binutils embeds gnulib so it might be an option, anyway lets give the world a chance to turn for a bit and see if there is any action upstream

# 01:47:55 cpackham your patch would get things unblocked so if there's no other action I'll probably look at over the weekend

# 02:25:11 Trel Can crosstools be configured to use a toolchain to build another toolchain?

# 02:26:43 Trel *use one of its generated toolchains

# 02:27:32 cpackham Trel: yes that's basically what a canadian cross is

# 02:28:04 cpackham There's a few samples of that in the repo

# 02:28:49 cpackham Main thing is that the first toolchain has to be on the $PATH. You can see examples of this in the github actions we use

# 02:34:49 cpackham quits : Ping timeout: 255 seconds

# 02:35:15 Trel That shouldn't be too hard hopefully.

# 02:35:43 Trel Probably easier since the architecture is the same, only glibc is ultimately different

# 02:42:06 cpackham joins #crosstool-ng

# 02:44:00 Trel If what I'm thinking works, I make toolchain B with toolchain A, and then make a buildroot with toolchain A, then copy B into the buildroot, and chroot in and go from there.

# 02:44:33 Trel assuming those steps have more nuance than that though.

# 03:07:51 cpackham quits : Ping timeout: 256 seconds

# 03:10:31 cpackham joins #crosstool-ng

# 03:33:59 Trel cpackham: I'm not getting from the instructions how to build the second toolchain. It can't just be PATH, because the binaries all have the tuple as part of the filename, it wouldn't know to use it.

# 03:34:22 Trel The tuple host and target name aren't built in ones

# 03:38:49 Trel nevermind on that, I figured out how to make it find it

# 03:40:43 Trel I have a bigger issue

# 03:50:13 Trel I'm starting over building these as tests now to see, so who knows

# 04:30:29 cpackham quits : Ping timeout: 240 seconds

# 19:23:25 cpackham joins #crosstool-ng

Generated by ibotlog2html by Yann E. MORIN

`# 01:46:58`	`cpackham`	`binutils embeds gnulib so it might be an option, anyway lets give the world a chance to turn for a bit and see if there is any action upstream`
`# 01:47:55`	`cpackham`	`your patch would get things unblocked so if there's no other action I'll probably look at over the weekend`
`# 02:25:11`	`Trel`	`Can crosstools be configured to use a toolchain to build another toolchain?`
`# 02:26:43`	`Trel`	`*use one of its generated toolchains`
`# 02:27:32`	`cpackham`	`Trel: yes that's basically what a canadian cross is`
`# 02:28:04`	`cpackham`	`There's a few samples of that in the repo`
`# 02:28:49`	`cpackham`	`Main thing is that the first toolchain has to be on the $PATH. You can see examples of this in the github actions we use`
`# 02:34:49`	`cpackham`	`quits : Ping timeout: 255 seconds`
`# 02:35:15`	`Trel`	`That shouldn't be too hard hopefully.`
`# 02:35:43`	`Trel`	`Probably easier since the architecture is the same, only glibc is ultimately different`
`# 02:42:06`	`cpackham`	`joins #crosstool-ng`
`# 02:44:00`	`Trel`	`If what I'm thinking works, I make toolchain B with toolchain A, and then make a buildroot with toolchain A, then copy B into the buildroot, and chroot in and go from there.`
`# 02:44:33`	`Trel`	`assuming those steps have more nuance than that though.`
`# 03:07:51`	`cpackham`	`quits : Ping timeout: 256 seconds`
`# 03:10:31`	`cpackham`	`joins #crosstool-ng`
`# 03:33:59`	`Trel`	`cpackham: I'm not getting from the instructions how to build the second toolchain. It can't just be PATH, because the binaries all have the tuple as part of the filename, it wouldn't know to use it.`
`# 03:34:22`	`Trel`	`The tuple host and target name aren't built in ones`
`# 03:38:49`	`Trel`	`nevermind on that, I figured out how to make it find it`
`# 03:40:43`	`Trel`	`I have a bigger issue`
`# 03:50:13`	`Trel`	`I'm starting over building these as tests now to see, so who knows`
`# 04:30:29`	`cpackham`	`quits : Ping timeout: 240 seconds`
`# 19:23:25`	`cpackham`	`joins #crosstool-ng`