Re: [MSEide-MSEgui-talk] Multi-arch problem...

Hello. Here result of my summer Linux distros tour. I did follow the excellent advices of Sternas from the CodeTyphon project: http://www.pilotlogic.com/sitejoom/index.php/wiki/135-wiki/codetyphon-host-oses What I want: - Multi-Arch OS (possibility to run 32 bit apps on a 64 bit OS). -

Re: [MSEide-MSEgui-talk] Multi-arch problem...

Hello Sieghard. Thanks for answer. OK, all is fixed now, compies + link + run 32 bit applications on a 64 bit multi-arch system. This patch for the fpc compiler did the trick (this for fpc 3.1.1): fpc_checkelf2.gz In

Re: [MSEide-MSEgui-talk] Multi-arch problem...

Sehr geehrter Herr fredvs, (sorry for the delay - I was mostly disconnected some time...) Sie schrieben am Wed, 25 Jul 2018 14:58:25 -0500 (CDT): > Huh, yes, using 32 bit apps on multi-arch 64 bit system can be ***very*** > painful. Well... Merely _using_ them shouldn't be any different from

Re: [MSEide-MSEgui-talk] Multi-arch problem...

Ha, the mails work again. ;) For all the passionates about ELF multi-arch, here how to check if a file is a ELF and what kind. From Wikipedia, ELF format: ... Read the first four bytes. If they are equal to \x7fELF, it's an ELF file. The ELF magic number is 0x7f454C46 (0x7f + "ELF") The

Re: [MSEide-MSEgui-talk] Multi-arch problem...

Hello. > Sorry, I didn't notice that you use Manjaro, Huh, after some bad experience with my ex-favorite Linux OS, I just have switched to a not-Debian OS: Arch-Manjaro. > I thought it's about PolyDev. With polYdev it is a other problem: FreeBSD multi-arch design is not compatible with their

Re: [MSEide-MSEgui-talk] Multi-arch problem...

