Hi, all
Trying to compile a program, I suddenly see:
Internal GPC problem: internal option '--amtmpfile' not given
I had compiled the program successfully a few minutes earlier.
I get this problem with every program that USES GRX that I attempt to compile. But When I attempt to compile a program that doesn't USE GRX, I see
cannot file -lgcc
Any guesses? GPC was working fine for me a few weeks ago. I'm using 2.1 (20020510) based upon 2.95.3 (20010315), under win2000, installed only a few months ago.
thanks, Toby
On 4 Apr 2003 at 16:55, Toby Ewing wrote:
Hi, all
Trying to compile a program, I suddenly see:
Internal GPC problem: internal option '--amtmpfile' not given
I had compiled the program successfully a few minutes earlier.
I get this problem with every program that USES GRX that I attempt to compile. But When I attempt to compile a program that doesn't USE GRX, I see
cannot file -lgcc
Any guesses? GPC was working fine for me a few weeks ago. I'm using 2.1 (20020510) based upon 2.95.3 (20010315), under win2000, installed only a few months ago.
Sounds like an installation problem. Did you install something else recently?
What are the outputs of these commands: "gpc -print-search-dirs"
and
"gpc -print-file-name=libgcc.a"
Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) web: http://www.bigfoot.com/~african_chief/
Le Dimanche 6 Avril 2003 21:54, Prof A Olowofoyeku (The African Chief) a écrit :
On 4 Apr 2003 at 16:55, Toby Ewing wrote:
Hi, all
Trying to compile a program, I suddenly see:
Internal GPC problem: internal option '--amtmpfile' not given
I had compiled the program successfully a few minutes earlier.
I get this problem with every program that USES GRX that I attempt to compile. But When I attempt to compile a program that doesn't USE GRX, I see
cannot file -lgcc
Any guesses? GPC was working fine for me a few weeks ago. I'm using 2.1 (20020510) based upon 2.95.3 (20010315), under win2000, installed only a few months ago.
Sounds like an installation problem. Did you install something else recently?
Could be a hardware problem also, I met such situations twice in the past, one with a failing memory chip (random failure) an once with a failing cooling fan (happened after some time of work, depending on ambiant temperature.