FAQ
After installing python 2.7.1 on a Freebsd 8.0 system with the normal configure
make dance

./configure --prefix=$HOME/PYTHON --enable-unicode=ucs2
make
make install

I find that when I build extensions PIL, MySQLdb I'm getting errors related to a
dangling ${LDFLAGS}

eg MySQLdb
running build_ext
building '_mysql' extension
creating build/temp.freebsd-7.0-RELEASE-i386-2.7
gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -Dversion_info=(1,2,2,'final',0) -D__version__=1.2.2 -I/usr/local/include/mysql -I/home/rptlab/PYTHON/include/python2.7 -c _mysql.c -o build/temp.freebsd-7.0-RELEASE-i386-2.7/_mysql.o -fno-strict-aliasing -pipe
gcc -pthread -shared ${LDFLAGS} build/temp.freebsd-7.0-RELEASE-i386-2.7/_mysql.o -L/usr/local/lib/mysql -lmysqlclient_r -lz -lcrypt -lm -o build/lib.freebsd-7.0-RELEASE-i386-2.7/_mysql.so
gcc: ${LDFLAGS}: No such file or directory
error: command 'gcc' failed with exit status 1
where should I be looking to fix this problem?
--
Robin Becker

Search Discussions

  • Philip Semanchuk at Feb 21, 2011 at 10:36 pm

    On Feb 21, 2011, at 12:56 PM, Robin Becker wrote:

    After installing python 2.7.1 on a Freebsd 8.0 system with the normal configure make dance

    ./configure --prefix=$HOME/PYTHON --enable-unicode=ucs2
    make
    make install

    I find that when I build extensions PIL, MySQLdb I'm getting errors related to a dangling ${LDFLAGS}

    eg MySQLdb
    running build_ext
    building '_mysql' extension
    creating build/temp.freebsd-7.0-RELEASE-i386-2.7
    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -Dversion_info=(1,2,2,'final',0) -D__version__=1.2.2 -I/usr/local/include/mysql -I/home/rptlab/PYTHON/include/python2.7 -c _mysql.c -o build/temp.freebsd-7.0-RELEASE-i386-2.7/_mysql.o -fno-strict-aliasing -pipe
    gcc -pthread -shared ${LDFLAGS} build/temp.freebsd-7.0-RELEASE-i386-2.7/_mysql.o -L/usr/local/lib/mysql -lmysqlclient_r -lz -lcrypt -lm -o build/lib.freebsd-7.0-RELEASE-i386-2.7/_mysql.so
    gcc: ${LDFLAGS}: No such file or directory
    error: command 'gcc' failed with exit status 1
    where should I be looking to fix this problem?
    It's been a while since I built anything on FreeBSD, but one thing that jumps out at me is that you say you're building on 8.0 but the build output you gave us mentions 7.0. That doesn't sound right at all.

    Are you using ports?

    bye
    Philip
  • Stefan Krah at Feb 21, 2011 at 10:46 pm

    Philip Semanchuk wrote:
    On Feb 21, 2011, at 12:56 PM, Robin Becker wrote:
    After installing python 2.7.1 on a Freebsd 8.0 system with the normal configure make dance

    ./configure --prefix=$HOME/PYTHON --enable-unicode=ucs2
    make
    make install

    I find that when I build extensions PIL, MySQLdb I'm getting errors related to a dangling ${LDFLAGS}

    eg MySQLdb
    running build_ext
    building '_mysql' extension
    creating build/temp.freebsd-7.0-RELEASE-i386-2.7
    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -Dversion_info=(1,2,2,'final',0) -D__version__=1.2.2 -I/usr/local/include/mysql -I/home/rptlab/PYTHON/include/python2.7 -c _mysql.c -o build/temp.freebsd-7.0-RELEASE-i386-2.7/_mysql.o -fno-strict-aliasing -pipe
    gcc -pthread -shared ${LDFLAGS} build/temp.freebsd-7.0-RELEASE-i386-2.7/_mysql.o -L/usr/local/lib/mysql -lmysqlclient_r -lz -lcrypt -lm -o build/lib.freebsd-7.0-RELEASE-i386-2.7/_mysql.so
    gcc: ${LDFLAGS}: No such file or directory
    error: command 'gcc' failed with exit status 1
    where should I be looking to fix this problem?
    Try the patch from http://bugs.python.org/issue10547 or use an svn checkout.
    The patch didn't make it into 2.7.1.


    Stefan Krah
  • Robin Becker at Feb 22, 2011 at 10:18 am
    On 21/02/2011 22:46, Stefan Krah wrote:
    ........
    error: command 'gcc' failed with exit status 1
    where should I be looking to fix this problem?
    Try the patch from http://bugs.python.org/issue10547 or use an svn checkout.
    The patch didn't make it into 2.7.1.


    Stefan Krah
    well that fixes things, thanks a lot. I did google for this error message, but
    the searches were full of OS X related problems of a similar nature.
    --
    Robin Becker
  • Robin Becker at Feb 22, 2011 at 9:39 am

    On 21/02/2011 22:36, Philip Semanchuk wrote:
    ..........
    running build_ext
    building '_mysql' extension
    creating build/temp.freebsd-7.0-RELEASE-i386-2.7
    gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -Dversion_info=(1,2,2,'final',0) -D__version__=1.2.2 -I/usr/local/include/mysql -I/home/rptlab/PYTHON/include/python2.7 -c _mysql.c -o build/temp.freebsd-7.0-RELEASE-i386-2.7/_mysql.o -fno-strict-aliasing -pipe
    gcc -pthread -shared ${LDFLAGS} build/temp.freebsd-7.0-RELEASE-i386-2.7/_mysql.o -L/usr/local/lib/mysql -lmysqlclient_r -lz -lcrypt -lm -o build/lib.freebsd-7.0-RELEASE-i386-2.7/_mysql.so
    gcc: ${LDFLAGS}: No such file or directory
    error: command 'gcc' failed with exit status 1
    where should I be looking to fix this problem?
    It's been a while since I built anything on FreeBSD, but one thing that jumps out at me is that you say you're building on 8.0 but the build output you gave us mentions 7.0. That doesn't sound right at all.

    Are you using ports?
    ........
    duh, I was actually ahead of myself and the machine is indeed a 7.0 system
    --
    Robin Becker

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouppython-list @
categoriespython
postedFeb 21, '11 at 5:56p
activeFeb 22, '11 at 10:18a
posts5
users3
websitepython.org

People

Translate

site design / logo © 2023 Grokbase