Building 32bit wine from source

Anyone know if it is possible to build 32bit wine from source on 64bit arch? There are patches I would like to apply to wine but currently the only way I can install wine on 64bit arch is via bin32-wine which uses the 32bit binary.
Other distributions this is very easy. It is just a matter of installing all of the 32bit libraries as well as the 64 bit libraries. I used to do this all the time with debian. Now with arch, even installing all of the 32bit libraries it does not seem to work at all. Has anyone been able to do this?
If someone can point me in the right direction on how to get 32bit wine to compile, i will try to make and maintain a package on the AUR which will do this.

I needed this a couple of months back but I couldn't find any documentation on this, other than building a chroot. Which seemed too much for me. So instead I booted ubuntu ;(
But it seems easy now: http://wiki.archlinux.org/index.php/Arc … _Arch64.3F

Similar Messages

How to build a package from sources

hi all,
Can someone please give some advices regarding making binaries from sources. I have found that a lot of programs on Snow Leopard can be also run in terminal and are in source form and need to be build. I have installed Xcode already and I have some programming skills as well such as using MinGW (GNU GCC) and VS EE on WinXP. I have never done anything in any UNIX-like system and I know sources need to be just compiled.
Please, give me a link if you have any =)
Regards.

I think you have done something in a UNIX-like system. MinGW is designed to provide a UNIX-line build system with GCC for Windows. Now, however, you have the real thing.
In most cases, all you need to do is extract the source tarbar into a directory (or checkout via CVS or SVN). Go into that directory with the Terminal and type "configure" and, if that goes well, "make", and if that looks good "sudo make install".

Building GNOME apps from source

Hi.
I just installed Arch on a virtual machine, and I'm trying to build a GNOME app from source code. In other distros this is very easy to do - you just install a package called gnome-devel and it provides you with the necessary header files and tools to build most source code.
What is the Arch way? I couldn't find a package named gnome-devel and couldn't see anything about it in the wiki. I installed base-devel.
Thanks.

udi wrote:
Hi.
I just installed Arch on a virtual machine, and I'm trying to build a GNOME app from source code. In other distros this is very easy to do - you just install a package called gnome-devel and it provides you with the necessary header files and tools to build most source code.
What is the Arch way? I couldn't find a package named gnome-devel and couldn't see anything about it in the wiki. I installed base-devel.
Thanks.
If I misunderstood you correctly:
Arch does not split out headers and so on into -dev packages. All of them are in the main packages. (with some rare exceptions)

Build Solaris 8 from source only?

I just downloaded the source for Solaris 8 and wanted to build the system from it, only it appears I need the Operating Environment to perform this and the OE is no longer available for download. Is there anyway to build the system with the source alone?

Yuechen wrote:
Hi
I understand that my requirement is kinda weird. However, I really wonder whether it is possible sometimes.
I have built ssh successfully both on solaris 8 and solaris 10. Now the problem is the binary built on solaris 8 can work on solaris 10, but the binary built on solaris 10 can not work on solaris 8.That is expected. Binaries should have forward compatibility and run on later versions of the OS.
Build on 8, run on 8 through 10.
Darren

[SOLVED] Problem whilst trying to build kernel26-ck from source

