![]() |
|
#1
|
|||
|
|||
Compile errors on FLUHi,
I wanted to compile FLU on ubuntu hardy amd64, but I get this error: Code:
I need it for icc-Examin and oyranos |
|||
|
#2
|
|||
|
|||
Re: Compile errors on FLUI have the same issue. Any fix for this on 64bit OS?
|
|
#3
|
|||
|
|||
Re: Compile errors on FLUQuote:
Open Flu_Tree_Browser.h in your text editor. Here's line 349: CPP / C++ / C Code:
Comment it out and add a line as follows: CPP / C++ / C Code:
g++ version 4 doesn't like the superfluous ‘Flu_Tree_Browser::' since it's inside the class definition. Regards, Dave |
|
#4
|
|||
|
|||
Re: Compile errors on FLUThanks, but I get these errors
Code:
|
|
#5
|
|||
|
|||
Re: Compile errors on FLUQuote:
Here's the code: CPP / C++ / C Code:
Here's the problem: The person who wrote the code has assumed that pointers are the same size as ints. Proper program design never (that's never) assumes stuff like "size of a pointer is the same as the size of whatever...," since C and C++ language standards specifically state that sizes of integer data types are allowed to vary from one implementation (compiler) to another. The result is that there is no guaranteed relationship between the size of any particular integer data type and pointer size for that compiler. Specifically, for GNU compilers for 64-bit systems, a pointer is 64-bits and an unsigned int is 32-bits. Therefore it won't compute. Note that For GNU compilers for 32 bit systems (and just about all current 32-bit compilers), pointers are 32-bits and unsigned ints are 32-bits. therefore this is (apparently) not a problem for those. This is one of the reasons that I stopped installing 64-bit Linux on any of my working systems. There is a ton of legacy code out there that does stuff like this. (This may be getting better as some of the authors/maintainers wise up in the light of current developments.) Maybe some other reader of this forum has found some modifications that will work. There are other fltk forums; maybe there is a solution on one of those. You could complain (politely, of course, since the software is free) to the author and/or maintainer of the code. I think there very well may be "simple" ways to "fix" it, but I have no way to test anything like this, and no desire to waste your time. Or you could install the 32-bit version of your operating system if this is a possibility. Regards, Dave |
|
#6
|
|||
|
|||
Re: Compile errors on FLUQuote:
Well, I fired up my 64-bit Centos 5.2 testbed/sandbox and discovered a way to get the FLU stuff to compile. Here's the readme from the attached zip file: Code:
I would like to emphasize that I haven't done much testing, and don't intend to do more, so if it doesn't help, then perhaps the best bet would be to contact the author. Actually, in my opinion, the best bet would be to use a 32-bit Linux distribution rather than a 64-bit one, but that may not be something you can do. Regards, Dave |
|
#7
|
|||
|
|||
Re: Compile errors on FLUThank you very much davekw7x! I'll have a look into it when I got some more time. I compiled oyranos without flu, because the developer of oyranos (Kai-Uwe Behrmann) replaced the references to FLU in his project with some other file management.
When I got success I'll try to inform the author of FLU, to make his package more x64 compatible. I have to admit, that it's a sad old news, that one should better avoid linux 64bit operating system nowadays, because of a bunch of applications that are not yet enabled to be used on these platforms. And you're right: I made that mistake 2 or three years ago, but I don't want to change my sytem yet. |
|
#8
|
|||
|
|||
Re: Compile errors on FLUQuote:
Well, I'm not sure that it's a "mistake." Let's just call it a "learning opportunity." The reason that I hang around gidforums is that I always learn something here---always. The reason that I go through things like this when I don't have to is that I'm guessing that some day I might run across (or create) an application that can actually require--or at least take advantage of--- 64-bit systems. (It hasn't happened yet for me personally, but it could happen, I'm thinking.) Regards, Dave |
|
#9
|
|||
|
|||
Re: Compile errors on FLU@davekw7x
Possible to upload the fix? I am unable to download the attachment |
|
#10
|
|||
|
|||
Re: Compile errors on FLUQuote:
Regards, Dave |
Recent GIDBlog
Not selected for officer school by crystalattice
| Thread Tools | Search this Thread |
| Rate This Thread | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Need urgent help. Nonsensical compile errors on test code (for game) | seasons | C++ Forum | 1 | 29-Nov-2007 12:41 |
| Compile Errors | jdbrine | C++ Forum | 3 | 30-Jun-2006 11:11 |
| Help needed in fixing compile errors. | daisy_polly | C++ Forum | 3 | 25-Jun-2006 17:47 |
| Compile Errors due to Default Parameters | jdbrine | C++ Forum | 1 | 17-Jun-2006 14:45 |
| Compile errors | earachefl | C++ Forum | 3 | 24-Feb-2006 16:49 |
Network Sites: GIDNetwork · GIDWebHosts · GIDSearch · Learning Journal by J de Silva, The