From: Aidan Williams <aidan@nicta•com.au>
To: Simon Jung <palasim@gmx•de>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: uCLinux for PPC: Bug in autoconf.h creation
Date: Thu, 07 Sep 2006 21:51:14 +1000 [thread overview]
Message-ID: <450007B2.4010508@nicta.com.au> (raw)
In-Reply-To: <44FFE5C9.2070203@gmx.de>
I would suspect CRLF issues..
Try running dos2unix on your
arch/ppc/platforms/xilinx_auto/auto-config.in
and then defaulting all your settings with make menuconfig to regenerate your kernel .config and config headers.
- aidan
Simon Jung wrote:
> I am trying to build a uCLinux Distribution for PowerPC following the
> instructions on
>
> http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux/uclinux_powerpc/
> <http://www.itee.uq.edu.au/%7Ejwilliams/mblaze-uclinux/uclinux_powerpc/>
>
> "make menuconfig" works well but the created file
> /linuxppx-2.4.x/include/linux/autoconf.h has errors:
>
> The created "#defines" for integer and string types are mistyped the
> closing bracket / quote is written into a newline.
> Example:
>
> #define CONFIG_XILINX_PPC405_0_DISABLE_OPERAND_FORWARDING (1
> )
> #define CONFIG_XILINX_PPC405_0_DETERMINISTIMULT (0
> )
> #define CONFIG_XILINX_PPC405_0_MMU_ENABLE (1
> )
> #define CONFIG_XILINX_PPC405_0_DCR_RESYNC (0
> )
> #define CONFIG_XILINX_PPC405_0_INSTANCE "ppc405_0
> "
> #define CONFIG_XILINX_PPC405_0_HW_VER "2.00.c
> "
> #define CONFIG_XILINX_ON1_DMA_MASTER_0_INSTANCE "on1_dma_master_PPC
> "
>
> How can I correct the generation of autoconf.h ?
>
> Greetings,
> Simon Jung
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs•org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
next prev parent reply other threads:[~2006-09-07 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-07 9:26 uCLinux for PPC: Bug in autoconf.h creation Simon Jung
2006-09-07 11:51 ` Aidan Williams [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-07 9:26 Simon Jung
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=450007B2.4010508@nicta.com.au \
--to=aidan@nicta$(echo .)com.au \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=palasim@gmx$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox