SCIENTIFIC-LINUX-USERS Archives

May 2015

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Vladimir Mosgalin <[log in to unmask]>
Reply To:
Vladimir Mosgalin <[log in to unmask]>
Date:
Mon, 25 May 2015 15:25:38 +0300
Content-Type:
text/plain
Parts/Attachments:
text/plain (31 lines)
Hi Tom H!

 On 2015.05.25 at 08:09:51 -0400, Tom H wrote next:

> > linux32 rpmbuild --rebuild pangox-compat-0.0.2-2.el7.src.rpm
> >
> > I have been doing a lot of the linux32 lately, but I am not
> > all the sure of exactly what it does.
> 
> "linux32" short for "setarch linux32".

To be more precise, it affects rpm macros so that 32-bit libraries are
picked by default and compiler options are changed to create 32-bit
code.

Doesn't work in all cases, really, which is why for building more
complicated packages 32-bit chroot - managed by mock - is required. This
ensures clean 32-bit environment without 64-bit packages. In fact, it's
a very good idea to always use one instead of "linux32 rpmbuild",
because just changing macros leads to invisible at first sight but
existing packaging problems (wrong paths, etc). Configuration/build
systems of some packages just aren't tricked by "linux32" alone to
create 32-bit build.

All 32-bit packages in 64-bit distribution (SL6, SL7) are created in
chroots with clean 32-bit environments, not with "linux32" hack :)

-- 

Vladimir

ATOM RSS1 RSS2