Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Adding SDK Build on Kernel Source Build Post 302737339 by h0ujun on Wednesday 28th of November 2012 08:53:39 PM
Old 11-28-2012
Adding SDK Build on Kernel Source Build

Hi,

So I downloaded this kernel source and was able to build it successfully.
But I want to add this SDK source code inside, can anyone help me how to do this? Note that the SDK source can be built by itself.

I added the SDK in the main Makefile:
Code:
init-y          := init/
#added SDK
drivers-y       := drivers/ sound/ firmware/ newSDK/
net-y           := net/
libs-y          := lib/
core-y          := usr/

Is this correct?

Also in the newSDK Makefile, the BASEDIR is set to '.' but when it starts building the SDK, it reports that it cannot see the necessary files that is set on BASEDIR.


Thanks!
 

10 More Discussions You Might Find Interesting

1. BSD

build kernel ,question?

# cd /usr/src/sys/i386/conf # cp GENERIC LOVEPP # cd /usr/src # make buildkernel KERNCONF=LOVEPP make:don't know how to make buildkernel. Stop Any suggestions? (I am using Freebsd4.8) (2 Replies)
Discussion started by: sheep
2 Replies

2. SCO

Installation error for Kernel Re-build

Hi All, While installing a Service Pack on my Unix Solaris machine, i got the following error: UX:acomp: ERROR: "space.c", line 16: undefined symbol: CHROOT_SECURITY UX:acomp: ERROR: "space.c", line 16: non-constant initializer: op "NAME" UX:idmkunix: ERROR: Compile/link of 'Driver_atup.o... (9 Replies)
Discussion started by: am_yadav
9 Replies

3. UNIX Benchmarks

FreeBSD 7.2 build kernel benchmarks

Just for fun: CPU/Speed: 2x AMD Opteron Model 2384 (2.7GHz/512KB) quad core processor Ram: 4 x2GB ECC DDR2-667 single rank memory in RAID 0 mode (strip 128KB, Read Caching enabled, Write Caching disabled) with 2 HDD, CPUTYPE=opteron, CFLAGS= -O2 -fno-strict-aliasing -pipe, CXXFLAGS+=... (0 Replies)
Discussion started by: Success_Tree
0 Replies

4. Red Hat

build a repository

Hi, i'll explain my problem in few words: i have to create a repository with mrepo on a RH. I see many procedures on internet and even in linux mag, but there isn't any case where the iso and rpm deposit aren't placed on the repository but on a remote system (a NetApp filer in my case). So... (0 Replies)
Discussion started by: nicnictout
0 Replies

5. Solaris

ffmpeg build - Sorais 10 x86: source code?

Hi I am trying to build ffmpeg on Solaris 10 from source as per the main downloads page on the ffmpeg site, howver I am running into various errors. I then came across this posting chrismiles: Building ffmpeg on Solaris 10 after some judicious googling. Unfortunately, the patch does not... (0 Replies)
Discussion started by: skewbie
0 Replies

6. Linux

Create a bootable PXE image from build kernel source code

Hi, Can i just ask how I can create a bootable PXE image from the built kernel source. What files do I need to get? Thanks! (1 Reply)
Discussion started by: h0ujun
1 Replies

7. Shell Programming and Scripting

Build.xml invocation by Build Script

Hi I have a build.xml file and I can run it on Windows via cmd. Now I want to write a script to invoke the same. Is there a way to do this? (1 Reply)
Discussion started by: ankur328
1 Replies

8. Shell Programming and Scripting

Build using scons

I have a tree structure as follows: /vik/build/sc/botoh.sc /vik/lib/endian.f /vik/utils/botoh.f Then I run the build script as cd vik/build/sc scons -f botoh.sc The above shows that the SConstruct botoh.sc is down a few levels, and it may be easiest to have the main... (6 Replies)
Discussion started by: kristinu
6 Replies

9. Linux Benchmarks

Newer PC build.

Just decided to run the benchmark for the heck of it. -Version- Dist: Debian GNU/Linux 8.5 CPU/Speed: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz RAM: DDR4 DRAM 64 GB 3000 MHz CMK64GX4M4B3000C15 MB: Maximus VIII Ranger Bus: 8 sata, 1 M.2 Socket 3 Cache: L2=4 x 256KB, L3=8 MB shared... (1 Reply)
Discussion started by: bajanine
1 Replies

10. Windows & DOS: Issues & Discussions

(VS 2008) New build config looking files from other folder build config

Hi Team, My new build configuration always looking for the files from the build where i copied from. please help me to resolve this. I am using Visual studio 2008.It has Qt 4.8. plugins,qml,C++ development I created new debug_new build configuration with additional preprocessor from the... (1 Reply)
Discussion started by: SA_Palani
1 Replies
PERLNETWARE(1)						 Perl Programmers Reference Guide					    PERLNETWARE(1)