Hello everybody. > Sorry, I didn't notice that you use Manjaro Huh, after some bad experience with my ex-favorite Linux OS, I just migrate to a not-Debian OS : Arch-Manjaro. >, I thought it's about PolyDev. No with polYdev multi-arch Linux-emulated works like charm (the problem is only with

Re: [MSEide-MSEgui-talk] Multi-arch problem...

Hello. > Sorry, I didn't notice that you use Manjaro, Huh, after some bad experience with my ex-favorite Linux OS, I just have switched to a not-Debion OS: Arch-Manjaro. > I thought it's about PolyDev. With polYdev it is a other problem: FreeBSD multi-arch design is not compatible with their

Re: [MSEide-MSEgui-talk] Multi-arch problem...

d. Fre;D De : Martin Schreiber Envoyé : jeudi 26 juillet 2018 18:47 À : mseide-msegui-talk@lists.sourceforge.net Objet : Re: [MSEide-MSEgui-talk] Multi-arch problem... On 07/26/2018 03:13 PM, Martin Schreiber wrote: > On Thursday 26 July 2018 15:01:25 fredvs

Re: [MSEide-MSEgui-talk] Multi-arch problem...

On Thursday 26 July 2018 18:47:21 Martin Schreiber wrote: > On 07/26/2018 03:13 PM, Martin Schreiber wrote: > > On Thursday 26 July 2018 15:01:25 fredvs wrote: > >> Re-hello. > >> > >>> Maybe librarysearchpath has an entry for /lib where on your system a 64 > >>> bit crtn.o is located? > >> > >>

Re: [MSEide-MSEgui-talk] Multi-arch problem...

On 07/26/2018 03:13 PM, Martin Schreiber wrote: > On Thursday 26 July 2018 15:01:25 fredvs wrote: >> Re-hello. >> >>> Maybe librarysearchpath has an entry for /lib where on your system a 64 >>> bit crtn.o is located? >> >> Re-about this, even if librarysearchpath has an entry for /lib (that I did

Re: [MSEide-MSEgui-talk] Multi-arch problem...

On Thursday 26 July 2018 15:01:25 fredvs wrote: > Re-hello. > > > Maybe librarysearchpath has an entry for /lib where on your system a 64 > > bit crtn.o is located? > > Re-about this, even if librarysearchpath has an entry for /lib (that I did > not found), compiler/systems/t_bsd.pas:124: "

Re: [MSEide-MSEgui-talk] Multi-arch problem...

Re-hello. > Maybe librarysearchpath has an entry for /lib where on your system a 64 > bit crtn.o is located? Re-about this, even if librarysearchpath has an entry for /lib (that I did not found), normally, like for all other libraries, it seems to me that there is a check if the file has the

Re: [MSEide-MSEgui-talk] Multi-arch problem...

> Maybe librarysearchpath has an entry for /lib where on your system a 64 bit crtn.o is located? It is exactly wath I was thinking but... I did not found this in FPC code. Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/

Re: [MSEide-MSEgui-talk] Multi-arch problem...

On Thursday 26 July 2018 14:11:11 fredvs wrote: > Hello Martin. > > > Because in linker script are absolute paths, see my mail from 2018-07-23: > > Huh, OK, I did read it but the code for the linker script is in > t_linux.pas line 508 (see my post of Jul 24, 2018; 2:41pm) > >

Re: [MSEide-MSEgui-talk] Multi-arch problem...

Hello Martin. > Because in linker script are absolute paths, see my mail from 2018-07-23: Huh, OK, I did read it but the code for the linker script is in t_linux.pas line 508 (see my post of Jul 24, 2018; 2:41pm) StartSection('INPUT('); if linklibc and (libctype<>uclibc) then begin

Re: [MSEide-MSEgui-talk] Multi-arch problem...

On Wednesday 25 July 2018 21:58:25 fredvs wrote: > > About the ctri.o and ctrn.o problems, the -Xd parameter fixes the linking > (but I did not find why the 64 bit object-files are assigned in place of 32 > bit). > Because in linker script are absolute paths, see my mail from 2018-07-23: " > >

Re: [MSEide-MSEgui-talk] Multi-arch problem...

Hello Sieghard. Thanks for your time. Huh, yes, using 32 bit apps on multi-arch 64 bit system can be ***very*** painful. At the moment I can successfully run fpc32 (on a 64 bit os) and compile 32 bit applications. Yesterday, I was even able to run those 32 applications on the multi-arch os !

Re: [MSEide-MSEgui-talk] Multi-arch problem...

Hello fredvs, Sie schrieben am Tue, 24 Jul 2018 07:41:42 -0500 (CDT): > Hello Seighard. ^^ie (Doesn't your editor extract this from the cited posting?) > > - considering, that these two _object_ files seem to be multi > > architacture in systems with multi architecture support. > >

Re: [MSEide-MSEgui-talk] Multi-arch problem...

Hello Seighard. > - considering, that these two _object_ files seem to be multi architacture > in systems with multi architecture support. Not sure to understand. Do you mean that it exist object_ files that have both ELF32+64 signatures ? And then only one file could be used in a multi-arch

Re: [MSEide-MSEgui-talk] Multi-arch problem...

Hello fredvs, Sie schrieben am Sun, 22 Jul 2018 16:06:13 -0500 (CDT): > It is not normal that all other needed libraries are using the correct 32 > bit path (/usr/lib32) and not crti.o and crtn.o It seems normal - > Normally, like for all other libraries, the system try to find in each >

Re: [MSEide-MSEgui-talk] Multi-arch problem...

On Sunday 22 July 2018 23:06:13 fredvs wrote: > Re-hello. > > Here a advice that has absolutely no importance. > > OK, -Xd does the trick because it does not give /lib nor /usr/lib as searh > path. > > But I maintain that there is still a problem with crti.o and crtn.o > > It is not normal that

Re: [MSEide-MSEgui-talk] Multi-arch problem...

Re-hello. Here a advice that has absolutely no importance. OK, -Xd does the trick because it does not give /lib nor /usr/lib as searh path. But I maintain that there is still a problem with crti.o and crtn.o It is not normal that all other needed libraries are using the correct 32 bit path

Re: [MSEide-MSEgui-talk] Multi-arch problem...

> -Xd (do not use the standard library path) link.res without Xd parameter: (and of course with correct -e and Fl) (that is what I did) -> SEARCH_DIR("/lib/") SEARCH_DIR("/usr/lib/") SEARCH_DIR("/usr/lib32/") SEARCH_DIR("/usr/lib/gcc/x86_64-pc-linux-gnu/8.1.1/32/") ... INPUT(

Re: [MSEide-MSEgui-talk] Multi-arch problem...

> Please ensure that you use the mseform.pas file from current git master > branch everywhere and ensure that the used mseform.ppu will be recompiled. Of course I did use the last msegui from Gitlab and deleted all the .ppu and .o before compile. Anyway now it is fixed (and I do not know how to

Re: [MSEide-MSEgui-talk] Multi-arch problem...

On Friday 20 July 2018 15:22:50 fredvs wrote: > > tcustommseform.windowopacity has been introduced recently. I assume you > > try > > to > > > load a form produced by current MSEide with an old MSEgui mseforms unit. > > Yes, it must be the problem. > The mseforms unit was created with a OS that

Re: [MSEide-MSEgui-talk] Multi-arch problem...

> tcustommseform.windowopacity has been introduced recently. I assume you try to > load a form produced by current MSEide with an old MSEgui mseforms unit. Yes, it must be the problem. The mseforms unit was created with a OS that use windowopacity. And it seems that Manjaro xfce does not use

Re: [MSEide-MSEgui-talk] Multi-arch problem...

On Friday 20 July 2018 01:34:24 fredvs wrote: > Aaargh. > > It seems to be a Manjaro+MSE problem. > > Compiling a 64 bit app is ok but running it: > > An unhandled exception occurred at $0060B7BA : > EReadError : Error reading configfo.windowopacity: Unknown property: > "windowopacity" >

Re: [MSEide-MSEgui-talk] Multi-arch problem...

Re-hello. OK, I get a work-around. in /msegui/lib/common/fpccompatibility/mclasses.pas At line 6573 + 6574, comment this: // raise EReadError.CreateFmt(SPropertyException, // [Name, DotSep, Path, e.Message]); Without those lines, the app 64 bit run OK (no crash). But for the app 32

Re: [MSEide-MSEgui-talk] Multi-arch problem...

Aaargh. It seems to be a Manjaro+MSE problem. Compiling a 64 bit app is ok but running it: An unhandled exception occurred at $0060B7BA : EReadError : Error reading configfo.windowopacity: Unknown property: "windowopacity" $0060B7BA line 6571 of

[MSEide-MSEgui-talk] Multi-arch problem...

Hello Martin. I try to make my new Linux (Manjaro xfce) 64 bit multi arch work. OK, compiling 32 bit MSE application with fpc32 is OK on the 64 bit OS. But, while running (with gdb) the 32 bit app on the 64 bit system, there is that error + crash: (gdb) run Starting program: