Sponsored Content
Full Discussion: SUSE Linux Enterprise 12
Special Forums UNIX and Linux Applications SUSE Linux Enterprise 12 Post 302933789 by drl on Monday 2nd of February 2015 09:54:52 AM
Old 02-02-2015
Hi.

Using zypper to check for gcc 32-bit packages yields:
Code:
  (opensuse: using zypper.)
  | gcc-32bit                             | The system GNU C Compiler                                             | package
  | gcc-c++-32bit                         | The system GNU C++ Compiler                                           | package
  | gcc-fortran-32bit                     | The system GNU Fortran Compiler                                       | package
  | gcc-gij-32bit                         | The system GNU Java bytecode interpreter                              | package
  | gcc-objc-32bit                        | The system GNU Objective C Compiler                                   | package
  | gcc33-32bit                           | The GNU C Compiler 32bit support                                      | package
  | gcc33-fortran-32bit                   | The GNU Fortran Compiler and Support Files                            | package
  | gcc33-objc-32bit                      | GNU Objective C Compiler                                              | package
  | gcc47-32bit                           | The GNU C Compiler 32bit support                                      | package
  | gcc47-ada-32bit                       | GNU Ada95 Compiler Based on GCC (GNAT)                                | package
  | gcc47-fortran-32bit                   | The GNU Fortran Compiler and Support Files                            | package
  | gcc47-gij-32bit                       | Java Bytecode Interpreter for gcc                                     | package
  | gcc47-objc-32bit                      | GNU Objective C Compiler                                              | package
i | libgcc_s1-32bit                       | C compiler runtime library                                            | package

For a system like:
Code:
OS, ker|rel, machine: Linux, 3.7.10-1.16-desktop, x86_64
Distribution        : openSUSE 12.3 (Dartmouth)

Best wishes ... cheers, drl
 

5 More Discussions You Might Find Interesting

1. SuSE

How to configure Suse Enterprise Linux 9.0 for sending mails to smtp server...???

Hi All, I have a system running with Suse Enterprise Linux 9.0. xyz# uname -a Linux xyz 2.4.21-291-smp #1 SMP Tue May 24 14:07:45 UTC 2005 i686 unknown I would like to configure postfix on this system for sending mails as a root user using "mail" command to smtp server (Windows System)... (5 Replies)
Discussion started by: jumadhiya
5 Replies

2. SuSE

LKCD for suse linux enterprise server 8

Hi, I have installed LKCD using lkcdutils pakage through Yast install and remove applications. I have used enterprise server cd for installation. But I did not found any service of lkcd like /etc/init.d/boo.lkcd there. if we dont have this servers lkcd dump can not be saved at dump... (0 Replies)
Discussion started by: bryanabhay
0 Replies

3. UNIX Desktop Questions & Answers

Suse Linux enterprise 10 - booting problem

Hi, It was happened to close my laptop without proper shutdown due to power failure with USB device connected to it. (removed the USB after shut down) After this incident, I was not able to boot my suse linux OS. Initial study reveals that the device is not unmounted properly and shows... (2 Replies)
Discussion started by: Prabhu V
2 Replies

4. UNIX for Dummies Questions & Answers

SunOS5.10 and SuSe Linux Enterprise

OK, I've been thrown into an issue at my company where the security folks want password aging turned on for their limited NIS environment. The config is a SunOS5.10 (Solaris 10) Master with several slaves and several SuSe Enterprise Server 11 Clients. What I'm looking to understand is... (0 Replies)
Discussion started by: rzrv15
0 Replies

5. SuSE

Suse enterprise server installation help

hello All, good day to you. could you tell me is there any way I can download SUSE lunux enterprise server trail version ? I want to install sap application over it. thanks in advance. (1 Reply)
Discussion started by: Leaner_963
1 Replies
build(1)						      General Commands Manual							  build(1)

NAME
build - build SuSE Linux RPMs in a chroot environment SYNOPSIS
build [--clean|--no-init] [--rpms path1:path2:...] [--arch arch1:arch2:...] [--root buildroot] [specfile|srcrpm] build --help build --verify DESCRIPTION
build is a tool to build SuSE Linux RPMs in a safe and clean way. build will install a minimal SuSE Linux as build system into some direc- tory and will chroot to this system to compile the package. This way you don't risk to corrupt your working system (due to a broken spec file for example), even if the package does not use BuildRoot. build searches the spec file for a BuildRequires: line; if such a line is found, all the specified rpms are installed. Otherwise a selec- tion of default packages are used. Note that build doesn't automatically resolve missing dependencies, so the specified rpms have to be sufficient for the build. If a spec file is specified on the command line, build will use this file and all other files in the directory for building the package. If a srcrpm is specified, build automatically unpacks it for the build. If neither is given, build will use all the specfiles in the current directory. OPTIONS
--clean remove the build system and reinitialize it from scratch. --no-init skip the build system initialization and start with build immediately. --list-state list rpms that would be used to create a fresh build root. Does not create the build root or perform a build. --rpms path1:path2:path3... Where build can find the SuSE Linux RPMs needed to create the build system. This option overrides the BUILD_RPMS environment vari- able. --arch arch1:arch2:arch3... What architectures to select from the RPMs. build automatically sets this to a sensible value for your host if you don't specify this option. --root buildroot Specifies where the build system is set up. Overrides the BUILD_ROOT enviroment variable. --useusedforbuild Tell build not to do dependency expansion, but to extract the list of packages to install from "# usedforbuild" lines or, if none are found, from all "BuildRequires" lines. This option is useful if you want to re-build a package from a srcrpm with exactly the same packages used for the srcrpm build. --norootforbuild --help Print a short help text. --verify verify the files in an existing build system. .spec FILE OPTIONS The build command interprets some special control comments in the specfile: # norootforbuild # needsrootforbuild build uses either user root or user abuild in the build system to do the build. For non-SUSE distros as well as since SUSE 10.2, the default build user is abuild. For 10.2 and before, the default build user is root. These two flags in the spec file allow to deviate from the defaults and force-set the build user to abuild and root (for # norootforbuild and # needsrootforbuild respec- tively. # needsbinariesforbuild provide the binary rpms that have been used to set up the build root in /.build.binaries within the build root. ENVIRONMENT
BUILD_ROOT The directory where build should install the chrooted build system. "/var/tmp/build-root" is used by default. BUILD_RPMS Where build can find the SuSE Linux RPMs. build needs them to create the build system. "/media/dvd/suse" is the default value which will do the trick if you have the SuSE Linux DVD mounted. BUILD_RPM_BUILD_STAGE The rpm build stage (-ba, -bb, ...). This is just passed through to rpm, check the rpm manpage for a complete list and descrip- tions. "-ba" is the default. You can use this to add more options to RPM. SEE ALSO
rpm(1), Maximum RPM: http://www.rpm.org/max-rpm/ cross distribution packaging: http://en.opensuse.org/Build_Service/cross_distribution_package_how_to SUSE packaging standards and guidelines: http://en.opensuse.org/Packaging (c) 1997-2008 SuSE Linux AG Nuernberg, Germany build(1)
All times are GMT -4. The time now is 07:22 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy