Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 165] New: openmotif does not build
Date: Tue, 10 Mar 2009 07:47:05 +0000 (UTC)	[thread overview]
Message-ID: <bug-165-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=165

              Host: Ubuntu 8.10 (64bit)
            Target: i586
             Build: buildroot-2009.02
           Summary: openmotif does not build
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: mathis_w at gmx.net
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created an attachment (id=117)
 --> (https://bugs.busybox.net/attachment.cgi?id=117)
buildroot configuration

When compiling buildroot with openmotif enabled, it always fails with:

make[3]: Betrete Verzeichnis
'/home/mathis/buildroot-2009.02/build_i586/openmotif-2.3.0-host/config/util'
gcc -DHAVE_CONFIG_H -I. -I../../include -I../../lib/Xm     -g -O2 -Wall -g
-fno-strict-aliasing -Wno-unused -Wno-comment -fno-tree-ter -MT makestrs.o -MD
-MP -MF .deps/makestrs.Tpo -c -o makestrs.o makestrs.c
mv -f .deps/makestrs.Tpo .deps/makestrs.Po
/bin/bash ../../libtool --tag=CC   --mode=link gcc  -g -O2 -Wall -g
-fno-strict-aliasing -Wno-unused -Wno-comment -fno-tree-ter   -o makestrs
makestrs.o  
../../libtool: line 810: X--tag=CC: command not found
../../libtool: line 843: libtool: ignoring unknown tag : command not found
../../libtool: line 810: X--mode=link: command not found
../../libtool: line 976: *** Warning: inferring the mode of operation is
deprecated.: command not found
../../libtool: line 977: *** Future versions of Libtool will require
--mode=MODE be specified.: command not found
../../libtool: line 2213: X-g: command not found
../../libtool: line 2213: X-O2: command not found
../../libtool: line 2213: X-Wall: command not found
../../libtool: line 2213: X-g: command not found
../../libtool: line 2213: X-fno-strict-aliasing: command not found
../../libtool: line 2213: X-Wno-unused: command not found
../../libtool: line 2213: X-Wno-comment: command not found
../../libtool: line 2213: X-fno-tree-ter: command not found
../../libtool: line 2382: Xmakestrs: command not found
X: user not authorized to run the X server, aborting.
../../libtool: line 2394: Xmakestrs: command not found
../../libtool: line 2402: mkdir /.libs: No such file or directory
mkdir: cannot create directory `/.libs': Permission denied
make[3]: *** [makestrs] Fehler 1


-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2009-03-10  7:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-10  7:47 bugzilla at busybox.net [this message]
2009-03-10  7:50 ` [Buildroot] [Bug 165] openmotif does not build bugzilla at busybox.net
2009-07-28 14:12 ` bugzilla at busybox.net
2009-07-28 20:03 ` bugzilla at busybox.net
2010-02-21 18:51 ` bugzilla at busybox.net
2010-02-24 21:59 ` bugzilla at busybox.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-165-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox