Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-devel / 2017-09

Can't compile FPC trunk x86_64-win64

4 messages · 2 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Ondrej Pokorny

Hello,

I can't compile latest trunk for x86_64-win64: the first error message is:

system.pp(136,18) Error: invalid register name

i386-win32 compiles fine.

Ondrej

Reply by email

Sven Barth
"Ondrej Pokorny" wrote 8 lines
Hello, I can't compile latest trunk for x86_64-win64: the first error message is: system.pp(136,18) Error: invalid register name i386-win32 compiles fine.

Are you sure that you're compiling with the correct compiler? Cause that sounds quite like you're trying to compile the Win64 RTL with a i386 compiler.

Also Jenkins reports no build errors, so that is probably indeed a problem on your side...

Regards,
Sven

Reply by email

Ondrej Pokorny
to Sven Barth
Sven Barth wrote 7 lines
Are you sure that you're compiling with the correct compiler? Cause that sounds quite like you're trying to compile the Win64 RTL with a i386 compiler. Also Jenkins reports no build errors, so that is probably indeed a problem on your side...

Yes, the problem was on my side. I use a batch script with SET mypath=myvalue configuration. I ran both batch scripts for i386 and x64 at the same time - and there was a collision in the environment variables. I didn't figure it out yesterday :)

Thanks
Ondrej

Reply by email

Sven Barth
to Ondrej Pokorny
"Ondrej Pokorny" wrote
On 30.09.2017 0:10, Sven Barth via fpc-devel wrote: > > Are you sure that you're compiling with the correct compiler? Cause that

sounds quite like you're trying to compile the Win64 RTL with a i386 compiler.

> > Also Jenkins reports no build errors, so that is probably indeed a

problem on your side...

> Yes, the problem was on my side. I use a batch script with SET

mypath=myvalue configuration. I ran both batch scripts for i386 and x64 at the same time - and there was a collision in the environment variables. I didn't figure it out yesterday :)

Thought so :P
Ah, the joys of batch scripts...

Regards,
Sven

Reply by email