NAME
perlnetware - Perl for NetWare DESCRIPTION
This file gives instructions for building Perl 5.7 and above, and also Perl modules for NetWare. Before you start, you may want to read the README file found in the top level directory into which the Perl source code distribution was extracted. Make sure you read and understand the terms under which the software is being distributed. BUILD
This section describes the steps to be performed to build a Perl NLM and other associated NLMs. Tools & SDK The build requires CodeWarrior compiler and linker. In addition, the "NetWare SDK", "NLM & NetWare Libraries for C" and "NetWare Server Protocol Libraries for C", all available at <http://developer.novell.com/wiki/index.php/Category:Novell_Developer_Kit>, are required. Microsoft Visual C++ version 4.2 or later is also required. Setup The build process is dependent on the location of the NetWare SDK. Once the Tools & SDK are installed, the build environment has to be setup. The following batch files setup the environment. SetNWBld.bat The Execution of this file takes 2 parameters as input. The first being the NetWare SDK path, second being the path for CodeWarrior Compiler & tools. Execution of this file sets these paths and also sets the build type to Release by default. Buildtype.bat This is used to set the build type to debug or release. Change the build type only after executing SetNWBld.bat Example: 1. Typing "buildtype d on" at the command prompt causes the buildtype to be set to Debug type with D2 flag set. 2. Typing "buildtype d off" or "buildtype d" at the command prompt causes the buildtype to be set to Debug type with D1 flag set. 3. Typing "buildtype r" at the command prompt sets it to Release Build type. Make The make process runs only under WinNT shell. The NetWare makefile is located under the NetWare folder. This makes use of miniperl.exe to run some of the Perl scripts. To create miniperl.exe, first set the required paths for Visual c++ compiler (specify vcvars32 location) at the command prompt. Then run nmake from win32 folder through WinNT command prompt. The build process can be stopped after miniperl.exe is created. Then run nmake from NetWare folder through WinNT command prompt. Currently the following two build types are tested on NetWare: o USE_MULTI, USE_ITHREADS & USE_IMP_SYS defined o USE_MULTI & USE_IMP_SYS defined and USE_ITHREADS not defined Interpreter Once miniperl.exe creation is over, run nmake from the NetWare folder. This will build the Perl interpreter for NetWare as perl.nlm. This is copied under the Release folder if you are doing a release build, else will be copied under Debug folder for debug builds. Extensions The make process also creates the Perl extensions as <Extension.nlm> INSTALL
To install NetWare Perl onto a NetWare server, first map the Sys volume of a NetWare server to i:. This is because the makefile by default sets the drive letter to i:. Type nmake nwinstall from NetWare folder on a WinNT command prompt. This will copy the binaries and module files onto the NetWare server under sys:Perl folder. The Perl interpreter, perl.nlm, is copied under sys:perlsystem folder. Copy this to sys:system folder. Example: At the command prompt Type "nmake nwinstall". This will install NetWare Perl on the NetWare Server. Similarly, if you type "nmake install", this will cause the binaries to be installed on the local machine. (Typically under the c:perl folder) BUILD NEW EXTENSIONS
To build extensions other than standard extensions, NetWare Perl has to be installed on Windows along with Windows Perl. The Perl for Windows can be either downloaded from the CPAN site and built using the sources, or the binaries can be directly downloaded from the ActiveState site. Installation can be done by invoking nmake install from the NetWare folder on a WinNT command prompt after building NetWare Perl by following steps given above. This will copy all the *.pm files and other required files. Documentation files are not copied. Thus one must first install Windows Perl, Then install NetWare Perl. Once this is done, do the following to build any extension: o Change to the extension directory where its source files are present. o Run the following command at the command prompt: perl -II<path to NetWare lib dir> -II<path to lib> Makefile.pl Example: perl -Ic:/perl/5.6.1/lib/NetWare-x86-multi-thread -Ic:perl5.6.1lib MakeFile.pl or perl -Ic:/perl/5.8.0/lib/NetWare-x86-multi-thread -Ic:perl5.8.0lib MakeFile.pl o nmake o nmake install Install will copy the files into the Windows machine where NetWare Perl is installed and these files may have to be copied to the NetWare server manually. Alternatively, pass INSTALLSITELIB=i:perllib as an input to makefile.pl above. Here i: is the mapped drive to the sys: volume of the server where Perl on NetWare is installed. Now typing nmake install, will copy the files onto the NetWare server. Example: You can execute the following on the command prompt. perl -Ic:/perl/5.6.1/lib/NetWare-x86-multi-thread -Ic:perl5.6.1lib MakeFile.pl INSTALLSITELIB=i:perllib or perl -Ic:/perl/5.8.0/lib/NetWare-x86-multi-thread -Ic:perl5.8.0lib MakeFile.pl INSTALLSITELIB=i:perllib o Note: Some modules downloaded from CPAN may require NetWare related API in order to build on NetWare. Other modules may however build smoothly with or without minor changes depending on the type of module. ACKNOWLEDGEMENTS
The makefile for Win32 is used as a reference to create the makefile for NetWare. Also, the make process for NetWare port uses miniperl.exe to run scripts during the make and installation process. AUTHORS
Anantha Kesari H Y (hyanantha@novell.com) Aditya C (caditya@novell.com) DATE
o Created - 18 Jan 2001 o Modified - 25 June 2001 o Modified - 13 July 2001 o Modified - 28 May 2002 perl v5.16.3 2013-03-04 PERLNETWARE(1)
All times are GMT -4. The time now is 07:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy