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.

Similar Messages

  • 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.

  • [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/

  • Haguichi won't build from AUR, and won't build from source tarball.

    I managed to get Hamachi installed. Go me. But I like having a frontend for things like that, so I tried to build Haguichi from the AUR. Didn't work. I downloaded the source tarball, and running ./configure returned the same error as yaourt.
    redpill% ./configure
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
    checking for gawk... gawk
    checking whether make sets $(MAKE)... yes
    checking whether to enable maintainer-specific portions of Makefiles... no
    checking for pkg-config... /usr/bin/pkg-config
    checking for dmcs... /usr/bin/dmcs
    checking pkg-config is at least version 0.9.0... yes
    checking for GTK_SHARP_20... yes
    checking for NOTIFY_SHARP... yes
    checking for GCONF_SHARP_20... yes
    checking for GLIB_SHARP_20... yes
    checking for DBUS_SHARP_10... no
    configure: error: Package requirements (dbus-sharp-1.0) were not met:
    No package 'dbus-sharp-1.0' found
    Consider adjusting the PKG_CONFIG_PATH environment variable if you
    installed software in a non-standard prefix.
    Alternatively, you may set the environment variables DBUS_SHARP_10_CFLAGS
    and DBUS_SHARP_10_LIBS to avoid the need to call pkg-config.
    See the pkg-config man page for more details.
    I made sure the dependencies were installed and updated to the latest versions, but it still won't build. What am I doing wrong?

    Scimmia wrote:Did you read the comments on the AUR page?
    Just did. I guess I'm still a bit noobish

  • Building from source

    Hello,
    I need the application Xwisp2 from http://www.robh.nl/picsoft.php. This software isn't downloadable as binary but only as source. I'm very unknown to programming, building a package with a makefile I can, but this even doesnt have one. Can anyone explane me how I turn this into an excecutable application please.
    I'd be very happy.
    Thank you
      Mac OS X (10.4.8)  

    The answer depends on the number of files that are part of the distribution and the language in which they were written. In the simple case, if you have a single source file, you can typically build it with make without a makefile. For example, you can generally build foo from foo.cpp with: make foo

  • MySQL custom build from sources best practices advices

    Hi,
    These days I'm setting up something that could be called a home server, basically a web server with DB support.
    Of course it's based on Arch Linux (probably not the best choice while everyone around is speaking about CentOS, RHLE, Debian, etc as server-oriented linuxes, anyway I hope Arch is not worse).
    Every application I need is available in packages, but the idea is to build every app to a custom and better organized location.
    I'm not a fan of the applications' distribuition in  /bin  /sbin  /lib  /var  /etc ...
    I embrace the philosophy of "one application in one place" with a structure similar to
    /appdir
    |---/app1
    |---/bin
    |---/lib
    |---/conf
    |---/docs
    |---/logs
    |---/tmp
    that's why I would like to build all my applications using the same pattern.
    Now I want to build the MySQL database server, but the process it's not straightforward like for other applications.
    I use the following configure inspired from --help, MySQL docs and PKGBUILD provided by the Arch mysql package:
    CFLAGS="-fPIC -march=amdfam10 -mtune=amdfam10 -O2 -pipe -fno-strict-aliasing -DBIG_JOINS=1 -fomit-frame-pointer" \
    CXXFLAGS="-fPIC -march=amdfam10 -mtune=amdfam10 -O2 -pipe -fno-strict-aliasing -DBIG_JOINS=1 -felide-constructors -fno-exceptions -fno-rtti" \
    ./configure \
    --sysconfdir=/usr/local/apps/mysql/conf \
    --prefix=/usr/local/apps/mysql \
    --exec-prefix=/usr/local/apps/mysql \
    --sbindir=/usr/local/apps/mysql/sbin \
    --docdir=/usr/local/apps/mysql/docs \
    --mandir=/usr/local/apps/mysql/man \
    --datarootdir=/usr/local/apps/mysql/share \
    --libexecdir=/usr/local/apps/mysql/sbin \
    --localstatedir=/usr/local/apps/mysql/data \
    --with-mysqld-ldflags=-all-static \
    --with-zlib-dir=bundled \
    --enable-assembler \
    --without-debug \
    --without-docs \
    --without-readline \
    --with-mysqld-user=mysql \
    --with-libwrap \
    --with-charset=utf8 \
    --with-collation=utf8_general_ci \
    --with-extra-charsets=binary,ascii,cp1250,cp1251,koi8r,latin1,latin2,latin5,utf8 \
    --with-embedded-server \
    --with-unix-socket-path=/var/run/mysqld.sock \
    --enable-local-infile \
    --with-plugins=partition,ftexample,blackhole,csv,heap,innobase,innodb_plugin
    Could someone with a deeper understanding of the process to give me some advices about optimization, plugins, etc, please?
    I want to build a fast server without unnecessary stuff.
    Some questions are about paths and directories:
    1) is it possible to get the pattern described above without having paths like  mysql/mysql/..., mysql/lib/mysql/<files>, mysql/include/mysql/<files>  but  mysql/lib/<files>, etc  ?
    2) is it OK to delete  mysql-test  and  sql-bench  directories if I don't need them ?

    bigman2126 wrote:
    Stebalien wrote:2. Never build wireless/wired modules into the kernel. If you use fuse, don't build that into your kernel either.
    I would like to know the reason too, I tend to build my custom kernels so that the hardware and things I use are compiled into the kernel.
    bangkok_manouel wrote:because the firmware is loaded later so the module is not properly initialized (or some word that sounds like this)
    That *has* to depend on the specific wifi driver because I have iwlwifi-1000 built into my kernel as we speak and it loads the firmware fine.
    As far as i915 and modesetting goes, I had the exact same issues.  It turned out in my case another driver was stealing control before the intel kms one could grab it (maybe FB_VESA?).  Anyways, here's the relevant part of my kernel config that does work with i915 kms built-in:
    http://pastebin.com/jaCAqPjh

  • Google Chromium takes up to 10 gigs to build from source?

    So I was browsing the AUR and saw in the package build for chromium-browser-svn that the build can take up to 5gigs to build. Well after surfing the web the official chromium wiki states that it can take up to 10gigs.
    This seems crazy to me, though I don't have a lot of programming knowledge.
    So my question is, does anyone here know why a program like this, that doesn't have a very large binary, would take so much disk space to build?

    Wow, I didn't realize that the source was 900mb. But still, 10gb is a whole order of magnitude greater than the source. I don't know, maybe I just don't know enough, or anything for that mater, about how software compilation happens, but this still seems quite ludicrous to me.
    So is there a simple answer to this or is it quite complicated?
    Thanks for any helpful information.

  • How to optimize building from source.

    Hi, ive read about MAKE options to optimize the package youre building, like "-march, -O3, -pipe and -fomit-frame-pointer"
    Is there another ways to improve package speed and optimize?

    bangkok_manouel wrote:
    I'm surprised no one's using the new graphite branch loop optimizations:
    -floop-interchange -floop-strip-mine -floop-block (See http://gcc.gnu.org/gcc-4.4/changes.html)
    Using this since GCC4.4 was pushed in [TESTING], no build problems at all. Of course, the performance gain is >>!*HUGE*!<< but won't be noticed by any human being. ;-)
    Found this in another thread... not sure how sarcastic he is being... is it worth using those optimizations?

  • Lesson 9 of DW CS5 & PHP Training from source problem

    Page 315.  Supposed to show name of file uploaded after inserting code for $filename.  The $filename is never shown.  How can I check to see that the $messages[] is set, and how can I trace the problem? Result SHOULD be that the message "filename successfully uploaded" where filename is the name of the file.   Code follows:
    process_upload.php:
    <?php
    if (isset($_POST['upload'])) {
        require_once('library.php');
        try {
            $destination = 'C:/upload_test';
            $uploader = new Zend_File_Transfer_Adapter_Http();
            $uploader->setDestination($destination);
            $success = $uploader->receive();
            if (!$success) {
                $messages = $uploader->getMessages();
            } else{
                $filename = $uploader->getFileName(NULL, FALSE);
                $MESSAGES[] = "$filename uploaded successfully";
        } catch (Exception $e) {
            echo $e->getMessage();
    upload_test.php:
    <?php
    require_once('scripts/process_upload.php');
    ?>
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <title>Untitled Document</title>
    </head>
    <body>
    <?php
    if (isset($messages)) {
        echo '<ul>';
        foreach ($messages as $item) {
            echo "<li>$item</li>";
        echo '</ul>';
    ?>
    <form action"" method="post" enctype = "multipart/form-data" name="form1" id="form1">
      <p>
        <input name="MAX_FILE_SIZE" type="hidden" id="MAX_FILE_SIZE" value="51200" />
        <label for="upload_file">File to upload</label>
        <input type="file" name="upload_file" id="upload_file" />
      </p>
      <p>
        <input type="submit" name="upload" id="upload" value="Upload File" />
      </p>
    </form>
    </body>
    </html>
    For the life of me, I can not figure out why the message that the file uploaded successfully isn't displayed.

    Absolutely.  BTW... I'm loving this book.  One of the things I have on my plate right now is designing a dedicated upload section for a client.  They need to have an area where their clients can upload files - images, pdf files, powerpoint displays, you name it, they have to be able to accept them.  Chapter 9 is giving me the background to develop the utility they need.
    Gene

  • 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)

  • 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

  • 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.

  • 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

  • Build pygame from source

    Hi,
    I've been trying to install pygame from source on OS X 10.5.5. Following the instructions [here|http://pygame.org/wiki/MacCompile?action=view], everything went fine until I got to the stage
    Edit Setup and put a '#' at the start of the line:
    #scrap src/scrap.c $(SDL) $(X11)
    My Setup file does not contain this line. Attempting to run python setup.py build produces problems...
    Using Darwin configuration...
    Hunting dependencies...
    Framework SDL found
    Framework SDL_ttf found
    Framework SDL_image found
    Framework SDL_mixer found
    Framework smpeg not found
    PNG : found
    JPEG : found
    SCRAP : not found
    If you get compiler errors during install, doublecheck
    the compiler flags in the "Setup" file.
    ~/Downloads/pygame-1.8.1release 2 19 (1781) $ python setup.py build
    running build
    running build_py
    creating build
    creating build/lib.macosx-10.5-i386-2.5
    creating build/lib.macosx-10.5-i386-2.5/pygame
    copying lib/_init_.py -> build/lib.macosx-10.5-i386-2.5/pygame
    copying lib/_numpysndarray.py -> build/lib.macosx-10.5-i386-2.5/pygame
    copying lib/_numpysurfarray.py -> build/lib.macosx-10.5-i386-2.5/pygame
    copying lib/colordict.py -> build/lib.macosx-10.5-i386-2.5/pygame
    copying lib/cursors.py -> build/lib.macosx-10.5-i386-2.5/pygame
    copying lib/locals.py -> build/lib.macosx-10.5-i386-2.5/pygame
    copying lib/mac_scrap.py -> build/lib.macosx-10.5-i386-2.5/pygame
    copying lib/macosx.py -> build/lib.macosx-10.5-i386-2.5/pygame
    copying lib/pkgdata.py -> build/lib.macosx-10.5-i386-2.5/pygame
    copying lib/sndarray.py -> build/lib.macosx-10.5-i386-2.5/pygame
    copying lib/sprite.py -> build/lib.macosx-10.5-i386-2.5/pygame
    copying lib/surfarray.py -> build/lib.macosx-10.5-i386-2.5/pygame
    copying lib/sysfont.py -> build/lib.macosx-10.5-i386-2.5/pygame
    copying lib/version.py -> build/lib.macosx-10.5-i386-2.5/pygame
    creating build/lib.macosx-10.5-i386-2.5/pygame/gp2x
    copying lib/gp2x/_init_.py -> build/lib.macosx-10.5-i386-2.5/pygame/gp2x
    copying lib/gp2x/constants.py -> build/lib.macosx-10.5-i386-2.5/pygame/gp2x
    copying lib/gp2x/locals.py -> build/lib.macosx-10.5-i386-2.5/pygame/gp2x
    creating build/lib.macosx-10.5-i386-2.5/pygame/threads
    copying lib/threads/_init_.py -> build/lib.macosx-10.5-i386-2.5/pygame/threads
    copying lib/threads/Py25Queue.py -> build/lib.macosx-10.5-i386-2.5/pygame/threads
    running build_ext
    building 'pygame.imageext' extension
    creating build/temp.macosx-10.5-i386-2.5
    creating build/temp.macosx-10.5-i386-2.5/src
    gcc -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd -fno-common -dynamic -DNDEBUG -g -Os -Wall -Wstrict-prototypes -DMACOSX -I/usr/include/ffi -DENABLE_DTRACE -arch i386 -arch ppc -pipe -Ddarwin -I/Library/Frameworks/SDL.framework/Versions/Current/Headers -I/Library/Frameworks/SDL_image.framework/Versions/Current/Headers -I/usr/local/include -I/usr/local/include -I/System/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5 -c src/imageext.c -o build/temp.macosx-10.5-i386-2.5/src/imageext.o
    In file included from /System/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/Pyth on.h:8,
    from src/pygame.h:60,
    from src/imageext.c:31:
    /System/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/pycon fig.h:386:1: warning: "HAVE_PROTOTYPES" redefined
    In file included from /usr/local/include/jpeglib.h:24,
    from src/imageext.c:30:
    /usr/local/include/jconfig.h:5:1: warning: this is the location of the previous definition
    In file included from /System/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/Pyth on.h:8,
    from src/pygame.h:60,
    from src/imageext.c:31:
    /System/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/pycon fig.h:516:1: warning: "HAVESTDLIBH" redefined
    In file included from /usr/local/include/jpeglib.h:24,
    from src/imageext.c:30:
    /usr/local/include/jconfig.h:12:1: warning: this is the location of the previous definition
    In file included from /System/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/Pyth on.h:8,
    from src/pygame.h:60,
    from src/imageext.c:31:
    /System/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/pycon fig.h:386:1: warning: "HAVE_PROTOTYPES" redefined
    In file included from /usr/local/include/jpeglib.h:24,
    from src/imageext.c:30:
    /usr/local/include/jconfig.h:5:1: warning: this is the location of the previous definition
    In file included from /System/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/Pyth on.h:8,
    from src/pygame.h:60,
    from src/imageext.c:31:
    /System/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/pycon fig.h:516:1: warning: "HAVESTDLIBH" redefined
    In file included from /usr/local/include/jpeglib.h:24,
    from src/imageext.c:30:
    /usr/local/include/jconfig.h:12:1: warning: this is the location of the previous definition
    src/imageext.c:353: warning: function declaration isn't a prototype
    src/imageext.c: In function 'opengltosdl':
    src/imageext.c:357: warning: unused variable 'formatflag'
    src/imageext.c:357: warning: unused variable 'typeflag'
    src/imageext.c:356: warning: unused variable 'readpixels'
    src/imageext.c:356: warning: unused variable 'pyopengl'
    src/imageext.c:353: warning: function declaration isn't a prototype
    src/imageext.c: In function 'opengltosdl':
    src/imageext.c:357: warning: unused variable 'formatflag'
    src/imageext.c:357: warning: unused variable 'typeflag'
    src/imageext.c:356: warning: unused variable 'readpixels'
    src/imageext.c:356: warning: unused variable 'pyopengl'
    gcc -Wl,-F. -bundle -undefined dynamic_lookup -arch i386 -arch ppc build/temp.macosx-10.5-i386-2.5/src/imageext.o -L/opt/local/lib -L/opt/local/lib -lpng -ljpeg -o build/lib.macosx-10.5-i386-2.5/pygame/imageext.so -framework SDL -F/Library/Frameworks/ -framework SDL_image -F/Library/Frameworks/
    ld warning: in /opt/local/lib/libpng.dylib, file is not of required architecture
    ld warning: in /opt/local/lib/libjpeg.dylib, file is not of required architecture
    ld: in /opt/local/lib/libz.1.dylib, file is not of required architecture for architecture ppc
    collect2: ld returned 1 exit status
    lipo: can't open input file: /var/tmp//cc0jcawF.out (No such file or directory)
    error: command 'gcc' failed with exit status 1
    In particular, the line gcc -Wl,-F. -bundle -undefined dynamic_lookup -arch i386 -arch ppc build/temp.macosx-10.5-i386-2.5/src/imageext.o -L/opt/local/lib -L/opt/local/lib -lpng -ljpeg -o build/lib.macosx-10.5-i386-2.5/pygame/imageext.so -framework SDL -F/Library/Frameworks/ -framework SDL_image -F/Library/Frameworks/ \[emphasis mine\] seems odd.
    The Setup file doesn't seem to contain anything helpful...
    #This Setup file is used by the setup.py script to configure the
    #python extensions. You will likely use the "config.py" which will
    #build a correct Setup file for you based on your system settings.
    #If not, the format is simple enough to edit by hand. First change
    #the needed commandline flags for each dependency, then comment out
    #any unavailable optional modules in the first optional section.
    SDL = -I/Library/Frameworks/SDL.framework/Versions/Current/Headers -Ddarwin -Xlinker "-framework" -Xlinker "SDL" -Xlinker "-F/Library/Frameworks/"
    FONT = -I/Library/Frameworks/SDL_ttf.framework/Versions/Current/Headers -Xlinker "-framework" -Xlinker "SDL_ttf" -Xlinker "-F/Library/Frameworks/"
    IMAGE = -I/Library/Frameworks/SDL_image.framework/Versions/Current/Headers -Xlinker "-framework" -Xlinker "SDL_image" -Xlinker "-F/Library/Frameworks/"
    MIXER = -I/Library/Frameworks/SDL_mixer.framework/Versions/Current/Headers -Xlinker "-framework" -Xlinker "SDL_mixer" -Xlinker "-F/Library/Frameworks/"
    SMPEG = -ls -lm -lp -le -lg
    PNG = -I/usr/local/include -L/opt/local/lib -lpng
    JPEG = -I/usr/local/include -L/opt/local/lib -ljpeg
    SCRAP = -I.
    #DEBUG = -C-W -C-Wall
    DEBUG =
    #the following modules are optional. you will want to compile
    #everything you can, but you can ignore ones you don't have
    #dependencies for, just comment them out
    imageext src/imageext.c $(SDL) $(IMAGE) $(PNG) $(JPEG) $(DEBUG)
    font src/font.c $(SDL) $(FONT) $(DEBUG)
    mixer src/mixer.c $(SDL) $(MIXER) $(DEBUG)
    mixer_music src/music.c $(SDL) $(MIXER) $(DEBUG)
    _numericsurfarray src/_numericsurfarray.c $(SDL) $(DEBUG)
    _numericsndarray src/_numericsndarray.c $(SDL) $(MIXER) $(DEBUG)
    #movie src/movie.c $(SDL) $(SMPEG) $(DEBUG)
    #scrap src/scrap.c $(SDL) $(SCRAP) $(DEBUG)
    #experimental new movie movie. requires libavcodec and libavformat.
    #add any necessary compile flags to this line and uncomment.
    #movieext src/movie.c src/ffmovie.c $(SDL) -lavcodec -lavformat
    #these modules are required for pygame to run. they only require
    #SDL as a dependency. these should not be altered
    base src/base.c $(SDL) $(DEBUG)
    cdrom src/cdrom.c $(SDL) $(DEBUG)
    color src/color.c $(SDL) $(DEBUG)
    constants src/constants.c $(SDL) $(DEBUG)
    display src/display.c $(SDL) $(DEBUG)
    event src/event.c $(SDL) $(DEBUG)
    fastevent src/fastevent.c src/fastevents.c $(SDL) $(DEBUG)
    key src/key.c $(SDL) $(DEBUG)
    mouse src/mouse.c $(SDL) $(DEBUG)
    rect src/rect.c $(SDL) $(DEBUG)
    rwobject src/rwobject.c $(SDL) $(DEBUG)
    surface src/surface.c src/alphablit.c src/surface_fill.c $(SDL) $(DEBUG)
    surflock src/surflock.c $(SDL) $(DEBUG)
    time src/time.c $(SDL) $(DEBUG)
    joystick src/joystick.c $(SDL) $(DEBUG)
    draw src/draw.c $(SDL) $(DEBUG)
    image src/image.c $(SDL) $(DEBUG)
    overlay src/overlay.c $(SDL) $(DEBUG)
    transform src/transform.c src/rotozoom.c src/scale2x.c $(SDL) $(DEBUG)
    mask src/mask.c src/bitmask.c $(SDL) $(DEBUG)
    bufferproxy src/bufferproxy.c $(SDL) $(DEBUG)
    pixelarray src/pixelarray.c $(SDL) $(DEBUG)
    +Message was edited by: semicolons+

    Hi,
    have you installed the prebuild binaries for libjpeg, and libpng? They are universal binaries.
    Otherwise you can copy/paste the gcc line, and get rid of the ppc part. Then run setup.py again, and it should continue on.
    (otherwise get a python from python.org and use the binaries... they work fine on leopard)
    cheers,

  • Arch from source

    Has anybody built Arch from source? Does anybody build packages from ABS (doesn't install it from official repo)?

    Does anybody build packages from ABS (doesn't install it from official repo)?
    I do that for some performance-critical packages like mplayer or for packages which aren't up to date yet, but from which i need the new features anyway(wine and the nvidia-drivers for instance). Actually building something source instead of binary is quite simplified by using yaourt(search the forums), since you only have type "yaourt -Sb package" to do it, although this is currently broken for community packages due to the repo migration from cvs to svn.
    I don't see much sense in doing that for all packages though, because the difference from i686 to your architecture should not be noticable in most cases, especially if you don't have a very new chipset. This in my opinion waste of time when compiling _everything_ was actually the main reason that made me leave gentoo for archlinux.
    Last edited by Asgaroth (2008-06-18 16:57:47)

Maybe you are looking for