I've spent some time reading about kernel patch sets, and after some research and valuable info from the Arch community, I've decided that the ck patchset is most appropriate for my system, however, I receive the following error after issuing a mkpkg -sc command:
==> Validating source files with md5sums...
linux-2.6.36.tar.bz2 ... Passed
patch-2.6.36-2-ARCH.bz2 ... Passed
config ... Passed
config.x86_64 ... Passed
kernel26.preset ... Passed
patch-2.6.36-ck2.bz2 ... Passed
0001-bfq_iosched-block-prepare_IO_context_code-v1-2.6.36.patch ... Passed
0002-bfq_iosched-block-add-cgroups-kconfig-and-build-bits-for-BFQ-v1-2.6.36.patch ... Passed
0003-bfq_iosched-block-introduce_BFQ-v1-2.6.36.patch ... Passed
==> Extracting Sources...
-> Extracting linux-2.6.36.tar.bz2 with bsdtar
-> Extracting patch-2.6.36-2-ARCH.bz2 with bzip2
-> Extracting patch-2.6.36-ck2.bz2 with bzip2
==> Starting build()...
==> Patching source with-ARCH patches
patching file drivers/video/logo/logo_linux_clut224.ppm
patching file drivers/video/logo/logo_linux_mono.pbm
patching file drivers/video/logo/logo_linux_vga16.ppm
patching file fs/file_table.c
patching file fs/namei.c
patching file fs/namespace.c
patching file fs/notify/group.c
patching file fs/notify/mark.c
patching file fs/open.c
patching file fs/splice.c
patching file fs/statfs.c
patching file include/linux/fs.h
patching file include/linux/namei.h
patching file include/linux/splice.h
patching file security/commoncap.c
patching file security/device_cgroup.c
patching file security/security.c
==> Patching source with BFQ patches
patching file block/Kconfig.iosched
patching file block/blk-ioc.c
patching file block/cfq-iosched.c
patching file fs/ioprio.c
patching file include/linux/iocontext.h
patching file block/Makefile
patching file include/linux/cgroup_subsys.h
patching file block/bfq-cgroup.c
patching file block/bfq-ioc.c
patching file block/bfq-iosched.c
patching file block/bfq-sched.c
patching file block/bfq.h
==> Patching source with ck1 patch set
patching file arch/powerpc/platforms/cell/spufs/sched.c
patching file Documentation/scheduler/sched-BFS.txt
patching file Documentation/sysctl/kernel.txt
patching file fs/proc/base.c
patching file include/linux/init_task.h
patching file include/linux/ioprio.h
patching file include/linux/sched.h
patching file init/Kconfig
patching file init/main.c
patching file kernel/delayacct.c
patching file kernel/exit.c
patching file kernel/kthread.c
patching file kernel/posix-cpu-timers.c
patching file kernel/sched_bfs.c
patching file kernel/sched.c
patching file kernel/sysctl.c
patching file lib/Kconfig.debug
patching file mm/vmscan.c
patching file include/linux/swap.h
patching file mm/memory.c
patching file mm/swapfile.c
patching file include/linux/mmzone.h
patching file include/linux/mm_inline.h
patching file mm/filemap.c
patching file mm/swap.c
patching file mm/page-writeback.c
patching file arch/x86/Kconfig
patching file kernel/Kconfig.hz
patching file arch/x86/kernel/cpu/proc.c
patching file arch/x86/kernel/smpboot.c
patching file include/linux/nfsd/stats.h
patching file include/net/inet_timewait_sock.h
patching file init/calibrate.c
patching file kernel/Kconfig.preempt
patching file drivers/cpufreq/cpufreq_ondemand.c
patching file Makefile
==> Running make mrproper to clean source tree
==> Running make prepare for you to enable patched options of your choosing
HOSTCC scripts/basic/fixdep
/bin/sh: scripts/basic/fixdep: Permission denied
make[2]: *** [scripts/basic/fixdep] Error 1
make[1]: *** [scripts_basic] Error 2
make: *** No rule to make target `include/config/auto.conf', needed by `include/config/kernel.release'. Stop.
Aborting...
[taylor-unix@Legion kernel26-ck]$
Issuing a mkpkg command '--asroot' fails to make any difference whatsoever.
Am I missing something here?
Last edited by edward.taylor89 (2010-11-09 22:38:29)

SOLVED!
The trick was to remove 'noexec' along the mount options for /home from fstab.
Last edited by edward.taylor89 (2010-11-09 17:22:01)

Building Flex swcs from source

I have found a number of bugs in the DataGrid,
ArrayCollection, LinearAxis etc that I would like to fix. Since the
framework source is included in the SDK, it seems pretty
straighforward to how to do this but. I would like to know which
flex packages are in which framework swc. What is the mapping from
mx.* space to flex.swc, charts.swc, framework.swc etc. I of course
will report these bugs and submit my fixes too.

This post may be outdated, but here is the solution:
First download the source from svn:
http://opensource.adobe.com/wiki/display/flexsdk/Get+Source+Code
Then import and compile it:
http://opensource.adobe.com/wiki/display/flexsdk/Build+and+Test
I did this today and it worked fine for me, so don't hesitate if you have any questions.

Building CrossBridgeSDK from source on Windows

I would like to build CrossBridge SDK from source on Windows platform - but the first error I recieve:
make[1]: Entering directory '/cygdrive/f/crossbridge'
mkdir -p /cygdrive/f/crossbridge/build/extra
mkdir -p /cygdrive/f/crossbridge/build/win/abclibs
mkdir -p /cygdrive/f/crossbridge/sdk/usr/lib/bfd-plugins
mkdir -p /cygdrive/f/crossbridge/sdk/usr/share
mkdir -p /cygdrive/f/crossbridge/sdk/usr/platform/"cygwin"/bin
mkdir -p /cygdrive/f/crossbridge/sdk/usr/platform/"cygwin"/libexec/gcc/avm2-unknown-freebsd8
ln -sfn ../usr /cygdrive/f/crossbridge/sdk/usr/avm2-unknown-freebsd8
ln -sfn "cygwin" /cygdrive/f/crossbridge/sdk/usr/platform/current
ln -sfn platform/current/bin /cygdrive/f/crossbridge/sdk/usr/bin
ln -sfn ../ /cygdrive/f/crossbridge/sdk/usr/platform/usr
ln: `/cygdrive/f/crossbridge/sdk/usr/platform/usr/..': cannot overwrite directory
Makefile:899: recipe for target 'base' failed
make[1]: *** [base] Error 1
make[1]: Leaving directory '/cygdrive/f/crossbridge'
Anybody who tried to build this on windows with cygwin and has a step-by-step guide?
(I'll write one if I succeed).
Best Regards

I found this repo to be missing several essential tools; as far as I got I "found" that
unzip and rsync were missing.
Just adding a generic cygwin/bin to the path did not work, because an unsuitable version
of ranlib got into the tool chain.
I made some progress by constructing a special bin directory that contained only the
DLLs from cygwin/bin + unzip + rsync
The next stumble (still unresolved) is in make "make"
checking whether the C compiler works... no
configure: error: in `/cygdrive/c/crossbridge-master/build/win/make':
configure: error: C compiler cannot create executables

Wombat (Arch 0.7) Kernal build from source problem

Using the large Arch 0.7 ISO and selecting build Kernel 2.6 from source, the command "make menuconfig" fails because the ncurses library is not present.
I am able to start the build of the kernel using the default .config file. There were a number of warnings for configuration variables no longer being used, and a number of features had been deprecated. Its not finished yet, but I suspect it will work ok.
I may install the pre-built kernels just in case the config file is incorrect.
Should I put this in as a problem, or is it already fixed in 0.8?

Actually, the instructions are quite good and I did follow them
It's pretty easy, since you can alt between F1 and F2 and check what you have to type.
I going through the whole process again, since I did not like the error messages I was getting. As in the earlier case, I am only installing base (which includes ncurses.)
I am not going to build the kernel from source this time, but wait until the system is up before doing that.
I have never seen this problem before with the beta's of 0.7, so I am going to assume its a fluke. I have used beta's of Wombat on 9 machines and this was the first time it happened.
If no one else has had this problem, I am going to assume its my fault.
No big deal.

Building eveything from source with ABS

