Подробно объясним как исправить ту или иную ошибку самым простым способом на Oshibkino.ru
Make error 139
Seems mnist8m dataset is downloadable now. #541 But I get another error make: *** [mnist8m.model] Error 139 gcc --version gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3 make mnist8m.test.confusion ./do-m...
Unfortunately, I cannot reproduce on my local machine (ubuntu 14.04).
Seems it was second run, after dataset was downloaded.
Yes, I google for |Error 139| one of the possible reasons is |old
version of GCC| so I posteed output of |gcc —version|. Also I use
|Ubuntu 12.04.5 LTS|.
I get the latest version from github via |git clone| and seems
compilation via |make| runs smoothly.
Only one warning:
cb_adf.cc: In function ‘void CB_ADF::get_observed_cost(cb_adf&,
v_array&)’:
cb_adf.cc:181:5: warning: ‘cl’ may be used uninitialized in this
function [-Wuninitialized]
Also I run |make test| and all test passed.
Here is full log:
|make mnist8m.test.confusion
wget http://leon.bottou.org/_media/projects/infimnist.tar.gz
—2015-08-12 11:43:00— http://leon.bottou.org/_media/projects/infimnist.tar.gz
Resolving leon.bottou.org (leon.bottou.org)… 128.122.47.89
Connecting to leon.bottou.org (leon.bottou.org)|128.122.47.89|:80… connected.
HTTP request sent, awaiting response… 200 OK
Length: 365872710 (349M) [application/octet-stream]
Saving to: `infimnist.tar.gz’
100%[======================================>] 365,872,710 582K/s in 10m 38s
Limitations:
This download is a free evaluation version. To unlock all features and tools, a purchase is required.
Make Error Code 139 Error Codes are caused in one way or another by misconfigured system files
in your windows operating system.
If you have Make Error Code 139 errors then we strongly recommend that you
Download (Make Error Code 139) Repair Tool.
This article contains information that shows you how to fix
Make Error Code 139
both
(manually) and (automatically) , In addition, this article will help you troubleshoot some common error messages related to Make Error Code 139 error code that you may receive.
Note:
This article was updated on 2023-02-03 and previously published under WIKI_Q210794
Contents
1. What is Make Error Code 139 error?
2. What causes Make Error Code 139 error?
3. How to easily fix Make Error Code 139 errors
What is Make Error Code 139 error?
The Make Error Code 139 error is the Hexadecimal format of the error caused. This is common error code format used by windows and other windows compatible software and driver vendors.
This code is used by the vendor to identify the error caused. This Make Error Code 139 error code has a numeric error number and a technical description. In some cases the error may have more parameters in Make Error Code 139 format .This additional hexadecimal code are the address of the memory locations where the instruction(s) was loaded at the time of the error.
What causes Make Error Code 139 error?
The Make Error Code 139 error may be caused by windows system files damage. The corrupted system files entries can be a real threat to the well being of your computer.
There can be many events which may have resulted in the system files errors. An incomplete installation, an incomplete uninstall, improper deletion of applications or hardware. It can also be caused if your computer is recovered from a virus or adware/spyware
attack or by an improper shutdown of the computer. All the above actives
may result in the deletion or corruption of the entries in the windows
system files. This corrupted system file will lead to the missing and wrongly
linked information and files needed for the proper working of the
application.
How to easily fix Make Error Code 139 error?
There are two (2) ways to fix Make Error Code 139 Error:
Advanced Computer User Solution (manual update):
1) Start your computer and log on as an administrator.
2) Click the Start button then select All Programs, Accessories, System Tools, and then click System Restore.
3) In the new window, select «Restore my computer to an earlier time» option and then click Next.
4) Select the most recent system restore point from the «On this list, click a restore point» list, and then click Next.
5) Click Next on the confirmation window.
6) Restarts the computer when the restoration is finished.
Novice Computer User Solution (completely automated):
1) Download (Make Error Code 139) repair utility.
2) Install program and click Scan button.
3) Click the Fix Errors button when scan is completed.
4) Restart your computer.
How does it work?
This tool will scan and diagnose, then repairs, your PC with patent
pending technology that fix your windows operating system registry
structure. basic features: (repairs system freezing and rebooting issues , start-up customization , browser helper object management , program removal management , live updates , windows structure repair.)
Any help is appreciated…. _________________ «I’m a Snake if we Disagree» — Jethro Tull, «Bungle in the Jungle»
Back to top
Genone Retired Dev
Joined: 14 Mar 2003 Posts: 9380 Location: beyond the rim
Posted: Wed Jun 13, 2007 12:17 am Post subject:
Does it always fail at the exact same location? Then try remerging qt. If it fails at different locations you’re probably having hardware problems.
Back to top
Rinkhals Apprentice
Joined: 02 May 2003 Posts: 165 Location: Scotland
Posted: Wed Jun 13, 2007 5:30 am Post subject:
Genone,
Thanks very much for your help.
How do you mean «at the exact same location»?
It always fails installing kdemultimedia-3.5.5.
This is not a new installation on this machine and it had been working fine.
However, I have had a problem with the sound card lately. Alsa complains that it cannot find the module «off». Clearly this module does not exist and is the result of some configuration file being corrupted (possibly a <name>/<value> pair being accidentally split over two lines). _________________ «I’m a Snake if we Disagree» — Jethro Tull, «Bungle in the Jungle»
Back to top
Genone Retired Dev
Joined: 14 Mar 2003 Posts: 9380 Location: beyond the rim
Does the segmentation fault always appear at that specific line or are the filenames different each time it fails? (I assume you tried it more than once)
Quote:
This is not a new installation on this machine and it had been working fine.
Doesn’t really matter. There are so many sources of problems that stuff can break out of the blue.
Quote:
However, I have had a problem with the sound card lately. Alsa complains that it cannot find the module «off». Clearly this module does not exist and is the result of some configuration file being corrupted (possibly a <name>/<value> pair being accidentally split over two lines).
Completely unrelated (unless you have a disk problem).
Back to top
Rinkhals Apprentice
Joined: 02 May 2003 Posts: 165 Location: Scotland
Posted: Wed Jun 13, 2007 6:54 am Post subject:
Genone wrote:
Does the segmentation fault always appear at that specific line or are the filenames different each time it fails? (I assume you tried it more than once)
I’ll check the log files and get back to you, but, from memory, it’s the same filename.
Code:
/bin/sh: line 3: 18429 Segmentation fault /usr/qt/3/bin/uic -L
Certainly the log files belong to kdemultimedia-3.5.5 _________________ «I’m a Snake if we Disagree» — Jethro Tull, «Bungle in the Jungle»
Back to top
Rinkhals Apprentice
Joined: 02 May 2003 Posts: 165 Location: Scotland
Posted: Wed Jun 13, 2007 5:01 pm Post subject:
Hi, Genone.
The following are excepts from 4 of the log files. All log files are kdemultimedia-3.5.5 and appear to have something to do with kaudiocreator.
kdemultimedia-3.5.5.ebuild, line 89: Called kde_src_compile
kde.eclass, line 170: Called kde_src_compile ‘all’
kde.eclass, line 340: Called kde_src_compile ‘myconf’ ‘configure’ ‘make’
kde.eclass, line 336: Called die
!!! died running emake, kde_src_compile:make
!!! If you need support, post the topmost build error, and the call stack if relevant.
!!! A complete build log is located at ‘/var/log/portage/kde-base:kdemultimedia-3.5.5:20070612-163536.log’.
I hope this gives you some idea of what is going on. I’m a bit stymied…. _________________ «I’m a Snake if we Disagree» — Jethro Tull, «Bungle in the Jungle»
Back to top
Rinkhals Apprentice
Joined: 02 May 2003 Posts: 165 Location: Scotland
Posted: Fri Jun 15, 2007 9:41 am Post subject:
Got everyone stumped, eh? _________________ «I’m a Snake if we Disagree» — Jethro Tull, «Bungle in the Jungle»
Back to top
Genone Retired Dev
Joined: 14 Mar 2003 Posts: 9380 Location: beyond the rim
Posted: Fri Jun 15, 2007 2:29 pm Post subject:
As I said, try remerging qt.
Back to top
Rinkhals Apprentice
Joined: 02 May 2003 Posts: 165 Location: Scotland
Posted: Fri Jun 15, 2007 10:22 pm Post subject:
Genone wrote:
As I said, try remerging qt.
Genone, your assistance is very much appreciated.
Yes, I tried that. I found the suggestion in a thread here a couple of days ago, but I can’t find it any more.
In any case, it hasn’t helped and I get the same error. _________________ «I’m a Snake if we Disagree» — Jethro Tull, «Bungle in the Jungle»
Back to top
Arfrever Bodhisattva
Joined: 29 Apr 2006 Posts: 2463 Location: 異世界
Posted: Fri Jun 15, 2007 10:27 pm Post subject:
Rinkhals wrote:
Yes, I tried that. I found the suggestion in a thread here a couple of days ago, but I can’t find it any more.
In any case, it hasn’t helped and I get the same error.
Are you sure that you remerged the appropriate slot of qt? Try:
Code:
emerge -1 qt:3
Perduodu linkėjimus
Arfrever
Back to top
Rinkhals Apprentice
Joined: 02 May 2003 Posts: 165 Location: Scotland
Posted: Sat Jun 16, 2007 9:54 pm Post subject:
Hi Arfrever,
I was certain that I had tried that command, but to be sure, I typed it as you had written it.
In any case, the error is the same….. _________________ «I’m a Snake if we Disagree» — Jethro Tull, «Bungle in the Jungle»
Back to top
Arfrever Bodhisattva
Joined: 29 Apr 2006 Posts: 2463 Location: 異世界
Posted: Sat Jun 16, 2007 10:53 pm Post subject:
Install «gdb», if you don’t have it.
Next post the output of:
Code:
cd /var/tmp/portage/kde-base/kdemultimedia-3.5.5/work/kdemultimedia-3.5.5/kaudiocreator
if test «$ret» = 0; then echo ‘#include «main_buttons_widget_ui.moc»‘ >> main_buttons_widget_ui.cpp; else rm -f main_buttons_widget_ui.cpp ; exit $ret ; fi
This is after some desperate things like emerge -e world… I don’t even remember what was the tiny new package which made all this mess while adding it…
Thanks for any ideas,
Rez
Back to top
Rinkhals Apprentice
Joined: 02 May 2003 Posts: 165 Location: Scotland
Posted: Fri Jun 22, 2007 4:34 pm Post subject:
Hi Rez.
I’m at a bit of a loss to know what to do next.
What hardware are you using? _________________ «I’m a Snake if we Disagree» — Jethro Tull, «Bungle in the Jungle»
Back to top
Arfrever Bodhisattva
Joined: 29 Apr 2006 Posts: 2463 Location: 異世界
Posted: Fri Jun 22, 2007 4:51 pm Post subject:
It seems I forgot about «./encoderedit.ui» in command line.
Post the output of:
Code:
cd /var/tmp/portage/kde-base/kdemultimedia-3.5.5/work/kdemultimedia-3.5.5/kaudiocreator
We can’t help you without additional data. Read this.
Perduodu linkėjimus
Arfrever
Back to top
Spanik l33t
Joined: 12 Dec 2003 Posts: 813 Location: Belgium
Posted: Sat Jun 23, 2007 5:35 pm Post subject:
Can you explain this in language understandable by ordinary mortals? Really, I read it but the effect was the same as reading legalese mumbo-jumbo voodoo… I have no idea what it is about.
Only thing I understood was a reply from didymos here: https://forums.gentoo.org/viewtopic-t-566689.html Which IMHO tranlates as: «you got an error. We don’t know what it is and don’t care because we don’t see it. F…O..». Honest I suppose, but not really helpful. I’m looking at a blue screen when I start it now so I fear any other suggestions come too late. I’m going for a re-install. I fear that there the same error will crop up with the same help… _________________ Expert in non-working solutions
Back to top
Rinkhals Apprentice
Joined: 02 May 2003 Posts: 165 Location: Scotland
Posted: Tue Jun 26, 2007 8:26 am Post subject:
Arfrever wrote:
It seems I forgot about «./encoderedit.ui» in command line.
Post the output of:
Code:
cd /var/tmp/portage/kde-base/kdemultimedia-3.5.5/work/kdemultimedia-3.5.5/kaudiocreator
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 46912539384928 (LWP 4413)]
0x0000000000000000 in ?? ()
(gdb) quit
The program is running. Exit anyway? (y or n)
_________________ «I’m a Snake if we Disagree» — Jethro Tull, «Bungle in the Jungle»
Back to top
Arfrever Bodhisattva
Joined: 29 Apr 2006 Posts: 2463 Location: 異世界
Posted: Tue Jun 26, 2007 2:17 pm Post subject:
Rinkhals wrote:
Code:
[New Thread 46912539384928 (LWP 4413)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 46912539384928 (LWP 4413)]
0x0000000000000000 in ?? ()
So segmentation fault happens inside Qt. It’s possible that Qt should be compiled with newer compiler. Didymos in this topic suggested upgrade of GCC and next reemerging all packages.
Perduodu linkėjimus
Arfrever
Back to top
Rinkhals Apprentice
Joined: 02 May 2003 Posts: 165 Location: Scotland
Posted: Tue Jun 26, 2007 6:52 pm Post subject:
Hi,
Yes, I searched before for answers to this problem and indeed came across that thread.
As a result, I did upgrade GCC and other packages, but will have to confirm which packages were upgraded.
As I mentioned, I am away from the PC at the moment and am unable to do much until next week.
Thanks once again for your assistance…. _________________ «I’m a Snake if we Disagree» — Jethro Tull, «Bungle in the Jungle»
Back to top
marcan n00b
Joined: 23 Oct 2006 Posts: 8
Posted: Wed Jun 27, 2007 2:51 pm Post subject:
I’m getting the same problem and I just fixed it. See here:
The problem seems to be old KDE plugins. In particular, I had 3.2, 3.3, 3.4, and 3.5 in /usr/kde (!). Moving 3.3 somewhere else fixed the problem.
As I write this I’m looking for the source of the problem. Even if there are old KDE libs around, they shouldn’t get referenced for any reason. Turns out there are KDE 3.3 references in /usr/qt/3/etc/settings/qtrc. Removing the references (or the entire file) fixed the problem as well, without having to move /usr/kde/3.3 anywhere.
Hope that helps. Note that there are some references in /usr/qt/3/etc/settings/qt_plugins_3.3rc as well. If the above doesn’t help, try removing those too.
I’m also removing old KDE packages from my system anyway, to free up some space.
Back to top
Rinkhals Apprentice
Joined: 02 May 2003 Posts: 165 Location: Scotland
Posted: Wed Jul 04, 2007 8:40 pm Post subject:
marcan wrote:
Hope that helps.
Yes it did!
That was obviously the problem!
thanks for the help! _________________ «I’m a Snake if we Disagree» — Jethro Tull, «Bungle in the Jungle»
Back to top
Display posts from previous:
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
I’m running Linux Mint with kernel version 3.8.0-29-generic. So I downloaded and extracted the Linux Kernel 3.8.9 source code and placed the folder in the main directory. Now using the command make menuconfig in the gnome-terminal I get the make error message:
So I did a memory test before booting up and there are no memory errors. So what’s the problem? FTR I am using a Toshiba satellite L500 with x86_64 architecture. It was suggested by someone else that the kernel source is not configured for this architecture….And if that’s the case where might I find a Linux kernel that works for x86_64?
The reason I’m trying to do this is in preparation to build the kernel source in order to create a kernel module: Is that even necessary with the Kernel already installed???
asked Nov 26, 2013 at 20:13
No, the kernel source is architecture-independant. Although some not really supported ancient architectures (f.e. 32bit MIPS) could need local patches, x86_64 isn’t one of them.
Try to increase verbosity to see, what this make does. Maybe the segfault happens not in the compiler, but in the just compiled fixdep binary.
In both cases, there is a major problem with your kernel source or with your system.
(You could yet give a try a complete new kernel source download/uncompress, if it broke somehow, then all will be ok)
So apparently I thought that the makefile script was using the headers in the /usr/src/linux-headers-3.8.0-29-generic/ folder but it also makes use of the GCC headers in /usr/lib/gcc/x86_64-linux-gnu/4.7.3/include/ folder. As it turns out, many others got the same error(segmentation fault: Error 139). And from the error messages is was the fixdep executable file which was a target of the makefile in the /scripts/basic/ folder whose source code is fixdep.c. One site said something about the «CONFIG_MODULE» listing and I noticed that uses the memcmp function. I had defined that function using some hackneyed inline assembly code I got from somewhere and placed in in the header. So I rewrote that using standard c code and that eliminated the segmentation error entirely!
I guess that inline assembly code may have been trying to access protected memory which can cause a segmentation error.
