Hey Everyone, I'm looking at the pkgfile for gcc (7.3.0) in the core crux ports, and i see it grabs two patch files:: gcc-nocheck-fixincludes.patch gcc-4.7.3-multilib-dirs.patch but I can't find these files on the gnu ftp, and certainly not in the path the pkgfile seems to be looking in. These reason I'm hunting for these is because I'm trying to track down the apparently age-old "crti.o" bug when building gcc, which crux seems to be immune to. Any help would be appreciated, thank you. -Vsteve
On Wed, Sep 19, 2018 at 01:38:50PM -0400, Steve Volumetric wrote:
Hey Everyone,
I'm looking at the pkgfile for gcc (7.3.0) in the core crux ports, and i see it grabs two patch files::
gcc-nocheck-fixincludes.patch gcc-4.7.3-multilib-dirs.patch
but I can't find these files on the gnu ftp, and certainly not in the path the pkgfile seems to be looking in.
They are distributed along with the port: https://crux.nu/gitweb/?p=ports/core.git;a=tree;f=gcc;h=24a5c05576712c853d0e...
These reason I'm hunting for these is because I'm trying to track down the apparently age-old "crti.o" bug when building gcc, which crux seems to be immune to.
Any help would be appreciated, thank you.
-Vsteve
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
-- Fredrik Rinnestam
Cool, thanks for that. I guess these patches have something to do with the crti.o error, I'm about to test them, but why on earth is there such a long standing bug with gcc that's up to distro devs to patch? It looks like this bug goes back to v4 gcc days and people worked around it by changing the $PATH variable. On Wed, Sep 19, 2018, 2:06 PM Fredrik Rinnestam <fredrik@rinnestam.se> wrote:
Hey Everyone,
I'm looking at the pkgfile for gcc (7.3.0) in the core crux ports, and i see it grabs two patch files::
gcc-nocheck-fixincludes.patch gcc-4.7.3-multilib-dirs.patch
but I can't find these files on the gnu ftp, and certainly not in the
On Wed, Sep 19, 2018 at 01:38:50PM -0400, Steve Volumetric wrote: path
the pkgfile seems to be looking in.
They are distributed along with the port:
https://crux.nu/gitweb/?p=ports/core.git;a=tree;f=gcc;h=24a5c05576712c853d0e...
These reason I'm hunting for these is because I'm trying to track down the apparently age-old "crti.o" bug when building gcc, which crux seems to be immune to.
Any help would be appreciated, thank you.
-Vsteve
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
--
Fredrik Rinnestam _______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
On Wed, Sep 19, 2018 at 02:45:34PM -0400, Steve Volumetric wrote:
Cool, thanks for that.
I guess these patches have something to do with the crti.o error, I'm about to test them, but why on earth is there such a long standing bug with gcc that's up to distro devs to patch?
It looks like this bug goes back to v4 gcc days and people worked around it by changing the $PATH variable.
To be honest these patches only do cosmetic stuff. I've never come across any problems with crti.o for as long as i've worked on the CRUX toolchain. From what I can find with a search I assume its a problem of crti.o missing during linking? -- Fredrik Rinnestam
That's the one, there was an informative thread over at stackoverflow and askubuntu about it that's not immediately easy for me to link to here, but it's exactly the behavior I'm seeing but for different versions of gcc. It was identified as a bug ...in what might actually be binutils from what I'm seeing now based on some really specific usage of ld (I guess) I'll keep tinkering. Thank for you the replies. On Wed, Sep 19, 2018, 3:08 PM Fredrik Rinnestam <fredrik@rinnestam.se> wrote:
On Wed, Sep 19, 2018 at 02:45:34PM -0400, Steve Volumetric wrote:
Cool, thanks for that.
I guess these patches have something to do with the crti.o error, I'm about to test them, but why on earth is there such a long standing bug with gcc that's up to distro devs to patch?
It looks like this bug goes back to v4 gcc days and people worked around it by changing the $PATH variable.
To be honest these patches only do cosmetic stuff. I've never come across any problems with crti.o for as long as i've worked on the CRUX toolchain. From what I can find with a search I assume its a problem of crti.o missing during linking?
--
Fredrik Rinnestam _______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
participants (2)
-
Fredrik Rinnestam -
Steve Volumetric