llvm dev - Apr 2006 - [LLVMdev] 1.7 Pre-Release Ready for Testing

I would like to test but the I modigied the configure 
 to make unknown = OpenBSD and Unix and go pretty far but 
 it died right after 'supports mkdir' yes...
 then the next line was 'your system is unsupported''
 I have gcc 3.3 on OpenBSD 3.3 pro-police stack compiler...
 I am only really interested in testing the C/C++ but C primarily 
 for my work.
 regards, Joseph Altea

Chris Lattner <sabre at nondot.org> wrote: On Sun, 16 Apr 2006, Tanya
Lattner wrote:
> For testing, we would like a mix of people to do x86 and ppc. Please send 
> email to the list if you plan to test, what architecture, and if you will
use
> the llvm-gcc binary or compile it yourself. That way, I know who to expect 
> results from.
I will test on Darwin/PPC, I'll try the precompiled llvmgcc, objdir != 
srcdir.

-Chris

-- 
http://nondot.org/sabre/
http://llvm.org/

_______________________________________________
LLVM Developers mailing list
LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev


		
---------------------------------
  Switch an email account to Yahoo! Mail, you could win FIFA World Cup tickets. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20060417/d54b69db/attachment.html>

Hi Josephm
> I would like to test but the I modigied the configure to make unknown
> = OpenBSD and Unix and go pretty far but it died right after 'supports
> mkdir' yes...
Could that have been `checking for mkdir...'?
> then the next line was 'your system is unsupported''
Have you looked at ./config.log.  ./configure creates this as it runs as
a trace of the path it took through ./configure.  Work backwards from
the end to find out what it didn't like.

Cheers,


Ralph.

PS.  Could you quote text you're replying to as otherwise it can make
reading the email a little confusing.

Hi again,

I wrote:
> > I would like to test but the I modigied the configure to make
> > unknown = OpenBSD and Unix
> 
> Have you looked at ./config.log.  ./configure creates this as it runs
> as a trace of the path it took through ./configure.  Work backwards
> from the end to find out what it didn't like.
I remember SourceForge's compile farm has an OpenBSD x86 machine so
thought I'd give it a go with a recent CVS check-out.

    $ ./configure
    configure: WARNING: Unknown project (HowToUseJIT) won't be configured
automatically
    configure: WARNING: Unknown project (ModuleMaker) won't be configured
automatically
    configure: WARNING: Unknown project (SmallExamples) won't be configured
automatically
    checking build system type... i386-unknown-openbsd3.8
    checking host system type... i386-unknown-openbsd3.8
    checking target system type... i386-unknown-openbsd3.8
    checking type of operating system we're on... Unknown
    configure: error: Operating system is unknown, configure can't continue

LLVM's configure.ac has a hard-coded list of supported platforms, which
is a shame, and `openbsd' isn't in it.

    [case $build in
      *-*-aix*) 
        llvm_cv_os_type="AIX" 
        llvm_cv_platform_type="Unix" ;;
    ...
      *-*-freebsd*) 
        llvm_cv_os_type="FreeBSD" 
        llvm_cv_platform_type="Unix" ;;

So I forged `freebsd'

    $ ./configure --build=i386-unknown-freebsd3.8

and ./configure completed successfully.  gmake stopped with

    llvm[1]: Compiling Mutex.cpp for Debug build
    Mutex.cpp:55: warning: the address of `int pthread_mutex_init(volatile
       pthread_mutex**, pthread_mutex_attr* const*)', will always be
`true'
    Mutex.cpp: In constructor `llvm::sys::Mutex::Mutex(bool)':
    Mutex.cpp:80: error: `pthread_mutexattr_setpshared' undeclared (first
use this
       function)
    Mutex.cpp:80: error: (Each undeclared identifier is reported only once for
each
       function it appears in.)

    78  #ifndef __FreeBSD__
    79      // Make it a process local mutex
    80      errorcode = pthread_mutexattr_setpshared(&attr,
PTHREAD_PROCESS_PRIVATE);
    81  #endif

So I modified both occurrences of __FreeBSD__ to also check for
__OpenBSD__.

The next problem was INT8_MAX, etc., weren't being defined.
include/llvm/Support/DataTypes.h.in is inadequate for this platform.  I
dumped a set of definitions into each file that wanted them as a bodge.
Better autoconf tests could set up INT8_MAX, etc., on all platforms that
don't define them.

After that, the build completed and I could run llvm-{as,dis} and lli.

So with a little work, OpenBSD looks like it could be supported out of
the box.  I've only a low-bandwidth Internet connection at the moment so
it won't be by me but is there a `how to submit a patch for LLVM'
document somewhere?

Cheers,


Ralph.