Version 11.2.6 (2012-02-03)
These release notes are generic for all SDK 11 based products.
The SUSE Linux Enterprise Software Development Kit (SDK) can be used for SUSE Linux Enterprise Server (SLES) and SUSE Linux Enterprise Desktop (SLED).
Several packages that are either only on SLES or only on SLED, but needed for the SDK, have been added to the SDK for convenience. The presence of those packages on the SDK does not indicate any support or maintenance entitlement. If you only have a support contract for SLED you are not automatically entitled to support for SLES packages on the SDK and vice versa.
You should be able to re-build any package on SLES or SLED with the SDK DVDs. If you are still using the deprecated CDs, please download the DVDs from http://developer.novell.com/wiki/index.php?title=SLES_SDK.
If you are missing packages on the DVD, please file a bug in the Novell Bugzilla system (http://bugzilla.novell.com). You may also find additional unsupported packages on openSUSE (http://www.opensuse.org).
Note: For various technical reasons not all SDK packages are available on all SLES hardware architectures.
The SDK does not come with a maintenance or support entitlement. From time to time SUSE may release package updates and security fixes online.
If you add the SDK during installation, online update sources for the SDK are added when you register your product.
If you have added the SDK later, please run the Novell Customer Center Configuration in YaST2. This will add the SDK update sources to your configuration. You will not have to re-enter your registration data for this.
The SDK contains the development packages for more than one product. Therefore it is not possible to install every development package on every product. In other words: Not all SDK packages are installable on all products because of the differences in the package lists of the base products.
The system compiler (based on GCC 4.3) does not support, or only suboptimally so, several newer architectures amongst them new processors for the zEnterprise platform.
For the sake of stability and maximum compatibility the system compiler based on GCC 4.3 remains in place, and we update the alternate compiler as part of the SDK to GCC 4.6, the newest upstream release.
Need to build a 32-bit JIT agent library using OProfile's JIT support.
A 32-bit JIT support library from OProfile is provided with this release in the oprofile-devel-32bit package.
The kiwi main package itself does not contain all software components, which could be necessary to build the specified image. For building such an image, some of the packages listed below are required.
To build an image using kiwi, make sure to have either the online SDK repository or the media available so that kiwi can download the required packages.
Note: Depending on the type of image you are building, only some of these packages may be required. All packages listed above are included either on SLES or SDK media and their repsective online repositories.
While not bundling the package may involve additional steps when building an image, it brings the benefit of kiwi always using the most recent version of the packages. Additionally, it improves the size of the kiwi package significantly.
In the past, building kernel module packages for different RPM-based Enterprise Linux distributions has been a challenge: There has been no way to use a single .spec file to build distro-specific kernel module RPMs.
Now, through the Linux Foundation Driver Backport Workgroup, key RPM-based distribution vendors have collaborated to support a standard .spec file format and RPM macros for building kernel module packages. Packagers will now be able to use a single .spec file to create distro-specific binary kernel module RPMs. An example kernel module package build structure, complete with the new standard .spec file and sampledriver source code, is available on the SUSE Linux Enteprise SDK 11 SP 1 in the package "samplekmp-source".
Example: libpcap0-devel-32bit package was available in SDK 10, but is missing from SDK 11
SUSE supports running 32bit applications on 64bit architectures; respective runtime libraries are provided with SLES 11 and fully supported. With SLE 10 we also provided 32bit devel packages on the 64bit SDK. Having 32bit devel packages and 64bit devel packages installed in parallel may lead to side-effects during the build process. Thus with SLE 11 we startet to remove some of (but not yet all) the 32bit devel packages from the 64bit SDK.
With the development tools provided in the SDK 11, customers and partners have two options to build 32bit packages in a 64bit environment (see below). Beyond that, SUSE's appliance offerings provide powerful environments for software building, packaging and delivery.
Use the "build" tool, which creates a chroot environment for building packages.
The SDK contains the software used for the openSUSE buildservice. Here the abstraction is provided by virtualization.
The following packages were removed with the release of Software Development Kit 11 Service Pack 2:
On the top level of the first CD you will find a very detailed ChangeLog file. Please, also read the READMEs on the CD.
In case of encountering a bug, please report it through your support contact.
Your SUSE Linux Enterprise Team
SUSE makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses. Please refer to http://www.novell.com/info/exports/ for more information on exporting SUSE software. SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright (c) 2010, 2011, 2012 SUSE. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.
SUSE has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.novell.com/company/legal/patents/ and one or more additional patents or pending patent applications in the U.S. and other countries.
For SUSE trademarks, see Novell Trademark ad Service Mark list (http://www.novell.com/company/legal/trademarks/tmlist.html). All third-party trademarks are the property of their respective owners.