No end to god-awful arch, compiling GCC 4.7...


Recommended Posts

So due to yet another **** up by the now pretty ****ing useless arch linux team, we're left with a broken GCC 4.8 package, they refuse to add in the patch on GCC's site or revert back to GCC 4.7, it's boost-libs and systemd all over again.

So, I'm trying to compile GCC 4.7.2 using the old make scripts, a simple task you'd think? WRONG.

I don't even know what the arch team have done but I've had to resort to using a patch a user made on the forums, farmpolice.com/content/files/texinfo_archlinux.patch, and had to remove all traces of ada from the PKGBUILD because I just get countless errors when it's trying to link (Not that I care about ada, never used it and never planning to use it).

So, during compilation I've been greeted with so many errors I can't list them all, the current one is;

ibtool: link: (cd ".libs" && rm -f "libgfortran.so.3" && ln -s "libgfortran.so.3.0.0" "libgfortran.so.3")

libtool: link: (cd ".libs" && rm -f "libgfortran.so" && ln -s "libgfortran.so.3.0.0" "libgfortran.so")

libtool: link: ar rc .libs/libgfortran.a backtrace.o bounds.o compile_options.o convert_char.o environ.o error.o fpu.o main.o memory.o pause.o stop.o string.o select.o all_l1.o all_l2.o all_l4.o all_l8.o all_l16.o any_l1.o any_l2.o any_l4.o any_l8.o any_l16.o count_1_l.o count_2_l.o count_4_l.o count_8_l.o count_16_l.o maxloc0_4_i1.o maxloc0_8_i1.o maxloc0_16_i1.o maxloc0_4_i2.o maxloc0_8_i2.o maxloc0_16_i2.o maxloc0_4_i4.o maxloc0_8_i4.o maxloc0_16_i4.o maxloc0_4_i8.o maxloc0_8_i8.o maxloc0_16_i8.o maxloc0_4_i16.o maxloc0_8_i16.o maxloc0_16_i16.o maxloc0_4_r4.o maxloc0_8_r4.o maxloc0_16_r4.o maxloc0_4_r8.o maxloc0_8_r8.o maxloc0_16_r8.o maxloc0_4_r10.o maxloc0_8_r10.o maxloc0_16_r10.o maxloc0_4_r16.o maxloc0_8_r16.o maxloc0_16_r16.o maxloc1_4_i1.o maxloc1_8_i1.o maxloc1_16_i1.o maxloc1_4_i2.o maxloc1_8_i2.o maxloc1_16_i2.o maxloc1_4_i4.o maxloc1_8_i4.o maxloc1_16_i4.o maxloc1_4_i8.o maxloc1_8_i8.o maxloc1_16_i8.o maxloc1_4_i16.o maxloc1_8_i16.o maxloc1_16_i16.o maxloc1_4_r4.o maxloc1_8_r4.o maxloc1_16_r4.o maxloc1_4_r8.o maxloc1_8_r8.o maxloc1_16_r8.o maxloc1_4_r10.o maxloc1_8_r10.o maxloc1_16_r10.o maxloc1_4_r16.o maxloc1_8_r16.o maxloc1_16_r16.o maxval_i1.o maxval_i2.o maxval_i4.o maxval_i8.o maxval_i16.o maxval_r4.o maxval_r8.o maxval_r10.o maxval_r16.o minloc0_4_i1.o minloc0_8_i1.o minloc0_16_i1.o minloc0_4_i2.o minloc0_8_i2.o minloc0_16_i2.o minloc0_4_i4.o minloc0_8_i4.o minloc0_16_i4.o minloc0_4_i8.o minloc0_8_i8.o minloc0_16_i8.o minloc0_4_i16.o minloc0_8_i16.o minloc0_16_i16.o minloc0_4_r4.o minloc0_8_r4.o minloc0_16_r4.o minloc0_4_r8.o minloc0_8_r8.o minloc0_16_r8.o minloc0_4_r10.o minloc0_8_r10.o minloc0_16_r10.o minloc0_4_r16.o minloc0_8_r16.o minloc0_16_r16.o minloc1_4_i1.o minloc1_8_i1.o minloc1_16_i1.o minloc1_4_i2.o minloc1_8_i2.o minloc1_16_i2.o minloc1_4_i4.o minloc1_8_i4.o minloc1_16_i4.o minloc1_4_i8.o minloc1_8_i8.o minloc1_16_i8.o minloc1_4_i16.o minloc1_8_i16.o minloc1_16_i16.o minloc1_4_r4.o minloc1_8_r4.o minloc1_16_r4.o minloc1_4_r8.o minloc1_8_r8.o minloc1_16_r8.o minloc1_4_r10.o minloc1_8_r10.o minloc1_16_r10.o minloc1_4_r16.o minloc1_8_r16.o minloc1_16_r16.o minval_i1.o minval_i2.o minval_i4.o minval_i8.o minval_i16.o minval_r4.o minval_r8.o minval_r10.o minval_r16.o product_i1.o product_i2.o product_i4.o product_i8.o product_i16.o product_r4.o product_r8.o product_r10.o product_r16.o product_c4.o product_c8.o product_c10.o product_c16.o sum_i1.o sum_i2.o sum_i4.o sum_i8.o sum_i16.o sum_r4.o sum_r8.o sum_r10.o sum_r16.o sum_c4.o sum_c8.o sum_c10.o sum_c16.o bessel_r4.o bessel_r8.o bessel_r10.o bessel_r16.o iall_i1.o iall_i2.o iall_i4.o iall_i8.o iall_i16.o iany_i1.o iany_i2.o iany_i4.o iany_i8.o iany_i16.o iparity_i1.o iparity_i2.o iparity_i4.o iparity_i8.o iparity_i16.o norm2_r4.o norm2_r8.o norm2_r10.o norm2_r16.o parity_l1.o parity_l2.o parity_l4.o parity_l8.o parity_l16.o matmul_i1.o matmul_i2.o matmul_i4.o matmul_i8.o matmul_i16.o matmul_r4.o matmul_r8.o matmul_r10.o matmul_r16.o matmul_c4.o matmul_c8.o matmul_c10.o matmul_c16.o matmul_l4.o matmul_l8.o matmul_l16.o transpose_i4.o transpose_i8.o transpose_i16.o transpose_r4.o transpose_r8.o transpose_r10.o transpose_r16.o transpose_c4.o transpose_c8.o transpose_c10.o transpose_c16.o shape_i4.o shape_i8.o shape_i16.o eoshift1_4.o eoshift1_8.o eoshift1_16.o eoshift3_4.o eoshift3_8.o eoshift3_16.o cshift1_4.o cshift1_8.o cshift1_16.o reshape_i4.o reshape_i8.o reshape_i16.o reshape_r4.o reshape_r8.o reshape_r10.o reshape_r16.o reshape_c4.o reshape_c8.o reshape_c10.o reshape_c16.o in_pack_i1.o in_pack_i2.o in_pack_i4.o in_pack_i8.o in_pack_i16.o in_pack_r4.o in_pack_r8.o in_pack_r10.o in_pack_r16.o in_pack_c4.o in_pack_c8.o in_pack_c10.o in_pack_c16.o in_unpack_i1.o in_unpack_i2.o in_unpack_i4.o in_unpack_i8.o in_unpack_i16.o in_unpack_r4.o in_unpack_r8.o in_unpack_r10.o in_unpack_r16.o in_unpack_c4.o in_unpack_c8.o in_unpack_c10.o in_unpack_c16.o exponent_r4.o exponent_r8.o exponent_r10.o exponent_r16.o fraction_r4.o fraction_r8.o fraction_r10.o fraction_r16.o nearest_r4.o nearest_r8.o nearest_r10.o nearest_r16.o set_exponent_r4.o set_exponent_r8.o set_exponent_r10.o set_exponent_r16.o pow_i4_i4.o pow_i8_i4.o pow_i16_i4.o pow_r16_i4.o pow_c4_i4.o pow_c8_i4.o pow_c10_i4.o pow_c16_i4.o pow_i4_i8.o pow_i8_i8.o pow_i16_i8.o pow_r4_i8.o pow_r8_i8.o pow_r10_i8.o pow_r16_i8.o pow_c4_i8.o pow_c8_i8.o pow_c10_i8.o pow_c16_i8.o pow_i4_i16.o pow_i8_i16.o pow_i16_i16.o pow_r4_i16.o pow_r8_i16.o pow_r10_i16.o pow_r16_i16.o pow_c4_i16.o pow_c8_i16.o pow_c10_i16.o pow_c16_i16.o rrspacing_r4.o rrspacing_r8.o rrspacing_r10.o rrspacing_r16.o spacing_r4.o spacing_r8.o spacing_r10.o spacing_r16.o pack_i1.o pack_i2.o pack_i4.o pack_i8.o pack_i16.o pack_r4.o pack_r8.o pack_r10.o pack_r16.o pack_c4.o pack_c8.o pack_c10.o pack_c16.o unpack_i1.o unpack_i2.o unpack_i4.o unpack_i8.o unpack_i16.o unpack_r4.o unpack_r8.o unpack_r10.o unpack_r16.o unpack_c4.o unpack_c8.o unpack_c10.o unpack_c16.o spread_i1.o spread_i2.o spread_i4.o spread_i8.o spread_i16.o spread_r4.o spread_r8.o spread_r10.o spread_r16.o spread_c4.o spread_c8.o spread_c10.o spread_c16.o cshift0_i1.o cshift0_i2.o cshift0_i4.o cshift0_i8.o cshift0_i16.o cshift0_r4.o cshift0_r8.o cshift0_r10.o cshift0_r16.o cshift0_c4.o cshift0_c8.o cshift0_c10.o cshift0_c16.o close.o file_pos.o format.o inquire.o intrinsics.o list_read.o lock.o open.o read.o size_from_kind.o transfer.o transfer128.o unit.o unix.o write.o fbuf.o associated.o abort.o access.o args.o bit_intrinsics.o c99_functions.o chdir.o chmod.o clock.o cpu_time.o cshift0.o ctime.o date_and_time.o dtime.o env.o eoshift0.o eoshift2.o erfc_scaled.o etime.o execute_command_line.o exit.o extends_type_of.o fnum.o gerror.o getcwd.o getlog.o getXid.o hostnm.o ierrno.o ishftc.o iso_c_generated_procs.o iso_c_binding.o kill.o link.o malloc.o mvbits.o move_alloc.o pack_generic.o perror.o selected_char_kind.o signal.o size.o sleep.o spread_generic.o string_intrinsics.o system.o rand.o random.o rename.o reshape_generic.o reshape_packed.o selected_int_kind.o selected_real_kind.o stat.o symlnk.o system_clock.o time.o transpose_generic.o umask.o unlink.o unpack_generic.o in_pack_generic.o in_unpack_generic.o _abs_c4.o _abs_c8.o _abs_c10.o _abs_c16.o _abs_i4.o _abs_i8.o _abs_i16.o _abs_r4.o _abs_r8.o _abs_r10.o _abs_r16.o _aimag_c4.o _aimag_c8.o _aimag_c10.o _aimag_c16.o _exp_r4.o _exp_r8.o _exp_r10.o _exp_r16.o _exp_c4.o _exp_c8.o _exp_c10.o _exp_c16.o _log_r4.o _log_r8.o _log_r10.o _log_r16.o _log_c4.o _log_c8.o _log_c10.o _log_c16.o _log10_r4.o _log10_r8.o _log10_r10.o _log10_r16.o _sqrt_r4.o _sqrt_r8.o _sqrt_r10.o _sqrt_r16.o _sqrt_c4.o _sqrt_c8.o _sqrt_c10.o _sqrt_c16.o _asin_r4.o _asin_r8.o _asin_r10.o _asin_r16.o _asinh_r4.o _asinh_r8.o _asinh_r10.o _asinh_r16.o _acos_r4.o _acos_r8.o _acos_r10.o _acos_r16.o _acosh_r4.o _acosh_r8.o _acosh_r10.o _acosh_r16.o _atan_r4.o _atan_r8.o _atan_r10.o _atan_r16.o _atanh_r4.o _atanh_r8.o _atanh_r10.o _atanh_r16.o _sin_r4.o _sin_r8.o _sin_r10.o _sin_r16.o _sin_c4.o _sin_c8.o _sin_c10.o _sin_c16.o _cos_r4.o _cos_r8.o _cos_r10.o _cos_r16.o _cos_c4.o _cos_c8.o _cos_c10.o _cos_c16.o _tan_r4.o _tan_r8.o _tan_r10.o _tan_r16.o _sinh_r4.o _sinh_r8.o _sinh_r10.o _sinh_r16.o _cosh_r4.o _cosh_r8.o _cosh_r10.o _cosh_r16.o _tanh_r4.o _tanh_r8.o _tanh_r10.o _tanh_r16.o _conjg_c4.o _conjg_c8.o _conjg_c10.o _conjg_c16.o _aint_r4.o _aint_r8.o _aint_r10.o _aint_r16.o _anint_r4.o _anint_r8.o _anint_r10.o _anint_r16.o _sign_i4.o _sign_i8.o _sign_i16.o _sign_r4.o _sign_r8.o _sign_r10.o _sign_r16.o _dim_i4.o _dim_i8.o _dim_i16.o _dim_r4.o _dim_r8.o _dim_r10.o _dim_r16.o _atan2_r4.o _atan2_r8.o _atan2_r10.o _atan2_r16.o _mod_i4.o _mod_i8.o _mod_i16.o _mod_r4.o _mod_r8.o _mod_r10.o _mod_r16.o misc_specifics.o dprod_r8.o f2c_specifics.o

libtool: link: ranlib .libs/libgfortran.a

libtool: link: ( cd ".libs" && rm -f "libgfortran.la" && ln -s "../libgfortran.la" "libgfortran.la" )

make[3]: Leaving directory `/root/GCC/src/gcc-build/x86_64-unknown-linux-gnu/libgfortran'

make[2]: Leaving directory `/root/GCC/src/gcc-build/x86_64-unknown-linux-gnu/libgfortran'

make[1]: Leaving directory `/root/GCC/src/gcc-build'

make: *** [all] Error 2

Now, if I try make again I get a completely different error related to libgo, I found http://gcc.gnu.org/ml/gcc-patches/2012-12/msg01378.html and added the fixes, now I get;

/root/GCC/src/gcc-4.7.2/libgo/runtime/print.c: In function ?gwrite?:

/root/GCC/src/gcc-4.7.2/libgo/runtime/print.c:20:3: error: ignoring return value of ?write?, declared with attribute warn_unused_result [-Werror=unused-result]

cc1: all warnings being treated as errors

make[4]: *** [print.lo] Error 1

and I haven't got a clue what to do about this error. Any ideas?

I'm not sure what's goin on with arch to be honest. It was crappy for a bit, then they made it quite stable, and seems like it's gone down hill again. Did a fresh install yesterday, now I can't get cinnamon to load via startx. X just shuts down (no errors or anything). However if I load stock X desktop I can then run cinnamon via xterm and it will load up.

Currently doing another re-install to see if the issue persists.

Get Debian Wheezy, end of story.

Or Ubuntu, seriously, that thing became quite solid, I even managed to get my overclock working on my laptop as I do with windows with K10STAT using TurionPowerControl.

142j.png(specs on my sig,m that's why I'm really impressed)

It runs it all, Cinnamon, MATE, everything.

Installed it in Virtual Box. Install went okay, took me a bit to realize that it doesn't generate the .xinitrc file so I couldn't figure out why it kept booting gnome-shell. Got that all fixed. Found that it doesn't have cinnamon 1.8 available just 1.6 which means the new nemo isn't available either. Using the minty theme seems to freeze cinnamon.

Also I cannot figure out how to enable dark themes for all apps. I can do it via gnome-tweak-tool in Arch but no option in debian.

I'm not sure what's goin on with arch to be honest. It was crappy for a bit, then they made it quite stable, and seems like it's gone down hill again. Did a fresh install yesterday, now I can't get cinnamon to load via startx. X just shuts down (no errors or anything). However if I load stock X desktop I can then run cinnamon via xterm and it will load up.

Currently doing another re-install to see if the issue persists.

Well.. unless you did something to prevent it, you should have gnome 3.8 libs and files and cinnamon wont run with them. Thats why Cinnarch distro was discontinued and the creator made a gnome 3 distro instead. I really liked Cinnarch :(

Installed it in Virtual Box. Install went okay, took me a bit to realize that it doesn't generate the .xinitrc file so I couldn't figure out why it kept booting gnome-shell. Got that all fixed. Found that it doesn't have cinnamon 1.8 available just 1.6 which means the new nemo isn't available either. Using the minty theme seems to freeze cinnamon.

Also I cannot figure out how to enable dark themes for all apps. I can do it via gnome-tweak-tool in Arch but no option in debian.

hmmm i dont know how cinnamon is with fedora, suse or gentoo, but you might want to take a look.. if you are going to stick with debian, in order to get a more updated cinnamon, you may need to change to a ubuntu based distro unfortunatelly

Well.. unless you did something to prevent it, you should have gnome 3.8 libs and files and cinnamon wont run with them. Thats why Cinnarch distro was discontinued and the creator made a gnome 3 distro instead. I really liked Cinnarch :(

Works fine for me Latest Arch, With Latest Cinnamon (1.8). I have some issues with the background being black. But other than that it is working fine.

That's very odd.. I bet you have the older gnome files or I must be very wrong.. On Cinarch cinnamon broke after a simple update - official repos (was kind of functional, but somewhat destroyed).

You're not the only one. I can't get fecking audio CDs to mount in any distro I try! Linux has really been testing my patience lately...

I fixed it! Linux is the shiz again!

1. Rip out IDE DVD Drive

2. Insert SATA DVD Drive

3. ...

4. Profit!

I goz mi U2 naw!!!! Sorry for the thread hijack...

That's very odd.. I bet you have the older gnome files or I must be very wrong.. On Cinarch cinnamon broke after a simple update - official repos (was kind of functional, but somewhat destroyed).

Its because the recent cinnamon 1.8 update fixed most of the gnome 3.8 problems.

I fixed it! Linux is the shiz again!

1. Rip out IDE DVD Drive

2. Insert SATA DVD Drive

3. ...

4. Profit!

I goz mi U2 naw!!!! Sorry for the thread hijack...

So errr what error were you getting whilst attempting to mount the disc? And what command were you using?

Got Debian Wheezy all setup in Virtual Box. Got it looking like my standard Arch installs, took a bit more searching and such to get everything than with Arch. With Arch I can usually have everything installed in ~20 mins with a combination of Pacman and Yaourt. However just finding the packages for things like skype, mono, and sdl took time in themselves.

Overall, no crashes and blow ups so that's good.

debianx.jpg

  • Like 2

well.. it does uses older packages.. not that old, but still... i'm guilty atm because im using elementary os (yeah, ubuntu 12.04 based) but I really loved the work they did there with the interface and everything else.. it just works and the crashes now are minimal

This topic is now closed to further replies.
  • Posts

    • Researchers claim Microsoft's quantum breakthrough is flawed by basic Python errors by Karthik Mudaliar Microsoft's aggressive roadmap to deliver a commercial quantum supercomputer by 2029 has now hit a bit of a snag, and it's not because of a complex sub-zero dilution refrigerator, but rather because of a few lines of basic Python code. A new critique published in the scientific journal Nature argues that simple software errors effectively manufactured the breakthrough that Microsoft's foundational research claimed back in 2025 into Majorana-based topological qubits. Topological quantum computing, the path that Microsoft chose for its research, relies on creating and controlling "Majorana zero modes." These are exotic quasiparticles that theoretically offer vastly superior error resistance compared to the highly sensitive superconducting qubits currently being championed by rivals like Google and IBM. However, physically proving you have created these particles requires sifting through massive amounts of complex electrical conductance data to isolate a specific "topological gap." Because of the sheer volume of data, physicists rely heavily on custom software pipelines to process the results. This is where the Python scripts come in. Now, according to the critique, Microsoft’s data processing software contained fundamental programming errors that ultimately skewed the published results. By mishandling data arrays or deploying incorrect logic within the Python script, the software supposedly discarded "noisy" or contradictory data. Which is why it only highlighted the specific electrical measurements that supported the topological-gap claim. The researchers behind the critique argued that this makes the findings invalid, suggesting the heralded "quantum leap" was actually a false positive generated by bad code and not a product of groundbreaking physics. However, Microsoft is pushing back hard against these allegations. The Redmond giant has formally rejected the criticism, saying that it's just a minor anomaly rather than a fatal flaw. According to the company, while there may have been a minor oversight in the data parsing scripts, it does not alter the fundamental reality of their physical experiment. Just weeks ago, Microsoft unveiled the Majorana 2 quantum processor, a milestone so significant that the company boldly accelerated its timeline for a commercial quantum supercomputer from 2035 down to 2029. But the new software allegations reopen an old wound. Microsoft's quantum division faced a remarkably similar crisis when a landmark 2018 paper on Majorana particles was famously retracted in 2021 after independent physicists discovered the data had been inappropriately cropped. That historical baggage makes the current Python-related allegations particularly sensitive. If the foundational math and data processing for the 2025 breakthrough are genuinely flawed, the highly anticipated 2029 commercial timeline could easily be delayed or, worse, cancelled.
    • Because of what they have done to VMware I will never buy anything Broadcom again.
    • AMD releases hotfix for driver install issues on Windows 10 PCs by Taras Buria Earlier this week, AMD released an important graphics driver update. Version 26.6.2 brought AMD FSR 4.1 support to the previous-gen Radeon lineup, the RX 7000 series, giving users better upscaling tech that was previously locked to the newest GPUs. However, the driver turned out to be a little buggy, with users reporting installation issues on systems still running Windows 10. AMD quickly acknowledged the bug and today released a hotfix to resolve the problem. The AMD 26.6.3 Hotfix update is now available for download from the official website. Given that it is a hotfix release, it has only one change in its release notes: AMD announced the update on its official X account and added that a WHQL driver update with the necessary fixes would be released next week. Meanwhile, users can apply the hotfix or roll back to the previous driver using the official AMD Cleanup Utility. You can download AMD Software: Adrenalin Edition 26.6.3 Hotfix Preview Driver from the official website here. It is compatible with all currently supported graphics cards and 64-bit Windows 10 and 11. Full release notes are available on the same page.
    • With Microsoft now listening to its core audience and acting upon received feedback, fans can finally expect a much better version of Windows 11 than what was available five years ago. Here is to five more years, Windows 11! I guess we all need a good laugh now and again...
  • Recent Achievements

    • Dedicated
      Scoobystu earned a badge
      Dedicated
    • First Post
      Tom Schmidt earned a badge
      First Post
    • One Month Later
      D0nn13 earned a badge
      One Month Later
    • Rookie
      +ChiefOfNeo went up a rank
      Rookie
    • One Year In
      Tom Schmidt earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      465
    2. 2
      +Edouard
      177
    3. 3
      PsYcHoKiLLa
      123
    4. 4
      Michael Scrip
      82
    5. 5
      Xenon
      76
  • Tell a friend

    Love Neowin? Tell a friend!