Hi. Im amazed with the ABS system. It´s aewsome, since I love to build all the software in my system from source, and compiling it and make it a binary package is just genious. But I have some questions, here they go:
1 - Im compiling everything using the ABS tree using makepkg -b, so it compiles and generates packages also for its dependencies and I edited makepkg.conf so all the generated packages go to a folder (i.e. /packages) so I can install them later using pacman -U package. My question is: If I later install a given packages, that depends on another, will that package be automatically installed when it´s needed? And is there a way to automatically redo all the source compiling and package generation automatically upon a source update for the packages I previously generated (like syncing in pacman)?
2- Im trying to build my desktop from source the ABS way the cleanest way possible, without all that kde programs, just the core of its window manager, so I would like to know what sources to compile. I guess it would be something like xorg -> kde -> nvidia drivers -> compiz-fusion (not supported by ABS) . Any directions, guys? Thanks in advance.
Last edited by Arthanis (2008-01-28 00:32:24)

Arthanis wrote:Sorry, it´s because i didn´t know how to move the post, I saw that if fit in another part of the forum
Don't worry too much. I suppose I was being mean given you are new here. It is just that help tends to be better when clustered in one place.
jacko wrote:I thought about doing this for myself at some point, there is a lot of things I just do not need that is compiled in by default which I could rid myself of but, is all the time worth it in the end? Would like to hear someone elses expertise on this issue.
Well, you could also add in more optimization for your specific processor. But I honestly don't think you need this for every package. Perhaps the kernel, glic and a couple of other often used and big packages, but in the end it is barely noticeable given Arch is fairly optimized by default and can make you system less stable.
The only real reason to recompile is to add/remove options. If the option is easy to add and doesn't bloat the package. the devs will probably add it for you if you ask in the bug tracker anyway. I think the only package I now recompile are mozilla ones because I want the branding.

[SOLVED] Building from source?

I'm new - quite new to Linux, totally new to Arch - thus this newbie question.
I can't seem to understand how to properly compile from source in Arch.
And before you ask, I have read the Wiki. A lot.
The way I understand it, normally one would use pacman and rely on it to find, download and install the package. I have not yet got a proper internet connection set up, and will therefore have to download the package(s) from my Win XP computer I'm sitting at.
I want to download wvdial - for getting dialup up and running. wvdial seems to depend on ppp, wvstreams and xplc, so I have to download those as well.
After searching, I found them all, but only the source code, as gzipped tarballs.
I understood that one was then supposed to use makepkg to make a package from the source code, and then install the resulting package using pacman.
Sounds OK, but it looks like I need a so-called PKGBUILD file for each package, a script used by makepkg to build the package correctly.
Did those tarballs contain any PKBUILD files? No. There were makefiles, but no such thing as a PKGBUILD file.
What am I supposed to do, then? Did I get the wrong tarballs?
I got wvdial from this page: http://www.archlinux.org/packages/extra/i686/wvdial/ which took me here: http://alumnit.ca/wiki/index.php?page=WvDial which again lead me here: http://alumnit.ca/wiki/index.php?page=DownloadReleases
This last page also included wvstreams.
For ppp: http://www.archlinux.org/packages/core/i686/ppp/
For xplc: http://www.archlinux.org/packages/extra/i686/xplc/
Last edited by Mzg (2009-09-06 18:13:28)

the binary package have to be downloaded from a mirror. here is a list with them: http://wiki.archlinux.org/index.php/Mirrors
note: http://www.archlinux.org/packages/extra/i686/wvdial
looking at the link you can find out where to look. is in extra repository, i686
http://linkmirror/extra/os/i686/

Building Asterisk from source error

