Newbie question - tmpnam error
Kalai Narayanan-SSI
kalai.rajah@ssi.samsung.com
Mon Jan 28 22:53:00 GMT 2013
Yann,
I had to set the LDFLAGS because it was not picking up the correct library versions for gmp while compiling ppl (during the gmp version check).
CT_PREFIX_BUILD - I wanted the prefix to distinguish from the tools that were already installed on the system.
CT_CC_ENABLE_CXX_FLAGS - I went through a few online suggestions from stackoverflow.com and added them in. W/o these options, I was seeing the following error ...
[ERROR] checking for extra compiler flags for building... configure: error: --enable-cxx-flags needs compiler flags as arguments
[ERROR] checking for cexp in -lm... make[2]: *** [configure-target-libstdc++-v3] Error 1
[ERROR] make[1]: *** [all] Error 2
I didn't want to try the known build as I wanted support for arm64 in gcc and I could see that the linaro build had the support for it.
-Kalai
-----Original Message-----
From: Yann E. MORIN [mailto:yann.morin.1998@gmail.com] On Behalf Of Yann E. MORIN
Sent: Monday, January 28, 2013 2:43 PM
To: Kalai Narayanan-SSI
Cc: crossgcc@sourceware.org; Bryan Hundven
Subject: Re: Newbie question - tmpnam error
Kalai, All,
On Monday 28 January 2013 Kalai Narayanan-SSI wrote:
> Here is the .config. I have uploaded the build.log at
> https://www.dropbox.com/s/5oyqp6sz3aswkw0/build.log
[--SNIP--]
> CT_EXTRA_LDFLAGS_FOR_BUILD="-L/share/projects/IP/local_5.8/ct/arm-unkn
> own
> -linux-uclibcgnueabi/.build/arm-unknown-linux-uclibcgnueabi/buildtools/lib/"
> CT_EXTRA_LDFLAGS_FOR_HOST="-L/share/projects/IP/local_5.8/ct/arm-unkno
> wn-
> linux-uclibcgnueabi/.build/arm-unknown-linux-uclibcgnueabi/buildtools/lib/"
Why did you set the LDFLAGS thus? It is not needed at all, and will probably break the build is a way or another.
Leave that empty.
(BTW, how did you come to setting those variables to those exact values?)
[--SNIP-]
> CT_BUILD_PREFIX="arm-elf-"
What are you trying to achieve with that?
CT_BUILD_PREFIX tells ct-ng what to prepend to host tools (eg. the native gcc, ar, ld...).
Leave that empty, too.
[--SNIP--]
> CT_CC_ENABLE_CXX_FLAGS="-fno-data-sections -fno-function-sections"
Hmm. I think that, as a starter, you should try starting with a known working configuration, and change things one by one to your needs.
For example, start with the bundled arm-unknown-linux-uclibcgnueabi sample (as I explained in my previous mail).
Once you have a working toolchain from that sample, change one thing at a time and rebuild. That will give you a known-working starting point, and you can see what change breaks the build.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics'
| conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
--
For unsubscribe information see http://sourceware.org/lists.html#faq
More information about the crossgcc
mailing list