From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 3955] New: git buildroot python 2.7.1 OBSOLETE utime x86_64
Date: Mon, 11 Jul 2011 03:00:42 +0000 (UTC) [thread overview]
Message-ID: <bug-3955-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=3955
Summary: git buildroot python 2.7.1 OBSOLETE utime x86_64
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: tspielkop at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
[code]~/buildroot/output/host/usr/bin/ccache
~/buildroot/output/host/usr/bin/x86_64-unknown-linux-uclibc-gcc -Xlinker
-export-dynamic -o python \
Modules/python.o \
-L. -lpython2.7 -lpthread -ldl -lpthread -lutil -lm
./libpython2.7.so: warning: the use of OBSOLESCENT `utime' is discouraged, use
`utimes'
~/buildroot/output/build/host-python-2.7.1/python: error while loading shared
libraries: libdl.so.0: cannot open shared object file: No such file or
directory
make[1]: *** [sharedmods] Error 127
make[1]: Leaving directory `~/buildroot/output/build/python-2.7.1'
make: *** [~/buildroot/output/build/python-2.7.1/.stamp_built] Error 2[/code]
Seems like it it a spelling mistake instead of utime it should be utimes.
PS.
Buildroot: any idea what happened to the .config python 2.7.1 option that is
now missing, maybe setting 2.7.2 has this error fixed.
--
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.
next reply other threads:[~2011-07-11 3:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 3:00 bugzilla at busybox.net [this message]
2013-05-26 10:37 ` [Buildroot] [Bug 3955] git buildroot python 2.7.1 OBSOLETE utime x86_64 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-3955-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