LOGIN   :::   RECOVER PASS   :::   GET ACCOUNT    
Browse
  • Projects
  • Code (CVS)
  • Forums
  • News
  • Articles
  • Polls
  •  
    OpenCores
  • FAQ
  • CVS HowTo
  • Mission
  • Media
  • Tools
  • Advertise
  • Mirrors
  • Logos
  • Contact us
  • Find Resources
  • Job Opportunity
  •  
    Tools
  • Search
      
  • Download Cores (CVSGet)
  •  
    More
  • Wishbone
  • Perlilog
  • EDA tools
  • OpenTech CD
  •  
    Navigation: All forums > Openrisc > Message List > Message Post

    Message

    Reply | Reply all
    Date Prev | Date Next | Thread Prev | Thread Next Date Index | Thread Index

    From: kobegpfan at yahoo.com<kobegpfan@y...>
    Date: Tue Jul 15 09:01:34 CEST 2008
    Subject: [openrisc] How to make uClibc -- It always fails
    Top
    Hi, Rich & Jeremy

    Thanks for your advices.
    I turned to use 2.6.19 kernel source and it works now.

    Best regards
    Kobe

    ----- Original Message -----
    From: rich_daddio at yahoo.com<rich_daddio@y...>
    To:
    Date: Fri Jul 11 13:23:29 CEST 2008
    Subject: [openrisc] How to make uClibc -- It always fails

    > Hi Kobe,
    > What is the KERNEL_SOURCE in your uclibc .config file? Make sure
    > you
    > point this to a valid 2.6.x kernel source. Down below it looks like
    > you are using KERNEL_SOURCE="uclinux/uClinux-2.0.x" which
    > is very old.
    > This might confuse a newer uclibc (such as 0.9.28.3).
    > HTH,
    > Rich d
    > ----- Original Message -----
    > From: kobegpfan at yahoo.com<kobegpfan at y...>
    > To:
    > Date: Fri Jul 11 03:35:07 CEST 2008
    > Subject: [openrisc] How to make uClibc -- It always fails
    > > Hi, Rich and Jeremy
    > >
    > > Thanks for your response that's very helpful.
    > > I checked the cross tool chains (or32 binutils and gcc), I can
    > > assure it
    > > works fine. Then based on your both suggestion, especailly by
    > > following
    > > MOF-opencores-build3, I made uclibc again. The previous error
    > > disappeared .... But unfortunately, new error arose as I
    > listed
    > > below.
    > > "or32-uclinux-"gcc -Wall -Wstrict-prototypes
    > > -Wno-trigraphs -fno-
    > > strict-aliasing -fno-builtin -nostdinc -D_LIBC -I../../include
    > -I.
    > > -Os -
    > > funit-at-a-time -isystem /opt/or32-uclinux/lib/gcc/or32-
    > > uclinux/3.4.4/include -DNDEBUG -D_DL_FINI_CRT_COMPAT -c
    > > ptsname.c -o ptsname.o
    > > ptsname.c:86:3: #error "__UNIX98PTY_ONLY__ enabled but
    > > TIOCGPTN
    > > ioctl not supported by your kernel."
    > > ptsname.c: In function `ptsname_r':
    > > ptsname.c:71: warning: unused variable `ptyno'
    > > make[2]: *** [ptsname.o] Error 1
    > > make[2]: Leaving directory
    > `/orp/tmp/uClibc-0.9.28.3/libc/stdlib'
    > > make[1]: *** [_dir_stdlib] Error 2
    > > make[1]: Leaving directory `/orp/tmp/uClibc-0.9.28.3/libc'
    > > make: *** [_dir_libc] Error 2
    > > In MOF-opencores_build3, it is said that "If you happen
    > to get
    > > some
    > > header errors in asm just go to those files and remove the
    > > '#include
    > > linux/config.h' since it is depracated." But this error
    > seems
    > > have nothing
    > > to do with this hint.
    > > Actually I am a hardware engineer. You know it's really a hard
    > work
    > > for
    > > me to debug it. I googled but found no useful information. I
    > have
    > > no
    > > choice but assort to your help.
    > > Best regards,
    > > Kobe
    > > ----- Original Message -----
    > > From: rich_daddio at yahoo.com<rich_daddio at y...>
    > > To:
    > > Date: Thu Jul 10 14:22:20 CEST 2008
    > > Subject: [openrisc] How to make uClibc -- It always fails
    > > > Hi,
    > > > Check out:
    > > > http://www.meansoffreedom.com/opencores_build3.html
    > > > click on sampledotconfig either copy to .config it or
    > > duplicate the
    > > > feature set for a start.
    > > > We do not support PIC at this time so you are enabling a
    > > feature
    > > > not
    > > > supported.
    > > > Please let me know how you make out either on the list or
    > via
    > > > rich_daddio at yahoo.com.
    > > > Thanks & Best Regards,
    > > > Rich d
    > > > ----- Original Message -----
    > > > From: kobegpfan at yahoo.com<kobegpfan at y...>
    > > > To:
    > > > Date: Thu Jul 10 03:04:32 CEST 2008
    > > > Subject: [openrisc] How to make uClibc -- It always fails
    > > > > I refered to several articles here and there. I used
    > > > > uClibc-0.9.28.3 and > > > > patched it with the 2 files released in > meansoffreedom: > > > > (1) uClibc-0.9.28-or32-libc-support.bz2 > > > > (2) uClibc-0.9.28-or32-unified.bz2. > > > > And then I run "make menuconfig" to modify > > something > > > like > > > > this > > > > TARGET_ARCH="or32" > > > > > > KERNEL_SOURCE="/orp/tmp/or1k/uclinux/uClinux-2.0.x" > > > > CROSS="or32-uclinux-" > > > > > RUNTIME_PREFIX="/opt/$(TARGET_ARCH)-uclinux" > > > > DEVEL_PREFIX="/opt/$(TARGET_ARCH)-uclinux" > > > > The above setting can be checked in .config file. > > > > Then I ran the following commands: > > > > (1)# ln -s extra/Configs/Config.or32.uclinux Config > > > > (2)# make all install > > > > But it stops with the following errors: > > > > make[3]: Entering directory > > > > `/orp/tmp/uClibc-0.9.28.3/libc/misc/regex' > > > > "or32-uclinux-"gcc -Wall -Wstrict-prototypes > > > > -Wno-trigraphs -fno- > > > strict-aliasing > -fno-builtin -nostdinc -D_LIBC > > -I../../../include > > > > -I. - > > > Os -funit-at-a-time -isystem > > /opt/or32-uclinux/lib/gcc/or32- > > > > uclinux/3.4.4/include -DNDEBUG -fPIC -c regex.c -o > regex.o > > > > /tmp/cconHoRg.s: Assembler messages: > > > > /tmp/cconHoRg.s:3837: Error: operation combines symbols > in > > > > different > > > segments > > > > /tmp/cconHoRg.s:3846: Error: operation combines symbols > in > > > > different > > > segments > > > > /tmp/cconHoRg.s:3847: Error: operation combines symbols > in > > > > different > > > segments > > > > /tmp/cconHoRg.s:3848: Error: operation combines symbols > in > > > > different > > > segments > > > > /tmp/cconHoRg.s:3849: Error: operation combines symbols > in > > > different > > segments > > > > /tmp/cconHoRg.s:3857: Error: operation combines symbols in > > > > different > > segments > > > /tmp/cconHoRg.s:3863: > Error: operation combines symbols in > > > different > > > segments > > > /tmp/cconHoRg.s:3864: Error: operation combines > symbols in > > > different > > segments > > > > /tmp/cconHoRg.s:3865: Error: operation combines symbols in > > > > different > > segments > > > /tmp/cconHoRg.s:3866: > Error: operation combines symbols in > > > different > > > segments > > > /tmp/cconHoRg.s:5083: Error: operation combines > symbols in > > > different > > segments > > > > /tmp/cconHoRg.s:5084: Error: operation combines symbols in > > > > different > > segments > > make[3]: *** > [regex.o] > Error 1 > > make[3]: Leaving directory > > > > `/orp/tmp/uClibc-0.9.28.3/libc/misc/regex' > > > make[2]: *** > [_dir_regex] Error 2 > > make[2]: Leaving > directory > > `/orp/tmp/uClibc-0.9.28.3/libc/misc' > > > make[1]: *** > [_dir_misc] Error 2 > > make[1]: Leaving > directory > `/orp/tmp/uClibc-0.9.28.3/libc' > > make: *** > [_dir_libc] > Error 2 > > I don't know what's happening > and how to fix it. > Would you > please > > give > > > me a hand? > > > > > > > > >

     
    Copyright (c) 1999 OPENCORES.ORG. All rights reserved.