Hello, I'm fairly new to Arch Linux and have been attempting to build Asterisk from source. Building on a Raspberry Pi and when I try and make, I get this error:
[pi@alarmpi asterisk-1.4.44]$ make
[CC] src/add.c -> src/add.o
gcc: error: unrecognized argument in option '-march=armv6l'
gcc: note: valid arguments to '-march=' are: armv2 armv2a armv3 armv3m armv4 armv4t armv5 armv5e armv5t armv5te armv6 armv6-m armv6j armv6k armv6s-m armv6t2 armv6z armv6zk armv7 armv7-a armv7-m armv7-r armv7e-m armv7ve armv8-a armv8-a+crc iwmmxt iwmmxt2 native
gcc: error: unrecognized argument in option '-march=armv6l'
gcc: note: valid arguments to '-march=' are: armv2 armv2a armv3 armv3m armv4 armv4t armv5 armv5e armv5t armv5te armv6 armv6-m armv6j armv6k armv6s-m armv6t2 armv6z armv6zk armv7 armv7-a armv7-m armv7-r armv7e-m armv7ve armv8-a armv8-a+crc iwmmxt iwmmxt2 native
/home/pi/builds/asterisk-1.4.44/Makefile.rules:91: recipe for target 'src/add.o' failed
make[2]: *** [src/add.o] Error 1
Makefile:50: recipe for target 'gsm/lib/libgsm.a' failed
make[1]: *** [gsm/lib/libgsm.a] Error 2
Makefile:369: recipe for target 'codecs' failed
make: *** [codecs] Error 2
I'm not very well versed in diagnosing Makefile errors…but I would assume at least one of the errors would be from gcc not seeing a valid -march option. Any suggestions on where I should look or what I should change to correct this error?
Last edited by zaplack (2014-11-18 20:23:37)

