Hi,
I remember your work for www.sunfreeware,com long time ago, and now you
are my hero again!
Thank you/Σας ευχαριστώ!
On 02/ 5/14 06:07 PM, Apostolos Syropoulos wrote:
Hello,
I have compiled OpenOffice 4.1.0 and I have posted to
Thank you very much!!
you are Great !!
Paolo
On 02/ 5/14 06:07 PM, Apostolos Syropoulos wrote:
Hello,
I have compiled OpenOffice 4.1.0 and I have posted to
https://asyropoulos.wordpress.com/2014/02/05/compiling-openoffice4/
my compilation notes. BTW, I have used GCC 4.8.2 and GNU ld. BTW,
I
On Wed, Feb 5, 2014 at 5:07 PM, Apostolos Syropoulos
asyropou...@yahoo.comwrote:
Hello,
I have compiled OpenOffice 4.1.0 and I have posted to
https://asyropoulos.wordpress.com/2014/02/05/compiling-openoffice4/
my compilation notes. BTW, I have used GCC 4.8.2 and GNU ld. BTW,
I had tried
Maybe you two should team up on both these packages??
On 2014-02-06 11:11, Peter Tribble wrote:
On Wed, Feb 5, 2014 at 5:07 PM, Apostolos Syropoulos
asyropou...@yahoo.comwrote:
Hello,
I have compiled OpenOffice 4.1.0 and I have posted to
I'd have thought a SIGSEGV immediately on startup indicates a problem
with the compilers and/or library sets used???
What compiler(s) and libraries and other stuff are you using for
LibreOffice?
On 2014-02-06 11:11, Peter Tribble wrote:
On Wed, Feb 5, 2014 at 5:07 PM, Apostolos Syropoulos
I tried a brand new user, and the problem remains:
except I can see there's an initial bit where a couple of things work: I
could define a new background wallpaper and, select using gnome rather
than xterm, and I could start a terminal.
However, no bottom or top panels showed, and after a
No, I'm thinking of some experiences from ages ago, where some compilers
would actually produce SIGSEGV errors due to incompatible stack and
procedure call standards between the compiler and some part of a lib used.
On 2014-02-06 13:38, James Carlson wrote:
On 02/06/14 07:33, Hans J.
On Thu, Feb 6, 2014 at 12:33 PM, Hans J. Albertsson
hans.j.alberts...@branneriet.se wrote:
I'd have thought a SIGSEGV immediately on startup indicates a problem with
the compilers and/or library sets used???
It looks like:
#0 0x087056ac in ?? ()
#1 0xfdd1eed1 in
On 02/ 6/14 11:11 AM, Peter Tribble wrote:
On Wed, Feb 5, 2014 at 5:07 PM, Apostolos Syropoulos
asyropou...@yahoo.comwrote:
Hello,
I have compiled OpenOffice 4.1.0 and I have posted to
https://asyropoulos.wordpress.com/2014/02/05/compiling-openoffice4/
my compilation notes. BTW, I have
FWIW
You can overflow the stack with automatic variables. I've run into this many
times with large arrays in main() and elsewhere. The symptom is SEGV on entry
to the function. It's not uncommon to encounter code that works fine on
several systems, but SEGVs on another.
Hi,
2014 April 8 ... this is the End ...
End of what ?
Just the End of Microsoft support for Windows XP.
Time passing, 2014 April 8 will be the beginning of more and more Windows XP
botnets.
Facts : to day about 20 - 30 % of desktop are still running Windows XP (almost
50% are in China).
11 matches
Mail list logo
