| 1 |
On 06-12-2007 21:58:08 +0100, Fabian Groffen wrote: |
| 2 |
> On 06-12-2007 21:48:42 +0100, Fabian Groffen wrote: |
| 3 |
> > On 06-12-2007 21:43:53 +0100, Fabian Groffen wrote: |
| 4 |
> > > The real issue seems to be that the iconv.h from /usr/include is taken |
| 5 |
> > > not the one from the prefix. On Darwin9 this file has changed indeed. |
| 6 |
> > > The Solaris patch we apply is wrong too, as it basically patches it to |
| 7 |
> > > work with /usr/include/iconv.h. |
| 8 |
> > > |
| 9 |
> > > I've yet to find out why c++ finds iconv.h from the host OS first... |
| 10 |
> > |
| 11 |
> > And to complete the confusion... c++ -E shows that it DOES include |
| 12 |
> > prefix' iconv.h and that the expanded function doesn't have any const in |
| 13 |
> > there, neither does the declared function it has pulled in... |
| 14 |
> > |
| 15 |
> > I'm completely puzzled now... |
| 16 |
> |
| 17 |
> Some tool at Apple decided to change libiconv's invocation... |
| 18 |
> http://www.opensource.apple.com/darwinsource/10.5/libiconv-24/patches/unix03.patch |
| 19 |
> http://www.opensource.apple.com/darwinsource/10.5/libiconv-24/patches/manpage.patch |
| 20 |
> |
| 21 |
> and then some tool from doxygen thought this was the "default" |
| 22 |
> behaviour, whereas "upstream" libiconv is just plain sec how it should |
| 23 |
> be... |
| 24 |
|
| 25 |
Ok... even worse. Looks like libiconv changes its headerfile itself |
| 26 |
based on the host OS... |
| 27 |
|
| 28 |
|
| 29 |
-- |
| 30 |
Fabian Groffen |
| 31 |
Gentoo on a different level |
| 32 |
-- |
| 33 |
gentoo-alt@g.o mailing list |
Archives