Re: Patch to remove hardcoded Header file locations

2008-06-06 Thread Jean-Marc Lasgouttes
Konrad Hofbauer <[EMAIL PROTECTED]> writes: > I have two versions on my system. Considering that, I think it is better to provide our own libintl. Why? 1/ it is never clear on the mac to know what version is available 2/ when cross compiling, it is even worse 3/ one has to compile against a st

Re: Remove BOOST (was Re: Patch to remove hardcoded Header file locations)

2008-06-05 Thread Andre Poenitz
On Tue, Jun 03, 2008 at 04:05:06PM +0200, Pavel Sanda wrote: > Abdelrazak Younes wrote: > > By the way, I think we should also remove boost from our source and just > > say that we depend on boost >= 1.34.0 which is already one year old. I > > checked the svn logs and we have no internal patch ap

Re: Patch to remove hardcoded Header file locations

2008-06-05 Thread Konrad Hofbauer
Jean-Marc Lasgouttes wrote: Yes, I know :) FWIW that is what some 'official' gnus programs like coreutils do, so being Abdel's preferred solution is less scary as it sounds. What I do not know is what is going to happen on platforms like MacOSX. I hace two versions on my system. One is $ /

Re: Patch to remove hardcoded Header file locations

2008-06-05 Thread Abdelrazak Younes
Jean-Marc Lasgouttes wrote: Abdelrazak Younes <[EMAIL PROTECTED]> writes: For me 2/, but you know that already :-) Yes, I know :) FWIW that is what some 'official' gnus programs like coreutils do, so being Abdel's preferred solution is less scary as it sounds. What I do not know is

Re: Patch to remove hardcoded Header file locations

2008-06-05 Thread Jean-Marc Lasgouttes
Abdelrazak Younes <[EMAIL PROTECTED]> writes: > For me 2/, but you know that already :-) Yes, I know :) FWIW that is what some 'official' gnus programs like coreutils do, so being Abdel's preferred solution is less scary as it sounds. What I do not know is what is going to happen on platforms li

Re: Patch to remove hardcoded Header file locations

2008-06-05 Thread Abdelrazak Younes
Jean-Marc Lasgouttes wrote: José Matos <[EMAIL PROTECTED]> writes: It can go in now. I will announce beta 3 soon. FWIW beta 3 was tagged and the resulting source packages were created yesterday. So for development purposes bet 3 is out already. :-) The only problem I have is that com

Re: Patch to remove hardcoded Header file locations

2008-06-05 Thread Jean-Marc Lasgouttes
José Matos <[EMAIL PROTECTED]> writes: > It can go in now. I will announce beta 3 soon. FWIW beta 3 was tagged and the > resulting source packages were created yesterday. So for development purposes > bet 3 is out already. :-) The only problem I have is that compiling with included gettext requ

Re: Patch to remove hardcoded Header file locations

2008-06-04 Thread José Matos
On Wednesday 04 June 2008 12:58:54 Jean-Marc Lasgouttes wrote: > Jose', please tell me when/if I can commit this (not before beta3, I > presume :) It can go in now. I will announce beta 3 soon. FWIW beta 3 was tagged and the resulting source packages were created yesterday. So for development pur

Re: Patch to remove hardcoded Header file locations

2008-06-04 Thread Jean-Marc Lasgouttes
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: > The solution is probably to upgrade gettext to the latest version. Or > to remove our gettext support stuff from trunk and let autoconf do its > thing. For information: I have a patch in my tree that removes all gettext stuff from the svn tree an

Re: Patch to remove hardcoded Header file locations

2008-06-03 Thread Jean-Marc Lasgouttes
Abdelrazak Younes <[EMAIL PROTECTED]> writes: > We should remove it. Windows builds use external intl already, so > should other platforms IMHO. I meant all the m4 infrastructure. I believe that the new way is to let autotools copy this, and avoid keeping stuff in svn, but I'll have to check. JM

Re: Remove BOOST (was Re: Patch to remove hardcoded Header file locations)

2008-06-03 Thread Abdelrazak Younes
Pavel Sanda wrote: Abdelrazak Younes wrote: By the way, I think we should also remove boost from our source and just say that we depend on boost >= 1.34.0 which is already one year old. I checked the svn logs and we have no internal patch applied since boost was upgraded, only some compiler

Re: Remove BOOST (was Re: Patch to remove hardcoded Header file locations)

2008-06-03 Thread Pavel Sanda
Abdelrazak Younes wrote: > By the way, I think we should also remove boost from our source and just > say that we depend on boost >= 1.34.0 which is already one year old. I > checked the svn logs and we have no internal patch applied since boost was > upgraded, only some compiler warning fixes.

Remove BOOST (was Re: Patch to remove hardcoded Header file locations)

2008-06-03 Thread Abdelrazak Younes
Jean-Marc Lasgouttes wrote: Konrad Hofbauer <[EMAIL PROTECTED]> writes: Dear developers, in two files a path to some system header files is hard-coded with /System/Library/Frameworks/CoreFoundation.framework/Headers The source of the problem is of course in gettext.m4, from which con

Re: Patch to remove hardcoded Header file locations

2008-06-03 Thread Abdelrazak Younes
Jean-Marc Lasgouttes wrote: Konrad Hofbauer <[EMAIL PROTECTED]> writes: Dear developers, in two files a path to some system header files is hard-coded with /System/Library/Frameworks/CoreFoundation.framework/Headers The source of the problem is of course in gettext.m4, from which con

Re: Patch to remove hardcoded Header file locations

2008-06-03 Thread Jean-Marc Lasgouttes
Konrad Hofbauer <[EMAIL PROTECTED]> writes: > Dear developers, > > in two files a path to some system header files is hard-coded with > /System/Library/Frameworks/CoreFoundation.framework/Headers The source of the problem is of course in gettext.m4, from which configure is generated. It seems t

Re: Patch to remove hardcoded Header file locations

2008-06-02 Thread Konrad Hofbauer
Konrad Hofbauer wrote: Attached two very simple patches (against the 1.6.0beta2 release) which seem to fix the problem. Hold on. My first suggested patch ever, and already it is wrong. So what I would THINK is correct (according to the gcc manual) is the attached new patch. However I cannot t