[SOLVED] Newpascal Error while linking

[tk]

This is maybe a silly question but I could not find any usable info to resolve this error:

Code: [Select]

Compile Project, OS: linux, Target: C:\Users\tk\AppData\Local\Temp\project1: Exit code 1, Errors: 1
project1.lpr(20,1) Error: Error while linking

I use newpascal distribution on Win7/x64 and try to crosscompile for linux i386 for the first time (package CrossLinuxi386.rar). Compilation runs fine but I get this error for every project (even for the fresh empty app).

Everywhere else I could only find error messages stating that some library is missing for the linker, but no such report in my case, just "Error while linking".

Thank you

[Jonas Maebe]

You should really ask that on the newpascal forum instead: http://synopse.info/forum/viewforum.php?id=21 (linked from the top of newpascal.org)

We have no control over what changes they have done to FPC, or how they package it.

[DonAlfredo]

Jonas is right ... I will answer your question in that forum !

[Thaddy]

Indeed, at this moment the newpascal fork should be adrressed by the ones that created it.
It is at the moment also highly unstable and lacks essential platforms.

That said: I Hope they un-fork it.... I've seen real efforts to do so.
It's a good effort.

But unusable for production.

And not supported here, because it is a fork.
[edit]
Tnx Alfred!!

[tk]

Ah sorry, did not see that link. Newpascal questions = newpascal forum . Will ask there in few moments. Thanks.

EDIT: http://synopse.info/forum/viewtopic.php?pid=22241#p22241

[hnb]

We have no control over what changes they have done to FPC, or how they package it.

Process is transparent and documented ( http://newpascal.org/compass.html ). Each release has full test suite to check regressions. Building process:

step 1: https://github.com/newpascal/freepascal/blob/release/appveyor.yml
step 2: https://github.com/newpascal/lazarus/blob/release/appveyor.yml
step 3: https://github.com/newpascal/newpascal/blob/master/appveyor.yml

soon will be more expanded and integrated with fpcupdeluxe.

It is at the moment also highly unstable and lacks essential platforms.

That said: I Hope they un-fork it.... I've seen real efforts to do so.
It's a good effort.

But unusable for production.

I can't agree with few points. I use NewPascal for production from beginning (Win server + Android ARM6/7 clients for business application). From my experience is more stable than 2.6.x/3.0.x series and works better than trunk for mORMot. Anyway at current form you can easily start development only on Windows (but that will change soon ).

Un-forking is outside my powers. I do what I can best to "merge back" patches and new features to FPC trunk.

[tk]

It is at the moment also highly unstable and lacks essential platforms.
..
But unusable for production.

It is true that I started with this fork few weeks ago so I don't have yet enough experience.
But today I would not say that it is unstable.
It definitely has better stability than my old Delphi XE

And actually Newpascal does exactly what I want now.
Just download, unpack and cross compile. How simple!

Anyway, this bug has been solved, see the link I entered above to the Newpascal forum.

[Thaddy]

I am not bashing. I await some of the features in newpascal with great anticipation.
I just wrote my opinion as a professional. Of course I am testing newpascal at least on a weekly basis.
The devs know that.

It is just not finished and needs loads of polishing as with any new metal.

But < grumpy mode on  > I hate forks when they are not needed.
Seems to me the conservative release and patch management of FPC is a good thing.

[Xor-el]

Seems to me the conservative release and patch management of FPC is a good thing.

that is the problem.
new awesome features added to FPC are only available in trunk.
an example : generic methods.
I am tired of waiting for a very long period of time to have access to these features.
bleeding edge forks like NewPascal helps me use this features without the burden of having to build from sources.

[Thaddy]

an example : generic methods.

That's a bad example. Freepascal had generics LONG BEFORE Delphi. Didn't you know that? <grumpy mode maximum  >

The problem is that a commercial company will never show what's really in the lab, not even for beta testers.
And that fpc trunk is fully available to everyone that knows how to work with it.
People who can use trunk can also apply proposed patches.
Even if they are not fully scrutinized and accepted.
 
What you propose is just silly. You are fired. <trump mode off> 

I can understand that when you see there is something in the lab you want it right now, but believe me patience is an art and very desirable. <hillary mode also off>

[Xor-el]

an example : generic methods.

That's a bad example. Freepascal had generics LONG BEFORE Delphi. Didn't you know that? <grumpy mode maximum  >

I meant generic methods not classes.
at least in the stable FPC 3.0 I use, generic methods does not compile.

see this
http://lists.freepascal.org/pipermail/fpc-pascal/2015-February/043593.html

http://lists.freepascal.org/fpc-pascal/2015-November/045746.html

[shobits1]

...
< grumpy mode on  >
...

...
<grumpy mode maximum  >
...
<trump mode off> 
...
<hillary mode also off>

,, so funny.