Vikas TM wrote: > Dear all, > > facing error saying, > cp /usr/slask/pwav/checkout/mcu/hcl/vikas/mcu/dropbear-0.44/scp > /usr/slask/pwav/checkout/mcu/hcl/vikas/mcu/targfs/usr/bin > powerpc-linux-uclibc-strip > /usr/slask/pwav/checkout/mcu/hcl/vikas/mcu/targfs/usr/bin/dropbearmulti > powerpc-linux-uclibc-strip: > /usr/slask/pwav/checkout/mcu/hcl/vikas/mcu/targfs/usr/bin/dropbearmulti: > File format not recognized > make: *** [dropbear-inst] Error 1 > > Any one please provide solution for above problem. > > Thanks > Vikas TM > Likely dropbearmult is not in powerpc format. Use 'file' or readelf tools to check if it has been correctly cross-compiled.
Cheers. Carmelo. P.S. Anyway, you are still posting not uclibc issues. So I kindly ask you to review carefully your build system and do deeper trouble analysis. > > On 11/19/07, Vikas TM <[EMAIL PROTECTED]> wrote: > >> I Able overcome this error. thanks Carmelo for your support. >> Carmelo, facing new error saying >> >> powerpc-linux-uclibc-strip targfs/allgon/swupdate >> cp /usr/share/allgon/BINARIES/MCU_Frontboard/MCU_Frontboard_1.1.0.bin >> targfs/usr/share/ >> make: *** No rule to make target `dropbear', needed by `dropbear-inst'. >> Stop. >> >> Can you please provide solution for this error. >> >> thanks >> Vikas TM >> >> On 11/19/07, Carmelo AMOROSO <[EMAIL PROTECTED]> wrote: >> >>> Vikas TM wrote: >>> >>>> Hi Carmelo, >>>> >>>> --with-logfile="/dev/null" >>>> configure: WARNING: If you wanted to set the --build type, don't use >>>> --host. >>>> If a cross compiler is detected then cross compile mode will be used. >>>> >>>> >>> I suspect your cross-compiler is not really cross; you need to configure >>> it for the correct target, >>> likely you exchanged --host with --target. >>> Check you configuration running powerpc-linux-uclibc-gcc -v. >>> For example, my cross sh4 gcc is configured with: >>> --host=i686-pc-linux-gnu --target=sh4-linux-uclibc >>> >>> plus other configurations on directories, sysroot >>> >>> Not really a uclibc issue, instead a gcc/buildroot problem. >>> So you should ask support to buildroot list, or review your toolchain >>> configuration. >>> >>> >>>> checking what to build and install... agent mibs >>>> using default "enterprise.net-snmp" >>>> using default enterprise sysOID "NET-SNMP-MIB::netSnmpAgentOIDs..." >>>> using default notifications "NET-SNMP-MIB::netSnmpNotifications" >>>> checking if I need to feed myself to ksh... no >>>> checking for powerpc-linux-gcc... powerpc-linux-uclibc-gcc >>>> checking for C compiler default output file name... configure: error: >>>> C compiler cannot create executables >>>> >>>> >>> clearly a mis-configured gcc issue >>> >>>> See `config.log' for more details. >>>> >>>> >>> did you look at it? >>> >>>> make: *** [net-snmp-5.1/.configured] Error 77 >>>> >>>> Can you please provide solution for this error. >>>> >>>> Thanks >>>> Vikas TM >>>> >>>> >>>> >>>> >>> Regards, >>> Carmelo >>> >>>> On 11/19/07, Carmelo AMOROSO <[EMAIL PROTECTED]> wrote: >>>> >>>> >>>>> Vikas TM wrote: >>>>> >>>>> >>>>>> Thanks Carmelo, >>>>>> >>>>>> Previously i made these changes what you mentioned now. still i am >>>>>> unable to compile & ld. can you please specify what are the changes >>>>>> required in the Makefile with an example Makefile.. >>>>>> >>>>>> >>>>>> >>>>> really none. Why don't you post the error log .. likely some one could >>>>> give you an hint. >>>>> Carmelo >>>>> >>>>> >>>>>> Thanks >>>>>> Vikas TM >>>>>> On 11/19/07, Carmelo AMOROSO <[EMAIL PROTECTED]> wrote: >>>>>> >>>>>> >>>>>> >>>>>>> Carmelo AMOROSO wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>>> Vikas TM wrote: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> Dear all, >>>>>>>>> >>>>>>>>> Please provide me nessessary changes required to migrate from glibc to >>>>>>>>> uclibc (Ex: Makefile changes (busybox, utils,...etc) & config file >>>>>>>>> changes). >>>>>>>>> >>>>>>>>> Thanks in advance >>>>>>>>> - >>>>>>>>> regards >>>>>>>>> Vikas TM >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> Once you have your uClibc built and you cross compiler proper >>>>>>>> configured >>>>>>>> for uClibc, >>>>>>>> nothing special to do... just use the correct cross-compilation >>>>>>>> environment, usually >>>>>>>> you need to set accordingly CC and LD env variables. >>>>>>>> >>>>>>>> You may have some problems linking some applications is you same >>>>>>>> functionalities >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> ... some applications if they use some functionalities that are not >>>>>>> enabled .... >>>>>>> >>>>>>> Sorry, the sentenc was really not understandable. >>>>>>> >>>>>>> >>>>>>> >>>>>>>> are not enabled and/or implemented within uClibc (i.e. gettext >>>>>>>> functions >>>>>>>> if you app >>>>>>>> is localized, but in this case you colud link against libintl, onece >>>>>>>> you >>>>>>>> have built it for uClibc). >>>>>>>> >>>>>>>> STLinux 2.3 distribution (www.stlinux.com) now provides a complete >>>>>>>> distribution (almost 400 packages) >>>>>>>> based on uClibc (nptl) for SH4. You may have a look to see the list of >>>>>>>> packages released. >>>>>>>> >>>>>>>> Regards, >>>>>>>> Carmelo >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> uClibc mailing list >>>>>>>>> [email protected] >>>>>>>>> http://busybox.net/cgi-bin/mailman/listinfo/uclibc >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> uClibc mailing list >>>>>>>> [email protected] >>>>>>>> http://busybox.net/cgi-bin/mailman/listinfo/uclibc >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>> >>>> >>>> >>> >> -- >> cheers & regards >> Vikas TM >> >> > > > _______________________________________________ uClibc mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/uclibc
