On Wed, 2020-08-12 at 15:05 -0500, Segher Boessenkool wrote:
> > As usual I've built my own version of GCC, and then I check it into
> > Git so that all builds can use this one canonical compiler
> > regardless of operating system, etc.
>
> There's your problem. Git is not an archiver. Git does
On Tue, Aug 11, 2020 at 08:01:55PM -0400, Paul Smith wrote:
> This is a kind of esoteric problem, but all the more annoying for that.
:-)
> As usual I've built my own version of GCC, and then I check it into Git
> so that all builds can use this one canonical compiler regardless of
> operating sy
On Wed, 12 Aug 2020 at 17:43, Paul Smith wrote:
> However, the lib directory is empty in my build. What lives in your
> version of lib?
All the runtime libs, but I think that's because mingw doesn't use the
lib/lib64 split.
$ ls -1 ~/gcc/mingw/x86_64-w64-mingw32/lib/
libatomic-1.dll
libatomic.a
On Wed, 2020-08-12 at 16:53 +0100, Jonathan Wakely wrote:
> On Wed, 12 Aug 2020 at 14:33, Paul Smith
> wrote:
>
> > I'm not talking about PREFIX/lib, though. As can be seen from my
> > question I'm talking about PREFIX///lib. This is
> > where GCC keeps its own internal libraries,
>
> Not by d
On Wed, 12 Aug 2020 at 14:33, Paul Smith wrote:
>
> I'm not talking about PREFIX/lib, though.
>
> As can be seen from my question I'm talking about
> PREFIX///lib. This is where GCC keeps its own
> internal libraries,
Not by default, it isn't. I'm not sure what directory that is, but
none of my
On Wed, 2020-08-12 at 15:37 +0200, Jakub Jelinek wrote:
> The important thing is that GCC wants to be relocatable, so most
> paths are not hardcoded into the compiler, but depend on where the
> gcc driver actually is. One can then just move the whole gcc tree
> somewhere else and it should still w
On Wed, Aug 12, 2020 at 09:33:05AM -0400, Paul Smith wrote:
> As someone who takes a lot of advantage of the flexibility that tools
> like GCC provide I'm wary of reducing that flexibility. On the other
> hand I'm not sure that breaking up the internal structure of GCC's
> installation via symlink
On Wed, 2020-08-12 at 15:08 +0200, Jakub Jelinek wrote:
> > I think it's worth adding this to bugzilla. Depending on the
> > existence of empty directories seems less than ideal.
>
> But canonicalizing the paths without taking the filesystem state into
> account will significantly change the behav
On Wed, Aug 12, 2020 at 01:08:53PM +0100, Jonathan Wakely via Gcc wrote:
> > Oddly, I looked through the gnulib library and didn't find any
> > appropriate module for this. It seems like there should be one.
>
> C++17 provides std::filesystem::weakly_canonical for that. It doesn't
> help GCC or g
On Wed, 12 Aug 2020 at 01:02, Paul Smith wrote:
>
> This is a kind of esoteric problem, but all the more annoying for that.
>
> As usual I've built my own version of GCC, and then I check it into Git
> so that all builds can use this one canonical compiler regardless of
> operating system, etc.
>
This is a kind of esoteric problem, but all the more annoying for that.
As usual I've built my own version of GCC, and then I check it into Git
so that all builds can use this one canonical compiler regardless of
operating system, etc.
After being checked into Git, the compiler started failing to
11 matches
Mail list logo
