Newest at the top
2025-07-19 03:51:11 +0200 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich |
2025-07-19 03:46:15 +0200 | caubert | (~caubert@user/caubert) (Ping timeout: 276 seconds) |
2025-07-19 03:39:33 +0200 | caubert | (~caubert@user/caubert) caubert |
2025-07-19 03:37:04 +0200 | hakutaku | (~textual@user/hakutaku) hakutaku |
2025-07-19 03:27:24 +0200 | caubert | (~caubert@user/caubert) (Ping timeout: 265 seconds) |
2025-07-19 03:24:53 +0200 | <koala_man> | high hopes |
2025-07-19 03:24:42 +0200 | <koala_man> | I haven't incorporated it yet, but manually kludging the settings file did result in successfully building an aarch64 version of shellcheck |
2025-07-19 03:22:31 +0200 | <geekosaur> | :thumbs_up: |
2025-07-19 03:22:16 +0200 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Ping timeout: 252 seconds) |
2025-07-19 03:22:15 +0200 | jespada | (~jespada@2800:a4:2237:6f00:3569:5753:cf2c:3fc0) (Ping timeout: 244 seconds) |
2025-07-19 03:22:13 +0200 | <koala_man> | you're right, build binary-dist does result in ("C compiler command", "aarch64-linux-gnu-gcc") |
2025-07-19 03:17:38 +0200 | jespada | (~jespada@2800:a4:2237:6f00:3569:5753:cf2c:3fc0) jespada |
2025-07-19 03:16:34 +0200 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) (Ping timeout: 248 seconds) |
2025-07-19 03:14:28 +0200 | Unicorn_Princess | (~Unicorn_P@user/Unicorn-Princess/x-3540542) (Remote host closed the connection) |
2025-07-19 03:12:10 +0200 | <geekosaur> | yes |
2025-07-19 03:11:25 +0200 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) humasect |
2025-07-19 03:11:21 +0200 | <koala_man> | do I run `./hadrian/build binary-dist`? I tried --help but didn't spot the flags to set the targets |
2025-07-19 03:08:48 +0200 | <geekosaur> | and they go into the settings file so cabal will also use them when it inspects ghc's settings to see how to compile stuff itself |
2025-07-19 03:08:26 +0200 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) (Remote host closed the connection) |
2025-07-19 03:07:21 +0200 | <geekosaur> | it's generally easiest as you can force the installed bindist to use target utilities instead of host |
2025-07-19 03:06:58 +0200 | jespada | (~jespada@2800:a4:2237:6f00:44a1:1043:513:768b) (Ping timeout: 248 seconds) |
2025-07-19 03:06:57 +0200 | <geekosaur> | and yes, bindist is for when yiou buid something to install elsewhere |
2025-07-19 03:06:45 +0200 | Square2 | (~Square@user/square) (Ping timeout: 244 seconds) |
2025-07-19 03:06:10 +0200 | ski | (~ski@remote11.chalmers.se) |
2025-07-19 03:06:05 +0200 | <geekosaur> | (specifically I know it does it for "C compiler command") |
2025-07-19 03:05:56 +0200 | ski | (~ski@remote11.chalmers.se) (Server closed connection) |
2025-07-19 03:05:45 +0200 | <geekosaur> | which doesn't have a target, as you found |
2025-07-19 03:05:31 +0200 | <geekosaur> | that's not enough, for some things cabal runs gcc directly and gets the invocation from ghc's settings file |
2025-07-19 03:05:03 +0200 | <koala_man> | I do specify --with-compiler=aarch64-linux-gnu-ghc for cabal |
2025-07-19 03:04:54 +0200 | <geekosaur> | so that would explain why ghc can build stuff itself but cabal trying to do the same will use host instead of target stuff |
2025-07-19 03:03:57 +0200 | <geekosaur> | oh, also I think if ghc runs things directly it passes target args, but cabal doesn't know it needs to do that when it digs the invocations out of ghc's settings file |
2025-07-19 03:03:07 +0200 | <geekosaur> | if you tell hadrian to make a bindist, you will get a (unpacked or packed) bindist which can be installed, but it has its own `configure` that constructs the `settings` file based on what tools it finds on the system. it's not smart so it will find _host_ utilities and headers |
2025-07-19 03:03:00 +0200 | trickard_ | (~trickard@cpe-63-98-47-163.wireline.com.au) |
2025-07-19 03:02:46 +0200 | trickard_ | (~trickard@cpe-63-98-47-163.wireline.com.au) (Read error: Connection reset by peer) |
2025-07-19 03:02:25 +0200 | <koala_man> | I'm doing "./hadrian/build --flavour=quickest --bignum=native -V -j install --prefix=/usr/local". is bindist the one that builds a binary package for installation elsewhere instead of installing directly? |
2025-07-19 03:02:12 +0200 | jespada | (~jespada@2800:a4:2237:6f00:44a1:1043:513:768b) jespada |
2025-07-19 03:02:04 +0200 | <geekosaur> | `hadrian` builds a cross-compiler and some wrappers to run it. but those wrappers don't really understand cross-compilers and will generally use host headers, libraries, and utilities |
2025-07-19 03:00:17 +0200 | <koala_man> | I didn't know there rwas a difference |
2025-07-19 03:00:07 +0200 | <geekosaur> | also that looks like the main configure, not the bindist |
2025-07-19 02:59:39 +0200 | <geekosaur> | I don't think that's enough to tell it which binaries to use for `GCC` etc. |
2025-07-19 02:59:06 +0200 | <koala_man> | geekosaur: I'm doing ./configure --host x86_64-linux-gnu --build x86_64-linux-gnu --target aarch64-linux-gnu, shouldn't that be enough? |
2025-07-19 02:56:57 +0200 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) |
2025-07-19 02:56:38 +0200 | jespada | (~jespada@2800:a4:2237:6f00:7121:3b2b:1efd:451) (Ping timeout: 272 seconds) |
2025-07-19 02:51:49 +0200 | jespada | (~jespada@2800:a4:2237:6f00:7121:3b2b:1efd:451) jespada |
2025-07-19 02:49:53 +0200 | <geekosaur> | this should be part of the bindist `confgure`; if you're having `hadrian` do that, you may need to split it out so you can configure it with the right cross-utilities |
2025-07-19 02:49:16 +0200 | Tuplanolla | (~Tuplanoll@91-159-69-59.elisa-laajakaista.fi) (Ping timeout: 252 seconds) |
2025-07-19 02:49:16 +0200 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Ping timeout: 252 seconds) |
2025-07-19 02:47:32 +0200 | <geekosaur> | that sounds like you need to adjust how you're configuring your cross-compiler |
2025-07-19 02:44:46 +0200 | phma | (phma@2001:5b0:211b:d0a8:5872:6174:f4b6:2963) |
2025-07-19 02:44:24 +0200 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) |