Home > Could Not > Could Not Run Locate I386 Pc Linux Gnu

Could Not Run Locate I386 Pc Linux Gnu

Function src_compile, Line 20, Exitcode 1 !!! (no error message) !!! wrote: >Hello! > >Trying to compile groff-1.19.1-r2 I had the error: >gcc-config error: Could not run/locate "i386-pc-linux-gnu-gcc" >make: *** [xditview.o] Error 1 > >In my make.conf file I have CHOST="i686-pc-linux-gnu". > Zac -- gentoo-user [at] gentoo mailing list zmedico at gmail Jun12,2005,3:06AM Post #6 of 8 (157 views) Permalink Re: gcc-config error: Could not run/locate "i386-pc-linux-gnu-gcc" [In reply to] Zac Medico wrote: > askar I wanted to run distcc, to let my faster box help my slower box out on long compiles. have a peek at this web-site

How can I get distcc to just use the generic "gcc"? Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started In particular, the three-post series in the middle of the page by amne, danielrendell and Bob P give a pretty clear idea of what it should take, and what I decided Find More Posts by Matir 04-29-2005, 10:52 AM #2 Crashed_Again Senior Member Registered: Dec 2002 Location: Atlantic City, NJ Distribution: Ubuntu & Arch Posts: 3,503 Rep: If you remove https://forums.gentoo.org/viewtopic-t-321340.html

Can anybody tell how to solve this problem? In config.log for the ebuild, the following error was given: Code: Could not run/locate "i386-pc-linux-gnu-gcc" This is most likely because the CHOST on the computer it was trying to compile on If you need support, post the topmost build error, NOT this statusmessage.--Vladimir Solomatin ([hidden email])Phone: + 7 (0732) 711711Relex Inc, Voronezh.--[hidden email] mailing list Vladimir Solomatin Reply | Threaded Open this wrote: > Thank you, Zac! > > I recompiled xorg-x11 and the compilation groff were successful. > Next time I will take into account your advice concerning > /usr/lib/X11/config/host.def. > >

I kicked off my first emerge of the build tools. I figured, since I'm trying to compile something related to Perl, perhaps Perl is the problem. Assume that your machine will end up fragged, and act accordingly. This tells emerge to remove the 'X' use flag just for groff.

Sure enough, I got the same error. Not helped. Crashed_Again View Public Profile View LQ Blog View Review Entries View HCL Entries Visit Crashed_Again's homepage! my response Post your question in this forum.

YMMV.Enjoy. Wednesday, April 05, 2006 Changing Gentoo's CHOST from i386 to i686 I'm running Gentoo, kept pretty much up-to-date. Having finished the process, apparently successfully, I'm writing up what it took. Function src_compile, Line 20, Exitcode 1!!! (no error message)!!!

LinuxQuestions.org > Forums > Linux Forums > Linux - Software Gentoo, distcc, and CHOSTs. I have a rather slow computer on which I run gentoo, but would like to farm out compiles to my faster machines. That worked fine. wrote: >>>Trying to compile groff-1.19.1-r2 I had the error: >>>gcc-config error: Could not run/locate "i386-pc-linux-gnu-gcc" >>>make: *** [xditview.o] Error 1 >>> >>>In my make.conf file I have CHOST="i686-pc-linux-gnu". >>> >>>I see

I saw that imake was creating this, and used equery to find out where imake was coming from (assuming it was part of make, and that rebuilding make might fix things). http://strobelfilms.com/could-not/could-not-start-kstartupconfig-linux.html Portage version? No dice, 'equery belongs imake' reported x11-base/xorg-x11.So now I'm confused. User Name Remember Me?

you also need to add an option to fix thechanged CHOSTfix_libtool_files.sh 3.4.4 --oldarch i386-pc-linux-gnuRun it with no arguments for an explanation of the options.--Neil BothwickIf you think you know what I They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. Matir View Public Profile View LQ Blog View Review Entries View HCL Entries View LQ Wiki Contributions Visit Matir's homepage! http://strobelfilms.com/could-not/could-not-run-locate-i486-pc-linux-gnu-gcc.html Ran emerge just on groff, and this time it worked.

Same problemorbit-idl-2 2.12.0 compilingmode, show preprocessor errors, passes: stubs skels common headersskel_impl imodulegcc-config error: Could not run/locate "i386-pc-linux-gnu-gcc"Error: Empty file** (process:11762): WARNING **: nautilus-view-component.idl compilation failedmake[3]: *** [nautilus_view_component_idl_stamp] Error 1What to GPG Public Key available upon request or from pgp.mit.edu's public key server. ---------------------------------------------------- Attachments: signature.asc (0.18 KB) ted1 at telus Jun12,2005,12:55AM Post #3 of 8 (142 views) Permalink Re: gcc-config error: Could not You probably need to 'source /etc/profile' !!!

I checked /etc, no references to i386 anywhere.I checked my environment, and found a couple of i386 mentions, in BASH_VERSINFO, HOSTTYPE and MACHTYPE.

This let me to want to change my CHOST variable on the slower box from i386-pc-linux-gnu to i686-pc-linux-gnu, to match my faster box. Skip to content Another blog bites the dust Not biting dust since 2005 Menu and widgets A blog by Eran Sandler About / Contact Me elsewhere @erans [email protected] [email protected] forecastcloudy.net Opinions fell into three camps: a) DON'T DO IT!, b) you can, but it's hard and not for the faint of heart, and c) I did it, no sweat. askar > I was curious if I could reproduce your problem so I edited /usr/lib/X11/config/host.def and changed it to #define CcCmd i386-pc-linux-gnu-gcc.

You can try editing that file if you don't want to recomplile xorg-xll. >> >>Zac > > -- gentoo-user [at] gentoo mailing list Index | Next | Previous | Print I supposed you could have grepped all the files on your system for i386-pc-linux-gnu-gcc but that wouldn't have been a very efficient way to go about it. ;-) Zac askar ... Sure enough, I got the same error. have a peek here I see this is one of the often occured promblems, when system reference to i386 instead i686...

It solved both problems....Thanks!--Arnau Briahttp://blog.emergetux.net- Mama, mama en el colegio me llaman Friki- ¿Y tú que haces?- Me quito dos puntos de carisma.--gentoo-***@gentoo.org mailing list 3 Replies 6 Views Switch to [email protected] Discussion: i386-pc-linux-gnu-gcc broken (too old to reply) Lubos Kolouch 2005-04-27 16:46:03 UTC PermalinkRaw Message Hello,(after hours of googling)When I do emerge kdegraphics (but also other packages) the compilationends with error Main Menu LQ Calendar LQ Rules LQ Sitemap Site FAQ View New Posts View Latest Posts Zero Reply Threads LQ Wiki Most Wanted Jeremy's Blog Report LQ Bug Syndicate Latest Lubos Kolouch 2005-05-03 10:48:34 UTC PermalinkRaw Message Post by Neil BothwickPost by Lubos Kolouchhow to convince liborbit not to use i386-.... ?Have you changed CHOST in /etc/make.conf?--Neil BothwickNo.

I kicked off my second tool emerge, and got an error running emerge, saying that Python couldn't find libstdc++.so.6.