On Sat, Nov 10, 2012 at 11:17 AM, R. Diez <[email protected]>wrote:
> > > >There is another issue with the muclibc/mglibc flag too, this is how > >I addressed this: > > > https://github.com/skristiansson/or1k-gcc/commit/8750ecc93fdf6563c4bf5d6280181e80ead39c2b > >(note that this probably doesn't apply cleanly as is ontop of peters tree) > > That's probably the error "Multiple different help strings for mglibc" I'm > getting, I forgot to report it yesterday. It's here: > > > options.c:807:2: error: #error Multiple different help strings for mglibc: > > The source code at that place looks like this: > > #error Multiple different help strings for muclibc: > Use uClibc > Use uClibc C library > > I think it all comes from file gcc/config/or1k/or1k.opt : > > ;; muclibc / mglibc are defined in linux.opt, so we can't easily re-define > ;; how they are recorded. > ;; We could remove linux.opt from extra_options, but that could backfire if > ;; more options are added that we don't want to remove. Hence we use > ;; TARGET_HANDLE_OPTION. > > I wasn't sure how to handle this issue. I commented out that option and > mglibc too > in or1k.opt, and I got further, but this is probably not the right > solution, > because I'm getting the following error messages when building the bare > (non-Linux) > toolchain from the same sources: > > gcc/common/config/or1k/or1k-common.c:49:10: error: ‘OPT_muclibc’ > undeclared (first use in this function) > gcc/common/config/or1k/or1k-common.c:52:10: error: ‘OPT_mglibc’ undeclared > (first use in this function) > > > Can you confirm that, after your patch, both the Linux and the bare > toolchain build OK from the same sources? > > Yes, they should, that's at least the point of the patch ;) Stefan
_______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
