This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
2011/5/26 Yann E. MORIN <yann.morin.1998@anciens.enib.fr>: > Bryan, Benoit, All, > > On Wednesday 25 May 2011 22:25:58 Bryan Hundven wrote: >> I have other uses for 'has_or_warn' and setting >> $some-external-lib_available as well. >> For instance the problem that ANDY had with fedora packaging only >> shared with -devel packages, and needing to install a seperate -static >> package in the distribution would allow being able to toggle the >> availability of building a static toolchain (i.e. if libncurses5.a is >> not availble, don't allow static toolchains, but also warn during >> ./configure time.) > > The first step is to warn at ./configure time. Propagating the result > down to kconfig can come later. > > We have to be very carefull as to how we do it. We do not want to create > a complex infrastructure for passing such options. Also, we do not want > to add too many such options, or it would become a nightmare to maintain. > > Really, I would stay on the safe side and require a bit of knowledge from > the end user to properly setup his/her host. > > After all, one should not consider building a toolchain a trivial task; > it really requires some thought before-hand. That we ease the toolchain > build in itself is good; that we abstract all the requirements is bad. > > We should only provide safeguards to detect errors, such as this libexpat > stuff, and not forbid doing stupid things, such as asking for a staticaly > linked toolchain when static libs are not installed. Yup! What I am thinking to do with this, specifically, is check for libstdc++.a on the build host to resolve issue #3 at the bottom of: http://sourceware.org/ml/crossgcc/2011-01/msg00100.html On Debian, all you need is already provided by `libstdc++6-4.x-dev', which is required by `g++-4.x (x being 4.4, 4.5, or 4.6). On Fedora, you can install g++ and still not get the static libraries, unless you specifically install `libstdc++-static'. The goal was not to create a warning specific to Fedora, but to say: *** Warning: ${lib} is missing from your build host. ***\n *** Because of this some options will not be available. *** But just depending on the CONFIG_has_${lib} might be good enough. >> I can provide the 'has_or_warn' code and an example with libncurses5.a I really did say libncurses5.a. I meant libstdc++.a. Sorry for the confusion. ;) >> if you want, but you or BenoÃt should be able to implement >> 'has_or_warn' as well ;) > > It's not as if has_or_warn was very complex to come up with! ;-) > I'll push a version a bit later. > > Then you can build upon this to add your stuff. Heh, I wasn't sweating the has_or_warn function, it was propagating the options to kconfig that had me worried. Well done! > 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. Â| > '------------------------------^-------^------------------^--------------------' > -Bryan -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |