Package Details: lto-dump-git 13.0.0_r197401.g33be3ee36a7-1

Git Clone URL: https://aur.archlinux.org/gcc-git.git (read-only, click to copy)
Package Base: gcc-git
Description: Dump link time optimization object files (git version)
Upstream URL: https://gcc.gnu.org
Licenses: GFDL-1.3-or-later, GPL-3.0-with-GCC-exception
Conflicts: lto-dump
Provides: lto-dump, lto-dump-git
Submitter: Allan
Maintainer: IslandC0der (ptr1337)
Last Packager: ptr1337
Votes: 15
Popularity: 0.000000
First Submitted: 2013-06-26 03:43 (UTC)
Last Updated: 2024-03-21 19:26 (UTC)

Pinned Comments

DAC324 commented on 2021-09-17 08:04 (UTC)

In addition to the jamespharvey20's sticky comment: The current GCC 12 versions are labelled "Experimental" for a reason. Development is ongoing, and there are still significant bugs. Hence, it is not recommended to use GCC 12 as a daily driver or on production systems.

At the moment, it is not even possible to build a working Linux kernel with GCC 12, see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101941 .

jamespharvey20 commented on 2017-02-15 04:30 (UTC) (edited on 2017-02-15 11:01 (UTC) by jamespharvey20)

*** STICKY *** These gcc*-git packages replace core's gcc* (non-git) packages. Technically, replacing the system gcc-libs can be dangerous. The possibility of a new upstream gcc git commit breaking your system isn't zero. When you compile and install this, you're using the latest git source, so you may be the first Arch user to be using that particular commit. In practice, I haven't seen an Arch user report such a problem for many years. Just understand that if installing these packages causes your computer to eat you, don't have your loved ones blame me. Oh, and know that if things go wrong, all you *should* have to do is uninstall the git version and go back to a previously working git version or even the core version. You might be able to do this while your system is still running, or you might have to do something like boot off an Arch ISO CD.

Latest Comments

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 Next › Last »

jamespharvey20 commented on 2015-12-13 10:45 (UTC) (edited on 2015-12-13 10:46 (UTC) by jamespharvey20)

Sure. The first instance I ran into it was at PKGBUILD::build(), at "make -C $CHOST/libstdc++-v3/doc doc-man-doxygen". It failed, expecting there to be a "${srcdir}/gcc-build/x86_64-unknown-linux-gnu/libstdc++-v3/doc" directory. But, instead, "${srcdir}/gcc-build/" has: build-x86_64-pc-linux-gnu/ prev-x86_64-pc-linux-gnu/ stage1-x86_64-pc-linux-gnu/ x86_64-pc-linux-gnu/ So, it doesn't actually detect CHOST using "unknown" and give an error. It makes the directories (at least on my system) with "pc" rather than "unknown", so every instance PKGBUILD uses $CHOST points to a non-existant directory. Off to bed. 6am here.

Allan commented on 2015-12-13 10:20 (UTC)

Can you point me at where GCC now expects the vendor to be set to something other than "unknown"?

jamespharvey20 commented on 2015-12-13 09:44 (UTC)

NOTE: GCC previously expected to see CHOST declaring vendor to be "unknown" on my system. (i.e. CHOST='x86_64-unknown-linux-gnu'.) On my system, GCC is now expecting to see vendor "pc". (i.e. CHOST='x86_64-pc-linux-gnu'.) Added a workaround so if Arch declares CHOST to be 'x86_64-unknown-linux-gnu' or 'i686-unknown-linux-gnu', it changes the 'unknown' portion to 'pc'. If this workaround fails on your system, you will receive a compilation error due to a non-existant directory. If this happens, you may have to change the PKGBUILD so _CHOST declares vendor as "softfloat", "hardfloat", or "unknown". (The directory it complains is missing will tell you what vendor value it's expecting.)

jamespharvey20 commented on 2015-12-13 09:38 (UTC)

My apologies. Unexpected multiple severe family health issues. (All turned out well.) Just pushed multiple updates that should take care of everything. There are one or two namcap errors that should be fairly non-consequential documented in the PKGBUILD that I'm going to look into and take care of tomorrow.

thatbrod commented on 2015-12-01 11:56 (UTC) (edited on 2015-12-01 11:56 (UTC) by thatbrod)

Could the owner please either orphan or update the package?

polymer commented on 2015-10-20 13:29 (UTC)

Current version fails when applying patches in prepare(), after commenting these I believe the script tries to use a MakeFile that doesn't exist. I think the PKGBUILD script is buggy or old.

charlie5 commented on 2015-07-25 12:42 (UTC)

Ok, no worries. I wasn't sure if it was the best way of doing things. I'll stay with the existing gnat_util pkg. Cheers.

jamespharvey20 commented on 2015-07-25 03:24 (UTC)

Ahh, OK. I made my previous comments thinking it was part of gcc's svn tree. Yeah, it's definitely good to keep it a separate as an Arch package.

charlie5 commented on 2015-07-24 05:55 (UTC)

I appreciate the quick responses, thanks. I've adopted a few Ada packages, some of which rely on gnat_util. Yep, gnat_util appears to have been about for a few years but hasn't made it into gcc (i think). The package provides a subset of 'core' ada files relating to system and compiler. It's used by Asis (Ada introspection), GnatColl (A set of general reuseable components), and a few others. I believe that gnat_util is not 'in' gcc as yet. There is a sourceforge project which provides it tho. I've made a PKGBUILD for gnat_util, which basically replicates your build of gcc-ada, then applies the sourceforge 'gnat_util' project Makefile to create/install the needed ada file subset (ie 1st build gcc/ada, then build gnat_util, using the just built gcc-build dir as 'input' to the gnat_util build). It appeared to work ok but was slow and a little clumsy. The PKGBUILD for the old gnat_util package should still be on the old AUR site. If I can help in anyway, pls let me know. Regards.

Allan commented on 2015-07-24 02:51 (UTC)

The [core] packages contain every file installed with "make install" (or at least I check it does at the start of every major release).

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 Next › Last »