Sign in Join

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

Mailing lists / lazarus / 2016-02

Problem with lazarus + fpc-3.0.0 under windows 10

3 messages · 1 person · –

Reply by email Subscribe to this list Your subscription

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

Zeljko

1.Fpc-3.0.0
2.Lazarus today trunk.
3.Windows 10 pro 64bit in vmware virtual machine

Builds fine, works fine. Now I'm trying to install dozen of my own packages...last one is virtualtrees package, in message window I can see: Linking lazarus... and then Fatal: no memory left

Tested with pure win32 and qt widgetsets under windows 10 pro.

So, anyone spotted such problem ? That works fine with fpc-2.6.4 (virtual machine also but with Win7 64 pro)
Is there any workaround ?

zeljko

Reply by email

Zeljko
to Zeljko
Zeljko wrote 13 lines
1.Fpc-3.0.0 2.Lazarus today trunk. 3.Windows 10 pro 64bit in vmware virtual machine Builds fine, works fine. Now I'm trying to install dozen of my own packages...last one is virtualtrees package, in message window I can see: Linking lazarus... and then Fatal: no memory left Tested with pure win32 and qt widgetsets under windows 10 pro. So, anyone spotted such problem ? That works fine with fpc-2.6.4 (virtual machine also but with Win7 64 pro) Is there any workaround ?

Sorry, it's not fpc-3.0.0 but fpc-3.1.1 from 18.01.2016 ... so I'll test tomorrow with 3.0.0 stable and see if error still exists.

zeljko

Reply by email

Zeljko
to Zeljko
Zeljko wrote 19 lines
On 02/24/2016 03:20 PM, Zeljko wrote: > 1.Fpc-3.0.0 > 2.Lazarus today trunk. > 3.Windows 10 pro 64bit in vmware virtual machine > > Builds fine, works fine. Now I'm trying to install dozen of my own > packages...last one is virtualtrees package, in message window I can see: > Linking lazarus... and then Fatal: no memory left > > Tested with pure win32 and qt widgetsets under windows 10 pro. > > So, anyone spotted such problem ? That works fine with fpc-2.6.4 > (virtual machine also but with Win7 64 pro) > Is there any workaround ? Sorry, it's not fpc-3.0.0 but fpc-3.1.1 from 18.01.2016 ... so I'll test tomorrow with 3.0.0 stable and see if error still exists.

FYI, works ok with fpc-3.0.0.

z.

Reply by email