HowTo: Switch to Linux to finish factoring

[axn]

Originally Posted by Andi47

1.) Is it really possible to see the windows partition? How?
2.) How do I open a prompt window?
3.) How do I install GMP?

1) From "Places" menu. Just play around and see what all you can find.
2) Application > Accessories > Terminal
3) It is probably already installed. But, fireup Synaptics Package Manager (system > administration). Search for: GMP. If it shows up with solid check box, it is installed. Otherwise, check the checkbox, and click Apply.

Whenever prompted for password, enter your password.

PS:- Not sitting in front of the linux box, so things could be not exactly where I said it would be -- but should be close enough

[Andi47]

Originally Posted by axn

1) From "Places" menu. Just play around and see what all you can find.
2) Application > Accessories > Terminal
3) It is probably already installed. But, fireup Synaptics Package Manager (system > administration). Search for: GMP. If it shows up with solid check box, it is installed. Otherwise, check the checkbox, and click Apply.

Whenever prompted for password, enter your password.

PS:- Not sitting in front of the linux box, so things could be not exactly where I said it would be -- but should be close enough

Thanks. I guess the prompt window will be able to see and access to data (e.g. a msieve.dat file) on the windows partition too? Just type "c:" to go there?

(I will try tonight, as I am currently not sitting in front of my linux box, too.)

[axn]

Originally Posted by Andi47

Just type "c:" to go there?

No. It has a more funky syntax, I think. Basically when you access it from "Places", it will be mounted as a volume, and then you access it like any other linux folder (/whatever/blah/.../msieve.dat)

[Andi47]

Originally Posted by axn

other than that, compiling is as easy as downloading msieve source and doing a "make x86_64" command.

downloaded msieve 1.42, unpacked it, typed this command and got (translated the german output to english):

GMP: libgmp3c2 is installed (as far as I understand; if I click onto the box next to the entry, it asks if I want to uninstall it; of course; I answered "no"), I guess, this will do?

The selected CPU does not support the X64 command set [note: german: Befehlssatz]

Huh? it's ubuntu (64 bit version) running on a core 2 duo laptop!

Should I try to type just "make"?

[henryzz]

you have to edit the makefile for 64-bit(wish this would be fixed(i havent checked svn recently))
comment out with a #
OPT_FLAGS = -O3 -fomit-frame-pointer -march=athlon-xp -DNDEBUG
and uncomment
OPT_FLAGS = -O3 -fomit-frame-pointer -march=k8 -DNDEBUG

[jrk]

Originally Posted by henryzz

you have to edit the makefile for 64-bit(wish this would be fixed(i havent checked svn recently))
comment out with a #
OPT_FLAGS = -O3 -fomit-frame-pointer -march=athlon-xp -DNDEBUG
and uncomment
OPT_FLAGS = -O3 -fomit-frame-pointer -march=k8 -DNDEBUG

Since he has a Core 2 duo, shouldn't he use -march=core2 instead?

OPT_FLAGS = -O3 -fomit-frame-pointer -march=core2 -DNDEBUG

[bsquared]

Originally Posted by jrk

Since he has a Core 2 duo, shouldn't he use -march=core2 instead?

OPT_FLAGS = -O3 -fomit-frame-pointer -march=core2 -DNDEBUG

I think it should be -march=nocona for core2. I've vague recollections of this (k8 vs. nocona) not mattering too much... but it makes sense to use the architecture flag you'll be using it on.

[Andi47]

Originally Posted by jrk

Since he has a Core 2 duo, shouldn't he use -march=core2 instead?

OPT_FLAGS = -O3 -fomit-frame-pointer -march=core2 -DNDEBUG

I have now tried with -march=core2 and got dozens of warnings that sound like:

Warning: conversion into "unit32" from "long int" could change the value.

Is this normal?

Edit: -march=nocona gives the same bunch of warnings.

After compilation, I copied msieve.exe into my 2,1766M-directory and tried to start msieve -v -p -nc2 -t 2 and got:

bash: msieve: command not found

[fivemack]

That's fine, it's just that the newest gcc is a little more paranoid about type conversion than previous ones were. Try 'msieve -v 11111111111111111111111111111111111111111111111111111111111111111111111' and check that you get factors ...

[Andi47]

Originally Posted by fivemack

That's fine, it's just that the newest gcc is a little more paranoid about type conversion than previous ones were. Try 'msieve -v 11111111111111111111111111111111111111111111111111111111111111111111111' and check that you get factors ...

I get

bash: msieve: command not found

[Mini-Geek]

Originally Posted by Andi47

I get

bash: msieve: command not found

Use ./msieve to start the command. For some reason, Linux won't look in the current directory for the file name you specify unless you do that. I think the "./" might mean "current directory" or something.