I found this repo to be missing several essential tools; as far as I got I "found" that
unzip and rsync were missing.
Just adding a generic cygwin/bin to the path did not work, because an unsuitable version
of ranlib got into the tool chain.
I made some progress by constructing a special bin directory that contained only the
DLLs from cygwin/bin + unzip + rsync
The next stumble (still unresolved) is in make "make"
checking whether the C compiler works... no
configure: error: in `/cygdrive/c/crossbridge-master/build/win/make':
configure: error: C compiler cannot create executables

Is it possible to build Java 1.5.0 from source?

I have posted a similar question on the "New To Java" list, but have not received an answer. I think that what I am trying to do is far too advanced for the Newbie forum.
I am attempting to build Java 1.5.0 from the source tarball I downloaded from java.sun.com - jdk-1_5_0-src.scsl.zip.
Sun's own build instructions at http://java.sun.com/j2se/1.5.0/scsl/build-linux.html state: "A GNU gcc compiler version 3.2.2 is required or gcc 3.2.1-7 built with the latest binutils package, version 2.13."
Since I have been completely unable to find gcc 3.2.1-7 anywhere on the internet, including at gnu.org, I used gcc 3.2.2.
Unfortunately, when I run the make scsl comman, I receive an error saying that gcc 3.2.2 is not supported and that I have to use gcc 3.2.1-7. I don't have the exact error message in front of me but can get it if it matters.
So it appears that Java 1.5.0 will not build with gcc 3.2.2. And I am not able to find gcc 3.2.1-7.
Has anyone out there tried to build Java 1.5.0 from source? Does anyone know why gcc 3.2.2 does not work?
And most importantly, does anyone know where I can find gcc 3.2.1-7?
Thanks.

Sun's own build instructions at
http://java.sun.com/j2se/1.5.0/scsl/build-linux.html
state: "A GNU gcc compiler version 3.2.2 isrequired
or gcc 3.2.1-7 built with the latest binutils
package, version 2.13."
Since I have been completely unable to find gcc
3.2.1-7 anywhere on the internet, including at
gnu.org, Did you try extracting it from the online source
control systems?No. I assumed that java.sun.com would be the definitive source for Java.
>
I used gcc 3.2.2.
Unfortunately, when I run the make scsl comman, I
receive an error saying that gcc 3.2.2 is not
supported and that I have to use gcc 3.2.1-7. I
don't have the exact error message in front of mebut
can get it if it matters.
So it appears that Java 1.5.0 will not build withgcc
3.2.2. And I am not able to find gcc 3.2.1-7.
I would suspect that 3.2.2 will work if you dig into
the build tools.

Building from source -- how to remove installation?

Greetings.
I am relatively new to the world of Linux, and while google has helped me thus far, I can't seem to solve this one: How do I effectively keep record of all the files being installed, when building from source?
When everything is done through Pacman or the AUR, it's all in a system; however, not when building it manually..
Some sourcefiles has an "make uninstall"-function, but not all.
I kinda feel that I don't have control over what's happening on my system, how do I solve this?
Thanks.

I only recently learned how to create my own packages. It was so easy! You can read about it here: http://wiki.archlinux.org/index.php/Building_Packages That link also provides a simple example "PKGBUILD" file.
As you can see, the "build" function in the PKGBUILD file is nothing more than what you would do to build the package by yourself. But, by creating a PKGBUILD file, using the "makepkg" command, and then installing it with "pacman -U package.pkg.tar.gz", you can easily uninstall it in the future.
If you want, you can then upload your PKGBUILD file to the AUR, and feel good as an Arch Linux contributor.
I found it interesting that Arch Linux doesn't even setup "/usr/local/bin" in the PATH by default. It's probably for the best. It keeps me from being naughty.

Building FretsOnFire from source - python problem

I am trying to build FretsOnFire from source so that I can get a native x86_64 version working.
So far I have working builds of amanith and pyamanith in AUR. I know these are working because I can run FretsOnFire directly from python.
To run FretsOnFire using just python, download both the src and the binary package. Copy the contents of the data folder from the binary package to the src package. Then run "python FretsOnFire.py" from the src directory of the source package. (This works on my i686 machine but I can't remember testing it on my x86_64 one).
Now I want to make the binary... To do that we need to edit Makefile.unix in the source package. Changes needed are:
1) CXFREEZE=/usr/share/cx-freeze/FreezePython
2) PYTHON_LIBS=/usr/lib/python2.5
3) /usr/local/lib/amanath -> /usr/lib/amanath
4) remove the following lines (quick hack that needs fixed later...):
/usr/lib/liblapack.so.3 \
/usr/lib/libg2c.so.0 \
/usr/lib/atlas/libblas.so.3 \
5) cx_freeze and epydoc are needed so intstall them.
6) copy FretsOnFire (shell script) from the binary package to data/launcher.sh in the source package
7) make -f Makefile.unix
Everything builds nicely! But running FretsOnFire from the newly created dist directory gives:
ImportError: No module named glx
What do I need to fix this?

@Demind: As I said above, I wanted a native x86_64 build. I have a hatred for lib32.
The problem is that amanith source code is not downloadable anymore.
I would be very happy to help you building a native x86_64 fretsonfire package but without that source code is impossible.
I don't know if in the past amanith was easily downloadable but now it doesn't seem to be so.
That's the real problem in my opinion and that's why i've used lib32.
However using lib32 is not so bad come on
Hmmm... I downloaded it only a couple of weeks ago. I even put working PKGBUILDs for amanith and pyamanith into AUR. But I see the company making it has gone all commercial on us.
Also, lib32 is evil! I don't use it out of principle. I was going to forgive FretsOnFire for the non-free songs but not to the extent of having to lib32ify my pure64(TM) system!

VIPM: pkg build aborted: "The following source VIs or Libraries are missing" (xpost from JKI forums)

Hey folks-
I hope this is not 'illegal' with respect to forum rules or anything, but I was thinking some of you that might be able to provide some insight on this might not necessarily be lurking the JKI forums as much as NI's...
http://forums.jki.net/topic/1718-pkg-build-aborted-the-following-source-vis-or-libraries-are-missing...
I've wasted many hours trying to figure this out...
thx
-pat

Re: Rules
You're OK in my book since you dclared it a cross-post.
It stops us from wasting our time trying to answer what has already been answered.
Sorry i can help with the QSM issue.
Take care,
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Building 32bit wine from source

Similar Messages

Maybe you are looking for