| 4 Oct 2021 |
 trofi | ideally -lgcc should be an internal detail of the compiler. | 06:35:37 |
| trofi | Also, perhaps there is no libgcc.so at all (libgcc_s.so should be an equivalent). Thus for LDFLAGS -lgcc should be enough. | 06:37:06 |
 sterni | we don't have ready-made solutions for compiler bootstrapping like lib.makeScopeWithSplicing, right? | 14:58:09 |
| sterni | I think at some point we'll want to make a similar abstraction for staged package sets which contain the compiler and run time libraries | 14:58:51 |
| sterni | ideally this could also work for the stdenv boostrap / reuse parts of that? | 14:59:18 |
| 6 Oct 2021 |
|  Rosario Pulella changed their display name from rosariopulella to Rosuavio. | 10:38:41 |
| Rosario Pulella changed their display name from Rosuavio to Rosario Pulella. | 10:45:04 |
|  kamadorueda joined the room. | 22:33:48 |
| 7 Oct 2021 |
| sterni | John Ericson: seems like we need to bring back the old school clangStdenv which was using lld regardless of hostPlatform.linker | 16:32:48 |
| sterni | since building any C++ just fails hillariously when linking using ld.bfd | 16:33:06 |
| sterni | the question just is what to call it | 16:33:13 |
| sterni | I suspect libcxxStdenv should always have lld, but we want libstdcxx + lld as well probably | 16:33:52 |
| sterni | plain clangStdenv with ld.bfd is fine more or less since it works fine for C | 16:34:05 |
| 8 Oct 2021 |
 pie_ | (xposting from main) | 00:48:22 |
| pie_ | does anyone uh know how i can tell libstdc++ to compile with more debug symbols?
Id like to figure out if it will be easier to figure out what I want to figure out by looking at stuff with gdb or trying to read the source...
doing that by itself might not be that hard (if i could find where in the guts of gcc it is...but i wouldnt know how to do to do the stdenv override either | 00:48:23 |
| trofi | libstdc++ is a part of gcc package. as opposed to glibc it does not have separateDebugInfo = true;. Perhaps it should? | 06:34:20 |
| trofi | note that libstdc++ contains a small bit of support around header-mostly STL. maybe it will be enough to add debugging symbols into it's user? (library or final executable) | 06:35:43 |
| pie_ | trofi: so i should recompile gcc with debug symbols? (or lower optimization?) | 16:47:03 |
| pie_ | specifically my problem is that i want to inspect the internals of a basic_streambuf object in gdb | 16:47:33 |
| pie_ | and gdb says <incomplete type> | 16:47:38 |
 siraben | Does Nix support Canadian cross-compilation? | 17:00:32 |
 Alyssa Ross | how's that different to the normal case? | 17:20:04 |
| trofi | pie_: don't know yet, sorry. But plan to find out for sure in following weeks :) | 17:59:00 |
| 9 Oct 2021 |
| pie_ | gdb's info sharedlibary always screws me up
the star in the read column means NOT read | 00:02:23 |
| pie_ | https://gcc-help.gcc.gnu.narkive.com/LHU6EUxd/compiling-only-libstdc-v3-with-debugging-symbols lead me to https://gcc.gnu.org/onlinedocs/libstdc++/manual/configure.html , which suggests adding --enable-libstdcxx-debug to the configureFlags for gcc might get me what i want | 00:32:21 |
| pie_ | that manual page also gives this suggestion:
Note this make command, executed in the build directory, will do much the same thing, without the configuration difference and without building everything twice: make CXXFLAGS='-g3 -O0 -fno-inline' all
| 00:32:49 |
| pie_ | I'm not quite sure that implies what I'm saying; but it would be nice if we could build libstdc++ in a separate derivation. (somehow noting the tight coupling of a c++ stdlib and its compiler | 00:33:35 |
| pie_ | * I'm not quite sure that implies what I'm saying; but it would be nice if we could build libstdc++ in a separate derivation. (somehow noting the tight coupling of a c++ stdlib and its compiler) | 00:33:37 |
| sterni | In reply to @siraben:matrix.org
Does Nix support Canadian cross-compilation? it's doable, but there's no ready made solution afaik | 09:32:38 |
| sterni | John Ericson talked about this | 09:34:08 |
