missing standard functions

[GoogleCodeExporter]

What steps will reproduce the problem?
1. open the terminal
2. super user
3. extract the file
4. go into the src folder
5. run ./configure in the terminal

What is the expected output? 
Checking for malloc… no
Configure: error: “missing standard functions”

What do you see instead?
Checking for malloc… yes

What version of the product are you using? On what operating system?
libmpsse-1.2-1, fedora 16

Please provide any additional information below.
I had installed the glibc and also the gcc.

Original issue reported on code.google.com by GeraldGo...@gmail.com on 26 Dec 2012 at 8:41

[GoogleCodeExporter]

correction!

What is the expected output? 
Checking for malloc… yes

What do you see instead?
Checking for malloc… no
Configure: error: “missing standard functions”

Original comment by GeraldGo...@gmail.com on 26 Dec 2012 at 8:45

[GoogleCodeExporter]

Have you done a yum groupinstall "Development Tools"?

Original comment by heffne...@gmail.com on 28 Dec 2012 at 3:57

[GoogleCodeExporter]

Nothing heard from original poster, could not duplicate.

Original comment by heffne...@gmail.com on 28 Jan 2013 at 6:39

• Changed state: WontFix

[GoogleCodeExporter]

same thing:

root@debian:~/i2c/libmpsse-1.2/src# ./configure
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for size_t... yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for malloc... no
configure: error: "missing standard functions"

Original comment by tmus...@gmail.com on 12 Feb 2013 at 3:33

[GoogleCodeExporter]

I get this error too. Perhaps the answer is in the "config.log" file. Here is a 
fragment:

configure:3423: gcc -o conftest -Wall -fPIC -fno-strict-aliasing -g -O2  -lftdi 
 conftest.c  >&5
conftest.c:44:6: warning: conflicting types for built-in function 'malloc' 
[enabled by default]
/usr/bin/ld.bfd.real: cannot find -lftdi
collect2: error: ld returned 1 exit status

I'm in no way an autotools expert, but it seems that configure cannot find 
libftdi. I installed libftdi from source (as many others, i presume), and it 
went installed into /usr/local/lib. Perhaps configure isn't looking there?

Orestes.

Original comment by masores...@gmail.com on 18 Feb 2013 at 9:03

[GoogleCodeExporter]

Well configure is invoking gcc and it's gcc that can't find libftdi; most 
likely, /usr/local/lib is not in your list of library paths. You may need to 
add it to /etc/ld.so.conf (and then run the ldconfig command to update the 
cache).

Original comment by heffne...@gmail.com on 18 Feb 2013 at 12:23

[GoogleCodeExporter]

Hello,

First of all, thanks for your work on libmpsse, and your fast response!

I'm aware of all ldconfig stuff, and I checked it before my posting. I have the 
/usr/local/lib correctly set in /etc/ld.so.conf.d/libc.conf (there's an 
"include /etc/ld.so.conf.d/*.conf" line in /etc/ld.so.conf)

Also, "ldconfig -v |grep ftdi" yelds:
        libftdi1.so.2 -> libftdi1.so.2.0.0
        libftdipp1.so.2 -> libftdipp1.so.2.0.0

So it seems ldconfig is correctly caching libftdi. The problem must be in other 
place.

I get the same error in a debian wheezy and in a (k)ubuntu quantal.

Any help or suggestion?

Original comment by masores...@gmail.com on 18 Feb 2013 at 2:49

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Another thing: I see in SVN that in revision r133 you updated the configure 
script to search for ftdi.h in /usr/include/libftdi/ instead of /usr/include 
(this resolved the  issue #20 )

but in my two systems libftdi installed its headers into 
/usr/local/include/libftdi1 (with a trailing "1"), so this may be the error...

Original comment by masores...@gmail.com on 18 Feb 2013 at 3:02

[GoogleCodeExporter]

Confirmed: the problem is in the trailing "1". I've temporarily worked around 
the problem by:

1) Defining additional symlinks (as root)
   ln -s /usr/local/lib/libftdi1.so.2 /usr/local/lib/libftdi.so
   ln -s /usr/local/lib/libftdipp1.so.2 /usr/local/lib/libftdipp.so
2) Invoking configure with "CFLAGS=-I/usr/local/include/libftdi1 ./configure"

With this, configuration, compilatio and installation was successful

Original comment by masores...@gmail.com on 18 Feb 2013 at 3:29

Attachments:

• config.log

[GoogleCodeExporter]

Ah, got it, thanks! I just checked in a patch to the trunk that fixes this; it 
compiled and ran against libftdi1 successfully so you shouldn't need those work 
arounds anymore.

Original comment by heffne...@gmail.com on 18 Feb 2013 at 6:15

• Changed state: Fixed