Kernel compile problem

in arch 0.7, when i compile redhat hat kernel 2.4.21-27.0.1.EL, gcc 3.4.3 complains:
gcc -D__KERNEL__ -I/data/linux-2.4.21-27.0.1.EL/include -Wall -Wstrict-prototypes -Wno-trigraphs -O3 -fno-strict-aliasing -fno-common  -Wno-unused -funroll-loops -fomit-frame-pointer -fomit-frame-pointer -pipe -freorder-blocks -mpreferred-stack-boundary=2 -march=pentium4   -DKBUILD_BASENAME=main -c -o init/main.o init/main.c
In file included from /data/linux-2.4.21-27.0.1.EL/include/linux/sched.h:24,
                from /data/linux-2.4.21-27.0.1.EL/include/linux/mm.h:22,
                from /data/linux-2.4.21-27.0.1.EL/include/linux/slab.h:14,
                from /data/linux-2.4.21-27.0.1.EL/include/linux/proc_fs.h:5,
                from init/main.c:15:
/data/linux-2.4.21-27.0.1.EL/include/linux/smp.h:31: error: conflicting types for 'smp_send_reschedule'
/data/linux-2.4.21-27.0.1.EL/include/asm/smp.h:41: error: previous declaration of 'smp_send_reschedule' was here
/data/linux-2.4.21-27.0.1.EL/include/linux/smp.h:31: error: conflicting types for 'smp_send_reschedule'
/data/linux-2.4.21-27.0.1.EL/include/asm/smp.h:41: error: previous declaration of 'smp_send_reschedule' was here
In file included from /data/linux-2.4.21-27.0.1.EL/include/linux/unistd.h:9,
                from init/main.c:17:
/data/linux-2.4.21-27.0.1.EL/include/asm/unistd.h:382: warning: conflicting types for built-in function '_exit'
make: *** [init/main.o] Error 1
gcc info:
Reading specs from /usr/lib/gcc/i686-pc-linux-gnu/3.4.3/specs
Configured with: ../gcc-3.4.3/configure --prefix=/usr --enable-shared --enable-languages=c,c++,objc --enable-threads=posix --enable-__cxa_atexit
Thread model: posix
gcc version 3.4.3
but when i compile the kernel src in redhat as 3 with the same kernel config , compiling options and kernel compiling procedure, everything is ok. the gcc info:
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux
Thread model: posix
gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-20)
what's the problem ? it's something between gcc 3.4 and kernel 2.4.21 (or redhat ?) ? how to resolve this problem ?

jnengland77 wrote:
hmmm if you need the patch Con Kolivas has a patch... idk if this is the exact need.
1g lowmem?
Many machines now have exactly 1Gb ram and the standard memory split on i386 does not allow you to use more than 896Mb ram without enabling high memory for at least 4Gb. The problem is that this incurs an overhead whereas we can simply change this split with this patch to allow i386 architectures to use up to 1Gb ram without enabling highmem. This is configurable if HIGHMEM is disabled.
I also don't know if his old patches have the patch or if the current will work on the 2.4 kernel..
Just looked around and found the 2.4 are now Ick patchset and i don't see that... CK does have a server patch... If anything just get the 2.6 CK server patchset...   2.6 is stable, but how am I to say I've only used 2.6... Go with 2.6 ck server.
websites:  CK patchset 2.6
ICK 2.4 patchset
i really want a huge kernel space, and i can't find the 4G kernel space vm patch for 2.4 at these links
thanks anyway

