Re: [fltk.development] [fltk.general] :Linking Fluid Error
Dear Ianya i do agree, libraries n all compiled properly, no error but only linker warnings are getting...but still my application codes are not compiling, same linking errors are coming..dats the reason m bit worried.could you suggest any cross compile toolchain with X11 support?? because toolchain what m using in that no X11 related libraries n include files. In the skiff toolchain X11 libraries n include files are there, but after including those in cross compile environment EABI version matching errors are coming.thats true beacuse u know target fluid built with EABI version 4, but X11 built with a EABI version 0. So finaly i have concluded that entire problem with my toolchain only. because of some version problem i coul not able to use skiff toolchain..so can u suggest any other prebuilt toolchain so that i can download n proceed for further process. otherwise i vl have to concentrate on cross compilation of X11 for arm target..RegdsVinayakQuoting quot;MacArthur, Ian (SELEX GALILEO, UK)quot; lt;[EMAIL PROTECTED]gt;:gt; Is this proparly compiled or not??? i hope its not butgt; still m asking you..please reply me.Are the warnings listed (below) the only warnings you get? And there areno outright errors?If so, I'd hazard that the build of the library and the test demoprograms has succeeded.Do you think it has not worked? It seems, from the way you phrased yourquestion, that you believe this has not worked correctly - if so, whatmakes you think it has not worked?Is there some specific problem you are seeing when you try and executethe code on your target board?gt; Linking fluid...gt; /usr/bin/ld: skipping incompatible gt; /home/vinayak/arm-2007q1/arm-none-linux-gnueabi/lib/X11//libXext.sogt; when searching for -lXextgt; /usr/bin/ld: skipping incompatible gt;/home/vinayak/arm-2007q1/arm-none-linux-gnueabi/lib/X11//libX11.sogt; when searching for -lX11gt; === making test ===gt; Compiling unittests.cxx...gt; Lin king unittests...gt; /usr/bin/ld: skipping incompatible/home/vinayak/arm-2007q1/arm-none-linux-These warnings would imply that when the linker is looking for librarieswith the names libXext.* and libX11.*, it is finding some that it cannot link because they are the wrong architecture - I'm guessing it islooking for ARM based libs and is finding some x86 based libs? Youreally need to fix that.Is the linker subsequently finding that quot;correctquot; versions for Xext andX11? I assume it must be as you have not shown any other linker errors.You are sure that you are using the correct (i.e. the ARM compatible)linker? Just checking...!-- IanSELEX Sensors and Airborne Systems LimitedRegistered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3ELA company registered in England amp; Wales. Company no. 02426132This email and any attachments are confidential to the intendedrecipient and may als o be privileged. If you are not the intendedrecipient please delete it from your system and notify the sender.You should not copy it or use it for any purpose nor disclose ordistribute its contents to any other person. ___ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
Re: [fltk.development] [fltk.general] :Linking Fluid Error
Dear Ian,Is this proparly compiled or not??? i hope its not but still m asking you..please reply me. Linking fluid.../usr/bin/ld: skipping incompatible /home/vinayak/arm-2007q1/arm-none-linux-gnueabi/lib/X11//libXext.so when searching for -lXext/usr/bin/ld: skipping incompatible /home/vinayak/arm-2007q1/arm-none-linux-gnueabi/lib/X11//libX11.so when searching for -lX11=== making test ===Compiling unittests.cxx...Linking unittests.../usr/bin/ld: skipping incompatible /home/vinayak/arm-2007q1/arm-none-linux-gnueabi/lib/X11//libXext.so when searching for -lXext/usr/bin/ld: skipping incompatible /home/vinayak/arm-2007q1/arm-none-linux-gnueabi/lib/X11//libX11.so when searching for -lX11---=== installing FL ===Installing include files in /home/vinayak/arm-2007q1/arm-none-linux-gnueabi//include...=== installing src ===Installing libraries in /home/vinayak/arm-2007q1/arm-none-linux-gnueabi//lib... === installing fluid ===Installing FLUID in /home/vinayak/arm-2007q1/arm-none-linux-gnueabi//bin...=== installing test ===Installing example programs to /home/vinayak/arm-2007q1/arm-none-linux-gnueabi//share/doc/fltk/examples...=== installing documentation ===Installing documentation files in /home/vinayak/arm-2007q1/arm-none-linux-gnueabi//share/doc/fltk...Installing man pages in /home/vinayak/arm-2007q1/arm-none-linux-gnueabi//share/man...Quoting quot;MacArthur, Ian (SELEX GALILEO, UK)quot; lt;[EMAIL PROTECTED]gt;:gt; before that i need to say one thing. gt; earlier while compiling got a an error which some thing like this:- Fl_x.cxx:239: error: impossible constraint in 'asm' Fl_x.cxx:240: error: impossible constraint in 'asm' Fl_x.cxx:241: error: impossible constraint in 'asm'If those line numbers are correct, then those errors suggest that youhave the wrong header files for the unix quot;selectquot; functions or similar -not specifically related to the X-windowing system, but still a showstopper.You need to ensure that *only* the target toolchain header files areincluded in the build, and that no local-system header files getincluded, as they *will* be different and often incompatible.gt; what i have done is copied X11 from /usr/lib/X11/ togt; my toolchain /lib.gt; is that correct method No.All the libs that you link the target applications against *must* belibs built for the target architecture.So you must not use *any* of your host libs on your target, you mustobtain (or build for yourself) the correct libs for the target.If you think about it, the libs contain code that will be linked intoyour app then run on your target - so the host libs contain x86 code andthe target libs need to contain ARM code... Not the same thing at all!gt; if not tell me from scracth will try to rebuild fltk. You need to tell us what display system your target board has - is itX-windows or is it a framebuffer device?Assuming it is X -windows, you need to obtain the correct X11 librariesand header files to allow you to build X-windows applications for yourtarget board. I assume that these will be available from the toolchainor board supplier.If you are building the boards yourself, then you may need to build theX11 libraries yourself - in which case you need to get the sources fromXorg, then cross-compile them for your target hardware. The Xorgconfigure system is complex, but does support cross-compilation fairlywell, and there are many articles on the web about doing this. It isoutside the scope of a fltk list to discuss it though. (Suffice to sayit is a straightforward but long and arduous process!)Anyway - once you have the necessary X libs and headers for your target,fltk should build against them without these troubles.SELEX Sensors and Airborne Systems LimitedRegistered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3ELA company registered in England amp; Wales. Company no. 02 426132This email and any attachments are confidential to the intendedrecipient and may also be privileged. If you are not the intendedrecipient please delete it from your system and notify the sender.You should not copy it or use it for any purpose nor disclose ordistribute its contents to any other person. ___ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
Re: [fltk.development] [fltk.general] :Linking Fluid Error
before that i need to say one thing. earlier while compiling got a an error which some thing like this:- Fl_x.cxx:239: error: impossible constraint in 'asm' Fl_x.cxx:240: error: impossible constraint in 'asm' Fl_x.cxx:241: error: impossible constraint in 'asm' If those line numbers are correct, then those errors suggest that you have the wrong header files for the unix select functions or similar - not specifically related to the X-windowing system, but still a show stopper. You need to ensure that *only* the target toolchain header files are included in the build, and that no local-system header files get included, as they *will* be different and often incompatible. what i have done is copied X11 from /usr/lib/X11/ to my toolchain /lib. is that correct method No. All the libs that you link the target applications against *must* be libs built for the target architecture. So you must not use *any* of your host libs on your target, you must obtain (or build for yourself) the correct libs for the target. If you think about it, the libs contain code that will be linked into your app then run on your target - so the host libs contain x86 code and the target libs need to contain ARM code... Not the same thing at all! if not tell me from scracth will try to rebuild fltk. You need to tell us what display system your target board has - is it X-windows or is it a framebuffer device? Assuming it is X-windows, you need to obtain the correct X11 libraries and header files to allow you to build X-windows applications for your target board. I assume that these will be available from the toolchain or board supplier. If you are building the boards yourself, then you may need to build the X11 libraries yourself - in which case you need to get the sources from Xorg, then cross-compile them for your target hardware. The Xorg configure system is complex, but does support cross-compilation fairly well, and there are many articles on the web about doing this. It is outside the scope of a fltk list to discuss it though. (Suffice to say it is a straightforward but long and arduous process!) Anyway - once you have the necessary X libs and headers for your target, fltk should build against them without these troubles. SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England Wales. Company no. 02426132 This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ___ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
Re: [fltk.development] [fltk.general] :Linking Fluid Error
Hi Ian,Greetingshave added --disable-xdbe in configure option and ran the script but still getting same problem.but m very much confused to change references in makeinclude. here m pasting a small chunk which is part of makeinclude file. please specify where i have to make changes..# libraries to link with:AUDIOLIBS =DSOFLAGS = -L. -L/home/vinayak/arm-2007q1/libLDFLAGS = $(OPTIM) -L/home/vinayak/arm-2007q1/libLDLIBS = -ldl -lm -lXext -lX11GLDLIBS = -ldl -lm -lXext -lX11LINKFLTK = ../lib/libfltk.aLINKFLTKGL =LINKFLTKFORMS = ../lib/libfltk_forms.a ../lib/libfltk.aLINKFLTKIMG = ../lib/libfltk_images.a ../lib/libfltk.a $(IMAGELIBS)LINKSHARED = ../lib/libfltk_images.a ../lib/libfltk_forms.a ../lib/libfltk.a $(IMAGELIBS)IMAGELIBS = -L../lib -lfltk_png -lfltk_z -lfltk_jpegThanksQuoting quot;MacArthur, Ian (SELEX GALILEO, UK)quot; lt;[EMAIL PROTECTED]gt;:gt; as per your suggestion, there i s no file like libXext.andgt; libXext.so in cross compile environment, but it is theregt; in host environment in /usr/lib.gt; my question is how to obtain libXext.so???If it is not there, it is probable that the X-server for your targetplatform does not provide those functions.Therefore your only option is to configure without xdbe support (use the--disable-xdbe option to configure) then remove any references tolibXext from the makeinclude file. After that, fltk should probably linkOK without Xext and you should be able to proceed.gt; and where to copy this particular file in cross platform environment.If it isn't provided with your environment, I expect that you will haveto work without it. You can not just copy in another version fromquot;somewhere elsequot;, that will not work. Building fltk without xdbe supportshould be enough to allow you to work without libXext installed,usually.SELEX Sensors and Airborne Systems LimitedRegistered Office: Sigma House, Christophe r Martin Road, Basildon, Essex SS14 3ELA company registered in England amp; Wales. Company no. 02426132This email and any attachments are confidential to the intendedrecipient and may also be privileged. If you are not the intendedrecipient please delete it from your system and notify the sender.You should not copy it or use it for any purpose nor disclose ordistribute its contents to any other person. ___ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
Re: [fltk.development] [fltk.general] :Linking Fluid Error
have added --disable-xdbe in configure option and ran the script Good. # libraries to link with: AUDIOLIBS = DSOFLAGS= -L. -L/home/vinayak/arm-2007q1/lib LDFLAGS = $(OPTIM) -L/home/vinayak/arm-2007q1/lib These lines look reasonable, but I would advise against trying shared linking, at least until after the basics are working, so hopefully you won't be using the DSOFLAGS options yet. LDLIBS = -ldl -lm -lXext -lX11 GLDLIBS = -ldl -lm -lXext -lX11 Both these lines need edited to remove the -lXext options. Is you X11 library in the /home/vinayak/arm-2007q1/lib folder? If not you might need a path to find that. LINKFLTK= ../lib/libfltk.a LINKFLTKGL = LINKFLTKFORMS = ../lib/libfltk_forms.a ../lib/libfltk.a LINKFLTKIMG = ../lib/libfltk_images.a ../lib/libfltk.a $(IMAGELIBS) LINKSHARED = ../lib/libfltk_images.a ../lib/libfltk_forms.a ../lib/libfltk.a $(IMAGELIBS) IMAGELIBS = -L../lib -lfltk_png -lfltk_z -lfltk_jpeg Probably these others are OK. SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England Wales. Company no. 02426132 This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ___ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
Re: [fltk.development] [fltk.general] :Linking Fluid Error
Dear Ian,good evening...and milliion thanks...As per your direction have removed the lXext this time i got quot;cannot find -lX11quot;.Even if i removed the both lXet as well as -lX11 from makeinclude, different errors are coming. at this moment m out of office tomorrow morning will post you the eroor snaps.Regds,VinayakQuoting quot;MacArthur, Ian (SELEX GALILEO, UK)quot; lt;[EMAIL PROTECTED]gt;:gt; have added --disable-xdbe in configure option and ran the scriptGood. # libraries to link with: AUDIOLIBS = DSOFLAGS= -L. -L/home/vinayak/arm-2007q1/lib LDFLAGS = $(OPTIM) -L/home/vinayak/arm-2007q1/libThese lines look reasonable, but I would advise against trying sharedlinking, at least until after the basics are working, so hopefully youwon't be using the DSOFLAGS options yet. LDLIBS = -ldl -lm -lXext -lX11GLDLIBS = -ldl -lm -lXext -lX11Both these lines need edited to remove the -lXext options.Is you X11 libra ry in the /home/vinayak/arm-2007q1/lib folder? If notyou might need a path to find that. LINKFLTK= ../lib/libfltk.a LINKFLTKGL = LINKFLTKFORMS = ../lib/libfltk_forms.a ../lib/libfltk.a LINKFLTKIMG = ../lib/libfltk_images.a ../lib/libfltk.a$(IMAGELIBS) LINKSHARED = ../lib/libfltk_images.a../lib/libfltk_forms.a ../lib/libfltk.a $(IMAGELIBS) IMAGELIBS = -L../lib -lfltk_png -lfltk_z -lfltk_jpegProbably these others are OK.SELEX Sensors and Airborne Systems LimitedRegistered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3ELA company registered in England amp; Wales. Company no. 02426132This email and any attachments are confidential to the intendedrecipient and may also be privileged. If you are not the intendedrecipient please delete it from your system and notify the sender.You should not copy it or use it for any purpose nor disclose ordistribute its content s to any other person. ___ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
Re: [fltk.development] [fltk.general] :Linking Fluid Error
As per your direction have removed the lXext this time i got cannot find -lX11. OK. Do you have the X-windows client libraries for your cross-target, and their associated dev packages, installed? Even if i removed the both lXet as well as -lX11 from makeinclude, different errors are coming. You can not build fltk without some windowing system. Under Linux, the usual windowing system is X-windows. So if your target uses X-windows as it's display system then you need, at the very least, to link against X11 (libX11.so probably, or libX11.a possibly.) Now - it is possible that your target hardware doesn't have an X-windows system at all, and only provides a framebuffer device for display. If so, getting fltk to run on this device is not going to be trivial. There are rumoured to be patches around to get fltk to build with a framebuffer display device, but I have never used them, and know nothing about them. Another possibility is that your target hardware has a minimal lightweight X-window system, such as nano-X or KDrive. Both of these provide an API that is essentially similar to a real X-windows system, but you may need to do some work to tweak the names of the included files and libraries and so forth to get fltk to build. There used to be a specific port of fltk for nano-X, but I don't know how current or well maintained it is. KDrive should be pretty much a drop-in replacement for a real X-server so probably will just work, if you link against the correct libraries at build time. However, in either case, a real X-server is a better bet! It is most likely that you simply haven't got the dev libraries for your X-windows system in your toolchain, and adding them will make things work. What display system does your target board have? SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England Wales. Company no. 02426132 This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ___ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
Re: [fltk.development] [fltk.general] :Linking Fluid Error
Hi,ya your absolutely correct. before that i need to say one thing. earlier while compiling got a an error which some thing like this:-Fl_x.cxx:239: error: impossible constraint in 'asm'Fl_x.cxx:240: error: impossible constraint in 'asm'Fl_x.cxx:241: error: impossible constraint in 'asm'but i did not inform you, but got it rectified myself. what i have done is copied X11 from /usr/lib/X11/ to my toolchain /lib. is that correct method if not tell me from scracth will try to rebuild fltk. have decided to choose fltk for my product development. I felt fltk is a nice tool kit.This is a very interesting and tricky situation as I am coming across a lot or errors while compiling.But I have decided firmly that I will not quit till I achieve my success .And for this task I need your helping hand.I will remain great full to you through out my life for the knowledge you have enlightened me with. Regds,VinayakQuoting quot;MacArthur, Ian (SELEX GALILEO, UK)quot; lt;[EMAIL PROTECTED] elexgalileo.comgt;:gt; As per your direction have removed the lXextgt; this time i got quot;cannot find -lX11quot;.OK. Do you have the X-windows client libraries for your cross-target,and their associated dev packages, installed?gt; Even if i removed the both lXet as well as gt; -lX11 from makeinclude, different errors are coming.You can not build fltk without some windowing system.Under Linux, the usual windowing system is X-windows. So if your targetuses X-windows as it's display system then you need, at the very least,to link against X11 (libX11.so probably, or libX11.a possibly.)Now - it is possible that your target hardware doesn't have an X-windowssystem at all, and only provides a framebuffer device for display. Ifso, getting fltk to run on this device is not going to be trivial. There are rumoured to be patches around to get fltk to build with aframebuffer display device, but I have never used them, and know nothingabout them.Another possibility is that you r target hardware has a minimallightweight X-window system, such as nano-X or KDrive. Both of theseprovide an API that is essentially similar to a quot;realquot; X-windows system,but you may need to do some work to tweak the names of the includedfiles and libraries and so forth to get fltk to build. There used to bea specific port of fltk for nano-X, but I don't know how current or wellmaintained it is. KDrive should be pretty much a drop-in replacement fora real X-server so probably will just work, if you link against thecorrect libraries at build time.However, in either case, a quot;realquot; X-server is a better bet!It is most likely that you simply haven't got the dev libraries for yourX-windows system in your toolchain, and adding them will make thingswork.What display system does your target board have?SELEX Sensors and Airborne Systems LimitedRegistered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3ELA company registered in England amp; Wale s. Company no. 02426132This email and any attachments are confidential to the intendedrecipient and may also be privileged. If you are not the intendedrecipient please delete it from your system and notify the sender.You should not copy it or use it for any purpose nor disclose ordistribute its contents to any other person. ___ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
Re: [fltk.development] [fltk.general] :Linking Fluid Error
Hi,Thanks for your response, but still m having small doubts i hope u will clear that..as per your suggestion, there is no file like libXext.and libXext.so in cross compile environment, but it is there in host environment in /usr/lib.my question is how to obtain libXext.so??? and where to copy this particular file in cross platform environment. please specify commands.Regds,Vinayak gt; Thanks for your support, m here trying to cross compile fltk gt; 1.1.9 for arm target board, finally m getting error is shown belowgt; gt; /home/vinayak/arm-2007q1/bin/../lib/gcc/arm-none-linux-gnueabi/4.2.0/../../../../arm-none-linux-gnueabi/bin/ld: cannot find -lXextgt; collect2: ld returned 1 exit statusgt; make[1]: *** [fluid] Error 1gt; make: *** [all] Error 1- You need to link against the cross-compiler target versions oflibXext.a or libXext.so to resolve this error (as suggested yesterday.)I suggest that this is as simple as adding the correct paths to yourlinker command line t o find this lib.- If you do not have libXext.* in your cross-compiler environment, thenyou will need to obtain it, as fltk/X11 will probably not work withoutit.- You need to post to fltk.general; this list [fltk.dev] is fordevelopment of the fltk library, not for development hat uses the fltklibrary.SELEX Sensors and Airborne Systems LimitedRegistered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3ELA company registered in England amp; Wales. Company no. 02426132This email and any attachments are confidential to the intendedrecipient and may also be privileged. If you are not the intendedrecipient please delete it from your system and notify the sender.You should not copy it or use it for any purpose nor disclose ordistribute its contents to any other person.--___ fltk-dev mailing [EMAIL PROTECTED]://lists.easysw.com/mailman/listinfo/fltk-devEnd of fltk-dev Digest, Vol 56, Issue 50 ___ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
Re: [fltk.development] [fltk.general] :Linking Fluid Error
as per your suggestion, there is no file like libXext.and libXext.so in cross compile environment, but it is there in host environment in /usr/lib. my question is how to obtain libXext.so??? If it is not there, it is probable that the X-server for your target platform does not provide those functions. Therefore your only option is to configure without xdbe support (use the --disable-xdbe option to configure) then remove any references to libXext from the makeinclude file. After that, fltk should probably link OK without Xext and you should be able to proceed. and where to copy this particular file in cross platform environment. If it isn't provided with your environment, I expect that you will have to work without it. You can not just copy in another version from somewhere else, that will not work. Building fltk without xdbe support should be enough to allow you to work without libXext installed, usually. SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England Wales. Company no. 02426132 This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ___ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
