Hey Stephen!  The version of gcc I'm using is actually 5.2.0 and I
don't think the OS is configured incorrectly, that's just how TC was
designed to run.  Instead of installing packages in a traditional
means like Debian, TC uses squashfs files and symlinks its contents to
the /usr/local/ area of the system.  I haven't had any issues with
compiling other software, just the BB source.  Thanks for the info
though!

Dave


On 7/22/16, Stephen Beckwith <[email protected]> wrote:
> I ran into a similar issue with menuconfig not finding ncurses library as
> well.  After talking with IT folks, we used HOSTCC='gcc -Wl, -llibtinfo' to
> get it to work - initially - the menu was "horrible". . . .
> After some debugging of other problems, I discovered that there were 2
> different compilers available on our systems:
> path1:  GCC 4.2.1 - which had the problems
> path2:  GCC 4.4.7 - which solved this and other problems.
> So it might be that the linux distro being used is not quite setup
> correctly????  Or it's a very old compiler?
> My situation is that the IT folks have tried to turn a Linux distro
> (RHEL6.4) into a BSD Variant-looking-messed-up-sort-of-thing. . . .
> NEVER had an issue running on FedoraCore22 in a VM on my MAC :)
>
> Regards,
> Stephen
>
> On Fri, Jul 22, 2016 at 12:48 PM, ..mg.. <[email protected]> wrote:
>
>>
>> On Thu, Jul 21, 2016 at 09:40:21PM +0200, Laurent Bercot wrote:
>> >
>> >  make menuconfig \
>> >     HOST_EXTRACFLAGS='-I/opt/ncurses/include -DKBUILD_NO_NLS
>> -DCURSES_LOC="<ncurses/ncurses.h>"' \
>> >     HOST_LOADLIBES='-L/opt/ncurses/lib -static -lncurses'
>> >
>> >  Yes, that's HOST_LOADLIBES with an 'E'.
>>
>>
>> Ah!  That's obnoxiously obscure, but probably better than my trick of
>> putting loader flags in CC.
>>
>> -mg
>>
>> >
>> > --
>> >  Laurent
>> >
>> > _______________________________________________
>> > busybox mailing list
>> > [email protected]
>> > http://lists.busybox.net/mailman/listinfo/busybox
>> _______________________________________________
>> busybox mailing list
>> [email protected]
>> http://lists.busybox.net/mailman/listinfo/busybox
>>
>
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox

Reply via email to