On 26 Mar 2014, at 23:15, fredvs wrote:
>
> Also, delete all the *.ppu and *.o of previous compile.
FWIW: Removing all of them when you get weird errors always does the trick
here. You can probably count yourself lucky as I once had a project with an
outdated .o file that *did* link. Took me a
> No problem... what's your fpc version? I'll compare with the right version
of FPC here.
Hum, now it compiles the library using same fpc.cfg with fpc 2.6.2. and
2.7.1 perfectly (the size of library is > with fpc 2.7.1).
It seems to me that the trick was to add lot of -Fu and -Fi search-paths for
No problem... what's your fpc version? I'll compare with the right version
of FPC here.
2014-03-26 14:17 GMT-03:00 fredvs :
> @ Fabio Luis Girardi :
>
> Here my working *fpc.cfg*
> _
> #
> # Config file generated by fpcmkcfg on 5-3-14 - 21:
@ Fabio Luis Girardi :
Here my working *fpc.cfg*
_
#
# Config file generated by fpcmkcfg on 5-3-14 - 21:58:27
# Example fpc.cfg for Free Pascal Compiler
#
# --
# Defines (preprocessor)
# --
#
# nested
>> You recompiled the FPC? Or simple change of fpc.cfg options solves your
problem?
Oops, sorry for the delay.
I only change fpc.cfg options and it solves the problem...
Hum, im really sorry but i do not know what changes do the trick. (i did not
save the old fpc.cfg-not-working, so, i cannot c
You recompiled the FPC? Or simple change of fpc.cfg options solves your
problem?
2014-03-22 21:55 GMT-03:00 Fred van Stappen :
>
> >> Works fine for me if I compile everything with those parameters
> >> (and -trunk) I assume you compiled with the build.sh and then
> >> didn't clean up properly w
>> Works fine for me if I compile
everything with those parameters
>> (and -trunk) I assume you compiled with
the build.sh and then
>> didn't clean up properly when you started adding
parameters,
>> thus leaving units compiled without the pic params.
Hello.
I have re-created a new fpc.cfg a
Yep, many thanks for the attention you give :
=> http://bugs.freepascal.org/view.php?id=25901
Hum, Marco explained :
>> Works fine for me if I compile
everything with those parameters
>> (and -trunk) I assume you compiled with
the build.sh and then
>> didn't clean up properly when you started
>> Indeed, not all bug reports are followed up within two days...
Yep, i feel better now ;-)
Thanks Jonas.
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.fre
On 20/03/14 12:59, Fred van Stappen wrote:
> It's quite possible that there is nevertheless a bug, but you will
have to
> provide the source code required to reproduce it and compilation
> instructions, otherwise there is nothing we can do (as always).
Hum, not too much answer here... ;-(
Inde
> It's quite possible that there is nevertheless a bug, but you will have to
> provide the source code required to reproduce it and compilation
> instructions, otherwise there is nothing we can do (as always).
Hum, not too much answer here... ;-(
Re-resumed :
Units/Project => https://github.com/g
> but you will have to provide the source code required to reproduce
> it and compilation instructions, otherwise there is nothing we can do (as
> always).> Jonas
Hum, ok (but you promise not to tell, it is still a secret...) ;-)
The project-units :
>> https://github.com/graemeg/fpGUI/tree/deve
On 18 Mar 2014, at 12:52, Fred van Stappen wrote:
/usr/bin/ld: /home/fred/mylib/lib/x86_64-linux/thefile.o:
réadressage de
R_X86_64_32S en vertu de « .bss.n_u_$thefile_$$_usedfirstmessage »
cannot
be used when creation of shared object, recompile with -fPIC/
home>> >/fred/fmylib/lib/x86_
> /usr/bin/ld: /home/fred/mylib/lib/x86_64-linux/thefile.o: réadressage de
> R_X86_64_32S en vertu de « .bss.n_u_$thefile_$$_usedfirstmessage » cannot
> be used when creation of shared object, recompile with -fPIC/home>>
> >/fred/fmylib/lib/x86_64-linux/thefile.o: error adding symbols: Bad value
Hello.
Here are some news from the front :
The fpc Library :
TheRevolutionaryLibrary library;
uses
TheBigUnit;
begin
end.
fpc compiler parameter => -fPIC.
=> Windows 32 bit => Compiles and works more than perfect.
=> Windows 64 bit => Compiles and works more than perfect.
=> Linux 32 bit => C
Same problem here when I try to compile a form on a library... I know that
Forms on lib don't work yet because of other problems, not because linking
problems.
I'm using Lazarus 1.3 and FPC 2.7.1 x64.
2014-03-11 11:15 GMT-03:00 Fred van Stappen :
> Hello.
>
> After successfully translate a usefu
Hello.
After successfully translate a useful unit into a universal library, i want to
do the same with something bigger.
I have compile that unit into a Windows library.
Perfect, it compile and works.
But when i try to compile it on Linux a get that error message, even if i
compile it with -f
17 matches
Mail list logo
