Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 22 Nov 2014 11:57:58 -0600
From: will cunningham <>
Subject: Re: changing/fixing the tarballs in the butch

By request I recreated the qt4 build problem to get the build log error.
Remember this happens when trying to build qt4 before installing xorg.
Here are the last few lines of build_qt4.log:

g++ -c -o qxmlutils.o -m64 -pipe -DQMAKE_OPENSOURCE_EDITION -I.
-Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac
g++ -o "/src/build/qt4/qt-everywhere-opensource-src-4.6.4/bin/qmake"
project.o property.o main.o makefile.o unixmake2.o unixmake.o mingw_make.o
option.o winmakefile.o projectgenerator.o meta.o makefiledeps.o
metamakefile.o xmloutput.o pbuilder_pbx.o borland_bmake.o msvc_dsp.o
msvc_vcproj.o msvc_nmake.o msvc_objectmodel.o symmake.o
initprojectdeploy_symbian.o symmake_abld.o symmake_sbsv2.o registry.o
epocroot.o qtextcodec.o qutfcodec.o qstring.o qtextstream.o qiodevice.o
qmalloc.o qglobal.o qbytearray.o qbytearraymatcher.o qdatastream.o
qbuffer.o qlist.o qfile.o qfsfileengine_unix.o
qfsfileengine_iterator_unix.o qfsfileengine.o qfsfileengine_iterator.o
qregexp.o qvector.o qbitarray.o qdir.o qdiriterator.o quuid.o qhash.o
qfileinfo.o qdatetime.o qstringlist.o qabstractfileengine.o
qtemporaryfile.o qmap.o qmetatype.o qsettings.o qlibraryinfo.o qvariant.o
qvsnprintf.o qlocale.o qlinkedlist.o qurl.o qnumeric.o qcryptographichash.o
qxmlstream.o qxmlutils.o  -m64
Basic XLib functionality test failed!
 You might need to modify the include and library search paths by editing

As I move forward tell me other things you want me to try/test as I'm
approaching this project as not just getting my core apps working but
understanding/taking control of the OS so I'm VERY interested in how this
all fits together.  For example I'd never heard of mdev/edev but I'm
reading up on them as I get x pumping, very interesting, and exciting libs
to be putting into/expanding practical use of.


On Wed, Nov 19, 2014 at 6:14 PM, will cunningham <>

> John,
> I wiped out and redid the install 10+ times last weekend, and finally was
> just trying to get past this stage, so I didn't write down/keep every
> problem log.  I'll go back after I'm fully up and try to get this isolated,
> or figure out what I was doing wrong/problems with my box/internet whatever.
> thanks again for helping me get past this stage,
> Will
> On Wed, Nov 19, 2014 at 4:43 PM, John Spencer <>
> wrote:
>> will cunningham wrote:
>>> OK I've got what I need loaded.  A couple pieces of business to close
>>> this
>>> thread out...
>>> You need to add xorg to the dependencies of qt4, or figure out what
>>> subset
>>> of xorg it need to compile.  Building qt4 right after stage1 and core it
>>> broke with a message something about an X11 lib, but after I installed
>>> xorg
>> did you make a note about the message? it would save us a lot of time
>> when we knew which lib it wanted.
>>  it built fine.  The no cups addition to the pkg file worked.
>>> I still get tarballs not downloading somewhat randomly, and I've found
>>> that
>>> if it starts to download but doesn't complete, you have to go in
>>> /src/tarballs and delete the source so it'll start fresh on the download
>> weird. you can take a look at what the KEEP/butch_download_template.txt
>> does
>> in general it gets a list of urls from the pkg, and then tries to dl them
>> with wget --retries=5
>> so in the case that one of the urls is broken, it would try up to 5 times
>> to download it before switching to the next url. note that
>> downloads-in-progress are saved to $filename.wip and only after a
>> successful download renamed to $filename.
>> in any case: please provide the names of the packages which made trouble.
>>  and not just try to work with what's there partially.  Also when
>>> something
>>> doesn't build, rebuilding the last lib in the log and then restarting
>>> with
>>> butch rebuild instead of butch install on the unfinished build usually
>>> gets
>>> it done.  Not scientific, but trying several combinations to get apps
>>> built
>>> this has worked for me.
>> in general stuff that works by magic is not in the spirit of sabotage. we
>> try to deliver sound solutions that are reproducible.
>> --JS

Content of type "text/html" skipped

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.