[PATCH 1 of 1] complibs/cloog: with static ppl, DAœorrectly link with libm
Yann E. MORIN
yann.morin.1998@anciens.enib.fr
Fri Aug 6 15:28:00 GMT 2010
Arnaud, All,
On Friday 06 August 2010 170615 Arnaud Lacombe wrote:
> On Thu, Aug 5, 2010 at 6:18 PM, Yann E. MORIN
> <yann.morin.1998@anciens.enib.fr> wrote:
> > [...]
> > cloog_opts+=( --disable-shared --enable-static )
> > - cloog_LDFLAGS='-lstdc++'
> > + cloog_LDFLAGS='-lstdc++ -lm'
> > fi
> >
> > CFLAGS="${CT_CFLAGS_FOR_HOST}" \
> >
> as a side note, this will be needed if one expect to use ct-ng on
> NetBSD. There has been a bug in 5.x which was fixed later on.
Nice to know. Thanks.
> Beside that, 2 questions:
> - does the missing symbols concerns libstdc++, from what I see in the
> errors triggered, the missing symbols come from ppl; wouldn't "-lm
> -lstdc++" do the job as well ?
Hmm... I don't know, I did not try. Even if the symbol is required by ppl
and not libstdc++, then having -lm after -lstdc+ is not very important.
The reverse would have been. Do we really care?
> - didn't you forgot the cc/gcc.sh part ?
I have two queus here: 'incoming', that gets only patches from the list,
and 'outgoing' that gets only my patches. I assume that patches in
'incoming' will be reviewed in the thread they originate from. and I do
not want to pollute the list with duplicates.
The gcc part is alrady on the list, so comments should go as a response
to the OP in the original thread. The two fixes apply to the same issue,
but are not dependent (code-wise) each on the other. So two threads
seemed OK to me.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +0/33 662376056 | Software Designer | \ / CAMPAIGN | ^ |
| --==< O_o >==-- '------------.-------: X AGAINST | /e\ There is no |
| http://ymorin.is-a-geek.org/ | (*_*) | / \ HTML MAIL | """ conspiracy. |
'------------------------------'-------'------------------'--------------------'
--
For unsubscribe information see http://sourceware.org/lists.html#faq
More information about the crossgcc
mailing list