Similar Messages

  • Kernel compile problems

    Right, I think I now knwo why I can't get my bttv DVB card working and need a quick kernel recompile to build in dvb-core.
    No problem with makemenuconfig
    However, when I start with make clean I get:
    make clean
    scripts/Makefile.clean:10: arch/i386/boot/Makefile: No such file or directory
    make[1]: *** No rule to make target `arch/i386/boot/Makefile'.  Stop.
    make: *** [archclean] Error 2
    Seems something is broke, or should I not be compiling from the source in /usr/src/linux-2.6.9-ARCH
    Any one got any thoughts?
    Could do with this working for my kids for Christmass <smile> <beg>

    Why do you use "make clean"? What does that do?
    I always compile my kernels the same way:
    - get the (latest) vanilla kernel from kernel.org
    - copy the .bz2 or .gz file to /usr/src
    - extract the file there
    - make a symlink called "linux" pointing to the directory of the new kernel
    - run "make menuconfig" and configure the kernel
    - run "make bzImage && make modules && make modules_install"
    - install the kernel to /boot and edit the bootloader.
    Maybe you need a vanilla kernel (standard kernel) tree instead of Arch's kernel tree.

  • Kernel compilation problem

    Hello there,
    I'm having some trouble compiling my own kernel. Hopefully this is a simple question.
    After downloading the kernel, I did `make defconfig`, and then I turned on some driver support, e.g. realtek wifi support. Then when I tried but build with make zImage, the system restarts the configuration. I have no idea why it would do that. Please help.

    Did you follow https://wiki.archlinux.org/index.php/Ke … raditional ?
    Have you tried https://wiki.archlinux.org/index.php/Ke … ild_System ?

  • Kernel compilation problems

    I just installed arch 0.7.2 on my laptop, but im having trouble compiling a new kernel.  Does anyone have any idea what this means:
    HOSTCC  scripts/basic/fixdep
    In file included from /usr/include/bits/posix1_lim.h:153,
                     from /usr/include/limits.h:145,
                     from /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/include/limits.h:122,
                     from /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/include/syslimits.h:7,
                     from /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/include/limits.h:11,
                     from scripts/basic/fixdep.c:113:
    /usr/include/bits/local_lim.h:36:26: error: linux/limits.h: No such file or directory
    In file included from /usr/include/sys/socket.h:35,
                     from /usr/include/netinet/in.h:24,
                     from /usr/include/arpa/inet.h:23,
                     from scripts/basic/fixdep.c:115:
    /usr/include/bits/socket.h:304:24: error: asm/socket.h: No such file or directory
    scripts/basic/fixdep.c: In function 'use_config':
    scripts/basic/fixdep.c:204: error: 'PATH_MAX' undeclared (first use in this function)
    scripts/basic/fixdep.c:204: error: (Each undeclared identifier is reported only once
    scripts/basic/fixdep.c:204: error: for each function it appears in.)
    scripts/basic/fixdep.c:204: warning: unused variable 's'
    scripts/basic/fixdep.c: In function 'parse_dep_file':
    scripts/basic/fixdep.c:300: error: 'PATH_MAX' undeclared (first use in this function)
    scripts/basic/fixdep.c:300: warning: unused variable 's'
    make[2]: *** [scripts/basic/fixdep] Error 1
    make[1]: *** [scripts_basic] Error 2
    make: *** [include/linux/autoconf.h] Error 2
    ==> ERROR: Build Failed.  Aborting...

    Yes, it's the 2.6.17.11 (and i checked 2.6.7.10).  This happens when ever I try make xconfig or make menuconfig and when i run makepkg with the pkgbuild from the custom ABS wiki.  It looks like i'm missing some files somewhere.

  • [solved]zen sources, kernel compilation problem

    scripts/kconfig/conf -s arch/x86/Kconfig
    CHK include/linux/version.h
    CHK include/linux/utsrelease.h
    SYMLINK include/asm -> include/asm-x86
    CALL scripts/checksyscalls.sh
    CHK include/linux/compile.h
    GZIP kernel/config_data.gz
    IKCFG kernel/config_data.h
    CC kernel/configs.o
    LD kernel/built-in.o
    LD vmlinux.o
    MODPOST vmlinux.o
    WARNING: vmlinux.o(.text+0x291): Section mismatch in reference from the function init_post() to the function .init.text:prepare_namespace()
    The function init_post() references
    the function __init prepare_namespace().
    This is often because init_post lacks a __init
    annotation or the annotation of prepare_namespace is wrong.
    WARNING: vmlinux.o(.cpuinit.data+0x0): Section mismatch in reference from the variable initial_code to the function .init.text:i386_start_kernel()
    The variable __cpuinitdata initial_code references
    a function __init i386_start_kernel().
    If i386_start_kernel is only used by initial_code then
    annotate i386_start_kernel with a matching annotation.
    GEN .version
    CHK include/linux/compile.h
    UPD include/linux/compile.h
    CC init/version.o
    LD init/built-in.o
    WARNING: init/built-in.o(.text+0x291): Section mismatch in reference from the function init_post() to the function .init.text:prepare_namespace()
    The function init_post() references
    the function __init prepare_namespace().
    This is often because init_post lacks a __init
    annotation or the annotation of prepare_namespace is wrong.
    LD .tmp_vmlinux1
    block/built-in.o: In function `vr_dispatch_requests':
    vr-iosched.c:(.text+0x14b8c): undefined reference to `__udivdi3'
    vr-iosched.c:(.text+0x14c71): undefined reference to `__udivdi3'
    make: *** [.tmp_vmlinux1] Error 1
    OMG, so close ... any ideas? maybe the zen-source.org forum is more appropriated?
    Last edited by hack.augusto (2008-12-23 20:14:36)

    How are you trying to build the zen kernel? Did you have an old copy of the zen sources around before you updated.
    I got the impression that some things have changed and it may be the reason why you are getting weird errors. Someone else had this same issue though and I don't have the foggiest for an answer.
    irc #zen-sources is a very helpful channel though

  • Kernel Compile how not to do it !!!! [FXx]

    EDIT I would like to say kernel compile problem was my fault.... I should have moved it then compiled 2.6.5-3 (gcc3.4) I will in future use /usr/src (improve my CLI skills)
    I am sorry for posting but this old boy gets in muddle sometimes & I like to think out loud.
    After several mugs of tea & reading posts I now have kernel 2.6.5-3 Xfee4.4 & nvidia working again (well for a couple of hours till 2.6.6 !!!)
    pacman -Af
    Many thanks again for all your help
    Mr Green :oops:

    If I use pacman -U I get a load of errors :
    usr/src/linux-2.6.5/sound/isa/Kconfig: exists in filesystem
    /usr/src/linux-2.6.5/sound/oss/Kconfig: exists in filesystem
    /usr/src/linux-2.6.5/sound/oss/dmasound/Kconfig: exists in filesystem
    /usr/src/linux-2.6.5/sound/parisc/Kconfig: exists in filesystem
    /usr/src/linux-2.6.5/sound/pci/Kconfig: exists in filesystem
    /usr/src/linux-2.6.5/sound/pcmcia/Kconfig: exists in filesystem
    /usr/src/linux-2.6.5/sound/ppc/Kconfig: exists in filesystem
    /usr/src/linux-2.6.5/sound/sparc/Kconfig: exists in filesystem
    /usr/src/linux-2.6.5/sound/usb/Kconfig: exists in filesystem
    Mr Green  :?

  • Custom kernel compilation with abs..

    Been trying out custom kernel compilation with abs, since i only know the regular make menuconfig style, thought that this would be a good thing to learn.
    here is my kernel pkgbuild (showing only the part that i changed):
    # Contributor: dibblethewrecker <dibblethewrecker>
    pkgname=kernel26
    pkgver=2.6.17.13
    pkgrel=1
    pkgdesc="The Linux Kernel 2.6.x.y and modules (IDE support), built with ... patchset"
    url="http://www.kernel.org"
    depends=('module-init-tools')
    install=kernel26.install
    ##### if you are using a single patch from a patchset you can add the name, without it's extention, below
    patch=2.6.18-rc6-mm2
    ##### add the names of any patches to this section, ensure you have the correct extentions!
    source=($patch.bz2 config ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-$pkgver.tar.bz2 )
    I want to install the 2.6.18-rc6-mm2, so i downloaded that patch and put it in the same folder as PKGBUILD.
    I copied kernel26.install and put it in the same folder as the PKGBUILD.
    when running makepkg it asks for a config file.. So i copied the config file in /var/abs/kernels/kernel26/. But this will build with an old config file.. how can i as when doing the manual way, do a make menuconfig and enter the settings i want for this kernel??
    thanks

    I'd say it does too, and I think the problem is here:
    jinn wrote:I copied kernel26.install and put it in the same folder as the PKGBUILD.
    Did you just copy the install script, or did you edit it to create an image with a unique name? The script is hardcoded to create an image called kernel26.img i.e. the image name required by the stock kernel, so if you ran it as it is, you have overwritten the images for your stock kernel with images for your new kernel.
    You might still be able to boot your new kernel with kernel26-fallback.img, but if not you will have to boot your stock kernel using the initrd image, which will have been unaffected.
    Once your system is running again, you need to regenerate the kernel26 images using mkinitcpio, and then you can start debugging the problem with your new kernel.
    Of course, if you've already edited kernel26.install for your new kernel, ignore the above, and I'll start again.

  • Kernel sources problem

    Hi again.
    I've tried last night to compile the "stock" kernel-2.6.18-ARCH provided with the distro (and updated to the latest package) so I can customize it the way I like it.  But I've run into a compilation problem after menuconfig. When I run make i get this error:
    make[1]: *** No rule to make target `/usr/src/linux-2.6.18-ARCH/init/Makefile'. Stop.
    make: *** [init] Error 2
    I don't know what's to be done. Maybe I've done something wrong or maybe I didn't do something that I should have done. ;-) Anyways.. I downloaded the vanilla 2.6.18.3 and compiled it. It works ok that way, too. But if this is a bug I just wanted to report it.

    I knew it should be my mistake. Thanks for clearing this out.
    Is your version of kernel a lot different than the vanilla kernel?
    Or is it ok to stick with the vanilla version without breaking anything?
    (except the video module for nvidia, which I'm building myself)

  • User Mode Linux -- Compiling problem

    Hi,
    I want to run the user mode linux for linux-2.6.17.6. When I try to compile the user mode linux I get this error:
    In file included from arch/um/include/os.h:13,
    from arch/um/drivers/fd.c:14:
    arch/um/include/kern_util.h:9:27: error: linux/threads.h: No such file or directory
    make[1]: *** [arch/um/drivers/fd.o] Error 1
    make: *** [arch/um/drivers] Error 2
    I was looking up a lot of time in google.
    My steps to compile it is:
    export ARCH=um
    make defconfig
    make
    If you have any suggestion, let me know.
    Bye.

    Using that option the kernel compiles smoothly. The problem here, is that I am not getting the kernel that I want. I am just building a normal kernel.
    Any suggestion, let me know
    Luis.

  • Kernel Compile error

    can someone look at http://members.aol.com/trekboy07/vmware.jpg I am getting kernel compile errors and i am doing everything in the FAQ.  what i do is i untar the file from the arch 4.0 cd into /usr/src/linux-2.4.20 and run make menuconfig take file from /usr/abs/base/kernel make some changes and replace it, and run "makepkg" i have done this in VMWare and on a Thinkpad 600 and get the same errors.
    thanks for the help

    It seems like you bumped into a little bug in the linux kernel (at least, that's what google says, see the top link at http://groups.google.com/groups?q=undef … htool_gset )
    I already sent a patch for this for 2.5 but I didn't know the problem
    also exists in 2.4. The following patch fixes it:
    --- linux-2.4.20-test/drivers/net/Makefile.old    2002-11-29 17:46:47.000000000 +0100
    +++ linux-2.4.20-test/drivers/net/Makefile    2002-11-29 17:47:22.000000000 +0100
    @@ -122,6 +122,7 @@
    obj-$(CONFIG_MAC8390) += daynaport.o 8390.o
    obj-$(CONFIG_APNE) += apne.o 8390.o
    obj-$(CONFIG_PCMCIA_PCNET) += 8390.o
    +obj-$(CONFIG_PCMCIA_SMC91C92) += mii.o
    obj-$(CONFIG_SHAPER) += shaper.o
    obj-$(CONFIG_SK_G16) += sk_g16.o
    obj-$(CONFIG_HP100) += hp100.o
    Zwane changed this driver to use the MII support library but he
    accidentially forgot that this requires mii.o.
    cu
    Adrian

  • Nigpib-linux driver compile problem

    I am running SUSE 9.0, and while trying to install nigpib-linux-0.8.6.tar.gz, I get the following compile error:
    Your kernel appears to be configured properly to build NI-GPIB for Linux.
    Do you want to proceed? [yn] y
    gcc -c -O2 -D__KERNEL__ -I/lib/modules/2.4.21-260-default/build/include -DMODULE -DMODVERSIONS -include /lib/modules/2.4.21-260-default/build/include/linux/modversions.h -D__GPIBDRIVER__ -o ib_linux-2.4.21-260-default.o ib_linux.c
    ib_linux.c:419:7: missing binary operator before token "("
    make: *** [ib_linux-2.4.21-260-default.o] Error 1
    Couldn't build driver.
    It has to do with the HZ definition.
    Thanks for any help anyone can give!

    dsb,
    Here is a link to a lengthy thread on this very problem. There appears to be a workaround or two mentioned in the post:
    Linux Driver Compiling Problem
    Let me know if the suggestions in that thread help out!
    Craig H.
    NI Applications Engineering

  • Re: [iPlanet-JATO] sp3 jsp compiler problem

    Weiguo,
    First, Matt is correct, the regular expression tool is perfect for general text
    substitution situations, and as a completely independent tool its use is not
    restricted to migration situations (or file types for that matter).
    Second, I sympathize with the unfortunate trouble you are experiencing due to
    Jasper's (perhaps more strict) compilation, but in what way did the iMT
    automated translation contribute to these inconsistencies that you cited?
    1. Changed the case of the tag attribute to be the same as what's
    defined in tld.
    example: changed OnClick to onClick
    The iMT does not generate any OnClick or onClick clauses per se. In a
    translation situation, the only way "OnClick" would have been introduced was if
    it had been part of the pre-existing project's "extraHTML" (which was written
    by the original customer and just passed through unchanged by the iMT) or if it
    was added manually by the post-migration developer.
    2. Removed attributes which are not defined in tld.
    example: escape attribute only defined in three tags
    but in some pages, it's used although it's not defined as an
    attribute
    of certain tags. The jasper compiler doesn't like it.Can you give soem examples? Is there a definite pattern? Again, this might be
    similar to the OnClick situation described above?
    3. In an end tag, there can't be any space.
    example: </content > doesn't work. </content> works.
    Again, the content tag would never have been generated by the iMT. There was no
    equivalent in the NetDynamics world, so any content tags in your code must have
    been introduced by your developers manually. Its a shame that jasper is so
    particular, but the iMT could not help you out here even if we wanted to. The
    constants that are used by the iMT are defined in
    com.iplanet.moko.jsp.convert.JspConversionConstants. From what I can see, the
    only situation of a closing tag with any space in it is
    public static final String CLOSE_EMPTY_ELEMENT = " />";
    But that should not cause the type of problem you are referring to.
    Mike
    ----- Original Message -----
    From: Matthew Stevens
    Sent: Thursday, September 06, 2001 10:16 AM
    Subject: RE: [iPlanet-JATO] sp3 jsp compiler problem
    Weiguo,
    Others will chime in for sure...I would highly recommend the Regex Tool from
    the iMT 1.1.1 for tackling this type of problem. Mike, Todd and myself have
    posted to the group (even recently) on directions and advantages of creating
    your own RULES (rules file) in XML for arbitary batch processing of source.
    matt
    -----Original Message-----
    From: weiguo.wang@b...
    [mailto:<a href="/group/SunONE-JATO/post?protectID=125056020108194190033029175101192165174144234026000079108238073194105057099246073154180137239239223019162">weiguo.wang@b...</a>]
    Sent: Thursday, September 06, 2001 12:25 PM
    Subject: [iPlanet-JATO] sp3 jsp compiler problem
    Matt/Mike/Todd,
    We are trying to migrate to sp3 right now, but have had a lot of
    issues with the new jasper compiler.
    The following workaround has been employed to solve the issues:
    1. Changed the case of the tag attribute to be the same as what's
    defined in tld.
    example: changed OnClick to onClick
    2. Removed attributes which are not defined in tld.
    example: escape attribute only defined in three tags
    but in some pages, it's used although it's not defined as an
    attribute
    of certain tags. The jasper compiler doesn't like it.
    3. In an end tag, there can't be any space.
    example: </content > doesn't work. </content> works.
    As I see it, we have two options to go about solving this problem:
    1. Write a script which will iterate through all the jsp files and
    call jspc on them. Fix the errors manually when jspc fails. Jspc will
    flag the line number where an error occurs.
    2. Write a utility which scans the jsp files and fix the errors when
    they are encountered. We should define what's an error and how to
    correct it. It's best if we combine this with solution 1 since we
    might miss an error condition.
    Actually, there might be another option, which is seeking help from
    you guys since you have better understanding of JATO and iAS. Can you
    do anything to help us?
    We would be happy to hear your thoughts.
    At last, I would like to suggest modifying the moko tool so that
    these rules are enforced and the generated JSPs work with the new
    compiler. This is for the benefit of any new migration projects.
    Thanks a lot.
    Weiguo
    [email protected]
    Choose from 1000s of job listings!
    [email protected]
    [Non-text portions of this message have been removed]

    Thanks a lot Matt and Mike for your prompt replies.
    I agree completely that iMT doesn't introduce the inconsistencies.
    About the three cases I mentioned, the third one happens only in
    manually created JSPs. So it has nothing to do with iMT. The first
    two are mainly due to the existing HTML code, as you rightly pointed
    out.
    The reason I made the suggestion is since we know that case 1 and 2
    won't pass the japser compiler in sp3, we have to do something about
    it. The best place to do this, in my mind, is iMT. Of course, there
    might be some twists that make it impossible or difficult to do this
    kind of case manipulation or attribute discard.
    Weiguo
    --- In iPlanet-JATO@y..., "Mike Frisino" <Michael.Frisino@S...> wrote:
    Weiguo,
    First, Matt is correct, the regular expression tool is perfect for general text substitution situations, and as a completely independent
    tool its use is not restricted to migration situations (or file types
    for that matter).
    >
    Second, I sympathize with the unfortunate trouble you are experiencing due to Jasper's (perhaps more strict) compilation, but
    in what way did the iMT automated translation contribute to these
    inconsistencies that you cited?
    >
    1. Changed the case of the tag attribute to be the same as what's
    defined in tld.
    example: changed OnClick to onClick
    The iMT does not generate any OnClick or onClick clauses per se. In a translation situation, the only way "OnClick" would have been
    introduced was if it had been part of the pre-existing
    project's "extraHTML" (which was written by the original customer and
    just passed through unchanged by the iMT) or if it was added manually
    by the post-migration developer.
    >
    2. Removed attributes which are not defined in tld.
    example: escape attribute only defined in three tags
    but in some pages, it's used although it's not defined as an
    attribute
    of certain tags. The jasper compiler doesn't like it.Can you give soem examples? Is there a definite pattern? Again, this might be similar to the OnClick situation described above?
    >
    >
    3. In an end tag, there can't be any space.
    example: </content > doesn't work. </content> works.
    Again, the content tag would never have been generated by the iMT. There was no equivalent in the NetDynamics world, so any content tags
    in your code must have been introduced by your developers manually.
    Its a shame that jasper is so particular, but the iMT could not help
    you out here even if we wanted to. The constants that are used by the
    iMT are defined in
    com.iplanet.moko.jsp.convert.JspConversionConstants. From what I can
    see, the only situation of a closing tag with any space in it is
    public static final String CLOSE_EMPTY_ELEMENT = " />";
    But that should not cause the type of problem you are referring to.
    Mike
    ----- Original Message -----
    From: Matthew Stevens
    Sent: Thursday, September 06, 2001 10:16 AM
    Subject: RE: [iPlanet-JATO] sp3 jsp compiler problem
    Weiguo,
    Others will chime in for sure...I would highly recommend the Regex Tool from
    the iMT 1.1.1 for tackling this type of problem. Mike, Todd and myself have
    posted to the group (even recently) on directions and advantages of creating
    your own RULES (rules file) in XML for arbitary batch processing of source.
    >
    matt
    -----Original Message-----
    From: weiguo.wang@b...
    [mailto:<a href="/group/SunONE-JATO/post?protectID=125056020108194190033029175101192165174048139046">weiguo.wang@b...</a>]
    Sent: Thursday, September 06, 2001 12:25 PM
    Subject: [iPlanet-JATO] sp3 jsp compiler problem
    Matt/Mike/Todd,
    We are trying to migrate to sp3 right now, but have had a lot of
    issues with the new jasper compiler.
    The following workaround has been employed to solve the issues:
    1. Changed the case of the tag attribute to be the same as
    what's
    defined in tld.
    example: changed OnClick to onClick
    2. Removed attributes which are not defined in tld.
    example: escape attribute only defined in three tags
    but in some pages, it's used although it's not defined as an
    attribute
    of certain tags. The jasper compiler doesn't like it.
    3. In an end tag, there can't be any space.
    example: </content > doesn't work. </content> works.
    As I see it, we have two options to go about solving this problem:
    >>
    1. Write a script which will iterate through all the jsp files and
    call jspc on them. Fix the errors manually when jspc fails. Jspc will
    flag the line number where an error occurs.
    2. Write a utility which scans the jsp files and fix the errors when
    they are encountered. We should define what's an error and how to
    correct it. It's best if we combine this with solution 1 since we
    might miss an error condition.
    Actually, there might be another option, which is seeking help from
    you guys since you have better understanding of JATO and iAS. Can you
    do anything to help us?
    We would be happy to hear your thoughts.
    At last, I would like to suggest modifying the moko tool so that
    these rules are enforced and the generated JSPs work with the new
    compiler. This is for the benefit of any new migration projects.
    Thanks a lot.
    Weiguo
    [email protected]
    Choose from 1000s of job listings!
    [email protected]
    Service.
    >
    >
    >
    [Non-text portions of this message have been removed]

  • Servlet Compilation Problem !

    Hi,
    I am just starting to learn servlets and I got problem in compiling them. I got compilation error in
    import javax.servlet.*;statement. Seems that the compiler cannot find the servlet package. I got J2EE 1.4 beta installed on my machine but there is no servlet.jar package. I am using J2SDK 1.4.1_02, J2EE 1.4 beta and Tomcat 4.1.24.
    Can anyone help me with my servlet compilation problem?
    Thanks in advance!
    Josh

    servlet.jar is here :
    <tomcatdir>\common\lib
    add it to your compiler classpath

  • Compilation problem in a JSP page

    Hi all,
    I'm trying to write a jsp page and some java stuff in it.
    It goes something like this -
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
    "http://www.w3.org/TR/html4/loose.dtd">
    <%@ page contentType="text/html;charset=windows-1255"%>
    <html>
      <head>
        <meta http-equiv="Content-Type" content="text/html; charset=windows-1255"/>
        <title>Michael</title>
      </head>
      <body>
    <%
              String strError="";
    %>
    </body>Now the problem is that I get compilation problem about the use in java -
    "String cannot be resolved to a type"
    I know for sure that in other computers it's work, the question is what I'm missing?
    I have Java VM installed and I've downloaded and installed the latest JDK, what else?
    thanks,
    Michael.

    Michael4488 wrote:
    BalusC wrote:
    Then you should be using JSTL/EL.I don't familiar with this technology, any way - Its work on one computer so in my understanding it should work on the other as well.It is not related to the actual problem. It was just a comment on your code. Using scriptlets is considered as bad practice.
    I understand that of course, but I don't use any configuration file or set any special parameters in my computer.
    What exactly does the compiler need in order to recognize the Java code in the JSP page? If i manually add the JAVA_HOME environment variable it will work?
    where should I refer it to? "..\Java\jre1.6.0_07\lib" will do?It must point to the root installation directory of the JDK (thus not the JRE!).

  • Kernel Label problem for SOL MAN 4.0

    Hi
    When was installing a Unicode SolMan 4.0 on Win 2003 SQL server 2005.
    I have downloaded a following CD for Kernel -
    51031778_11 NW 2004s SR1 UC-Kernel 7.00 Windows Server on IA32 32bit
    When I give the LABEL.ASC for kernel, it does not accept it and give me following error -
    You entered: E:/nw04s/kernel/DVD_NW_2004s_SR1_Kernel_Windows__LNX_X86/LABEL.ASC
    Found the label SAP:AKK:700:DVD_KERNEL:SAP Kernel 700:D51031778 but need label
    SAP:AKK:700:KERNEL:.WINDOWS_I386:
    I tried all these option from the below link, but it did not work
    Kernel Label problem...
    Does any one have solution for that?
    I appreciate your help
    regards
    kamal

    Hi udo lang,
    I have downloaded the Kernel file 51031778_3 NW 2004s SR1 Kernel 7.00 Windows Server on IA32 32bit today. I will try to fix the problem by using this kernel.
    I also got reply from Sap that solution for this issue is:
    This is most unusual. Due to the currently running RampUp the
    DVD's could have been updated.
    I suggest that you try the following,
    Download both the Unicode and NonUnicode Kernel files from the
    SAP Service Market Place.
    The Kernel DVD 51031778 contains the Kernel for Unicode and for Non-
    Unicode, as you wrote, in directory "", label:
    "SAP:AKK:700:KERNEL::WINDOWS_X86_64:"
    Please check if you start Unicode Installation. Due to an incorrect
    procedure sapinst requireds both Kernel-CD.
    With the next release will be it correct. If you start a Unicode
    installation it will be a unicode.
    51031792_5 NW 2004s SR1 UC-Kernel 7.00 AIX 64bit
    51031792_1 NW 2004s SR1 Kernel 7.00 AIX 64bit
    Etract them to one directory, like:
    <downloadDIR>/
    kernel/
    KN_WINDOWS_I386/
    KU_WINDOWS_I386/
    CDLABEL.ASC
    LABEL.ASC
    LABELIDX.ASC
    When you ware asked for the kernel DVD, please enter
    <downloadDIR>/kernel
    SAPinst should take the right kernel version for the installation
    automatically.
    You may additionally refer to the below note for reference.
    921593 Inst. SAP NetWeaver 2004s SR1 on UNIX
    If the problem is resolved i will let you know. Thanks for your assistance
    regards
    Kamal

Maybe you are looking for