| View previous topic :: View next topic |
| Author |
Message |
craftyc
Guru
Joined: 23 May 2002
Posts: 443
Location: Behind You.
|
 Posted: Wed Aug 28, 2002 7:04 pm Post subject: Problems with memtest86 |
 |
|
When I try to emerge memtest86 I get this.
| Code: | chandegra root # emerge memtest86
Calculating dependencies ...done!
>>> emerge sys-apps/memtest86-3.0 to /
>>> md5 ;-) memtest86-3.0.tar.gz
>>> Unpacking source...
>>> Unpacking memtest86-3.0.tar.gz
>>> Source unpacked.
gcc -E -traditional head.S -o head.s
gcc -c -fPIC -Wall -g -O2 -fno-strict-aliasing reloc.c
gcc -c -Wall -march=i486 -O -fomit-frame-pointer -fno-builtin -fPIC main.c
gcc -c -Wall -march=i486 -O -fomit-frame-pointer -fno-builtin test.c
test.c:12: conflicting types for `v'
test.h:280: previous declaration of `v'
make: *** [test.o] Error 1
make: *** Waiting for unfinished jobs....
!!! ERROR: The ebuild did not complete successfully.
!!! Function src_compile, Line 1, Exitcode 2
!!! (no error message)
!!! emerge aborting on /usr/portage/sys-apps/memtest86/memtest86-3.0.ebuild .
|
Anybody know what's going wrong?
Thanks.
_________________
Postcount ++ |
|
| Back to top |
|
 |
BonezTheGoon
Bodhisattva
Joined: 14 Jun 2002
Posts: 1408
Location: Albuquerque, NM -- birthplace of Microsoft and Gentoo
|
| Posted: Wed Aug 28, 2002 9:35 pm Post subject: |
|
|
Well quite plainly this is a problem with the ebuild. The compiler is complaining that in the code 'v' is declared twice and the two declarations are even of different types (meaning one could be an int while another is a char). One reference is in test.c line twelve and the other is test.h line two hundred eighty. This would appear (to me) to be a problem with the source code not really with the ebuild, but the ebuild should have tested this. It is possible the source has been changed and the ebuild needs updating.
No matter, a bug report should be filed-- please do so here. Also please post a reply to this thread with your bug report number so that others can easily find and reference it.
Regards,
BonezTheGoon
[edit] Added link to file bug report [/edit] |
|
| Back to top |
|
|
rac
Bodhisattva
Joined: 30 May 2002
Posts: 6553
Location: Japanifornia
|
| Posted: Wed Aug 28, 2002 11:45 pm Post subject: |
|
|
It appears to be already entered as bug #4088, opened 2002-06-24.
_________________
For every higher wall, there is a taller ladder |
|
| Back to top |
|
|
xorbe
n00b
Joined: 19 Jul 2002
Posts: 46
Location: near San Jose, CA
|
| Posted: Thu Aug 29, 2002 5:41 am Post subject: |
|
|
I never did get 3.0 to run on my system, I have to use 2.9. 3.0 just displays "Memtest86" and locks up.  |
|
| Back to top |
|
|
craftyc
Guru
Joined: 23 May 2002
Posts: 443
Location: Behind You.
|
| Posted: Fri Aug 30, 2002 11:05 am Post subject: |
|
|
OK so I'll just wait for it to be fixed. No probs.
_________________
Postcount ++ |
|
| Back to top |
|
|
nexus
n00b
Joined: 14 Aug 2002
Posts: 13
Location: Hamburg
|
| Posted: Sat Sep 07, 2002 5:40 pm Post subject: |
|
|
Probably I have the same problem like xorbe.
I downloaded memtest86-3.0 and patched it.
After that I compiled it without errors.
But after rebooting into the memtest kernel it just displayed memtest86 and nothing happened.
Anybody knows a solution ?
Or how can I use memtestx86-2.9 ?
Can't find this older version  |
|
| Back to top |
|
|
|
Other Things Gentoo
