After I sent my post about this yesterday, I noticed something about the error message:
undefined reference to `___gxx_personality_sj0'
I noticed that `___gxx_personality_sj0' begins with THREE underscores. I haven't looked at the code at all, and don't know anything about it. But if the THREE underscores were a typo for TWO underscores, it might explain why the reference is undefined. Can anyone say whether the code contains references that begin with THREE underscores?
Tom
On Sun, 10 Jan 2010 08:34:28 -0500, Thomas wrote:
Hi,
After I sent my post about this yesterday, I noticed something about the error message:
undefined reference to `___gxx_personality_sj0'
I noticed that `___gxx_personality_sj0' begins with THREE underscores. I haven't looked at the code at all, and don't know anything about it. But if the THREE underscores were a typo for TWO underscores, it might explain why the reference is undefined. Can anyone say whether the code contains references that begin with THREE underscores?
I don't think this is a typo. It's rather a private symbol inside gcc (or one of its libraries).
And this is the point: this symbol is never used in Geany nor in Scintilla. I assume you are missing a gcc/g++ library or anything else is wrong with your compiler installation within Cygwin. Mostly unrelated to Geany, I'm afraid. But I didn't play with Cygwin for a few years, so I can't say that much.
The question which raises to me: why are you doing that at all? That is, why do you want to compile Geany in Cygwin? I think the native Windows port is faster and at least easier to use.
Regards, Enrico
The question which raises to me: why are you doing that at all? That is, why do you want to compile Geany in Cygwin? I think the native Windows port is faster and at least easier to use.
Cygwin creates native windows executables AFAIK.
Best regards.
On Sun, Jan 10, 2010 at 9:46 AM, Thomas Martitz thomas.martitz@student.htw-berlin.de wrote:
The question which raises to me: why are you doing that at all? That is, why do you want to compile Geany in Cygwin? I think the native Windows port is faster and at least easier to use.
Cygwin creates native windows executables AFAIK.
Well, the usual way to develop under Cygwin is to write source code which assumes a POSIX environment. When you compile this, Cygwin links to its own special DLL which provides POSIX emulation. So, most Cygwin applications are "native" in the sense that they are Windows binaries, but they are also not native in the sense that someone without the Cygwin DLL cannot run that application.
According to the Cygwin site, there are compiler options which let you link directly to Microsoft's libraries and NOT use the Cygwin DLL, but then you cannot assume the POSIX environment and you must code for native Windows. In this scenario, Cygwin is essentially just providing the Unix-like command shell and Unix-like compilation tools.
Presumably, if someone is talking about using Cygwin to compile Geany, what they mean is they want to compile the source as if they were on *nix, but doing so on their Cygwin-equipped Windows machine. This would fall under the Cygwin-DLL-requiring scenario. Enrico's point is: Why not just use the Windows version of Geany?
The only reason I can think of (and I am just guessing here, because I don't use Cygwin myself) is that the OP wants to use Geany as his Cygwin editor/IDE, and that a truly native Windows version (that doesn't use the Cygwin DLL) wouldn't be able to correctly access the Cygwin environment where all his development stuff is.
John
Am 10.01.2010 22:53, schrieb John Yeung:
On Sun, Jan 10, 2010 at 9:46 AM, Thomas Martitz thomas.martitz@student.htw-berlin.de wrote:
The question which raises to me: why are you doing that at all? That is, why do you want to compile Geany in Cygwin? I think the native Windows port is faster and at least easier to use.
Cygwin creates native windows executables AFAIK.
Well, the usual way to develop under Cygwin is to write source code which assumes a POSIX environment. When you compile this, Cygwin links to its own special DLL which provides POSIX emulation. So, most Cygwin applications are "native" in the sense that they are Windows binaries, but they are also not native in the sense that someone without the Cygwin DLL cannot run that application.
According to the Cygwin site, there are compiler options which let you link directly to Microsoft's libraries and NOT use the Cygwin DLL, but then you cannot assume the POSIX environment and you must code for native Windows. In this scenario, Cygwin is essentially just providing the Unix-like command shell and Unix-like compilation tools.
I assumed he aimed for that (i.e. follow the last point you mentioned). The windows port of geany is native. I should've said "is able to create" :)
Presumably, if someone is talking about using Cygwin to compile Geany, what they mean is they want to compile the source as if they were on *nix, but doing so on their Cygwin-equipped Windows machine. This would fall under the Cygwin-DLL-requiring scenario. Enrico's point is: Why not just use the Windows version of Geany?
The only reason I can think of (and I am just guessing here, because I don't use Cygwin myself) is that the OP wants to use Geany as his Cygwin editor/IDE, and that a truly native Windows version (that doesn't use the Cygwin DLL) wouldn't be able to correctly access the Cygwin environment where all his development stuff is.
John
Thanks for clearing this up. The only thing I build under cygwin so far didn't depend on cygwin.dll after compilation.
Best regards.
On Sun, 10 Jan 2010 16:53:10 -0500, John wrote:
On Sun, Jan 10, 2010 at 9:46 AM, Thomas Martitz thomas.martitz@student.htw-berlin.de wrote:
The question which raises to me: why are you doing that at all? That is, why do you want to compile Geany in Cygwin? I think the native Windows port is faster and at least easier to use.
Cygwin creates native windows executables AFAIK.
Well, the usual way to develop under Cygwin is to write source code which assumes a POSIX environment. When you compile this, Cygwin links to its own special DLL which provides POSIX emulation. So, most Cygwin applications are "native" in the sense that they are Windows binaries, but they are also not native in the sense that someone without the Cygwin DLL cannot run that application.
According to the Cygwin site, there are compiler options which let you link directly to Microsoft's libraries and NOT use the Cygwin DLL, but then you cannot assume the POSIX environment and you must code for native Windows. In this scenario, Cygwin is essentially just providing the Unix-like command shell and Unix-like compilation tools.
Presumably, if someone is talking about using Cygwin to compile Geany, what they mean is they want to compile the source as if they were on *nix, but doing so on their Cygwin-equipped Windows machine. This would fall under the Cygwin-DLL-requiring scenario. Enrico's point is: Why not just use the Windows version of Geany?
The only reason I can think of (and I am just guessing here, because I don't use Cygwin myself) is that the OP wants to use Geany as his Cygwin editor/IDE, and that a truly native Windows version (that doesn't use the Cygwin DLL) wouldn't be able to correctly access the Cygwin environment where all his development stuff is.
Yeah, that could be a sane use case which would disqualify the native build. Still, as I wrote earlier, I'm not sure what's wrong. To me, it looks rather like an error in the build system setup (gcc, g++ + their libs) than a problem in Geany itself.
Regards, Enrico