cross compliation --host=armle-unknown-linux --target=armle-unknown-linux fails due to "error: cannot check for file existence when cross compiling"

Bug #1326035 reported by Karl-Philipp Richter
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Miredo
Fix Released
Low
Rémi Denis-Courmont

Bug Description

Compilation with
<code>
git clone git://git.remlab.net/miredo.git; cd miredo
git checkout <1.2.4/1.2.5/1.2.6>
libtoolize
./autogen.sh
env CC=/usr/local/arm-marvell-linux-gnueabi/bin/arm-marvell-linux-gnueabi-gcc LD=/usr/local/arm-marvell-linux-gnueabi/bin/arm-marvell-linux-gnueabi-ld RANLIB=/usr/local/arm-marvell-linux-gnueabi/bin/arm-marvell-linux-gnueabi-ranlib CFLAGS="-I/usr/local/arm-marvell-linux-gnueabi/arm-marvell-linux-gnueabi/libc/include -mhard-float -mfpu=vfpv3-d16" LDFLAGS="-L/usr/local/arm-marvell-linux-gnueabi/arm-marvell-linux-gnueabi/libc/lib" ./configure --host=armle-unknown-linux --target=armle-unknown-linux --build=i686-pc-linux --prefix=/usr/local # as recommended in the http://usdl.synology.com/download/ds/userguide/Synology_DiskStation_Manager_3rd_Party_Apps_Developer_Guide.pdf
</code>
fails with due to <code>
configure: error: cannot check for file existence when cross compiling
</code> when checking for /proc/self/maps

Output of command sequence and config.log attached

Revision history for this message
Karl-Philipp Richter (krichter722) wrote :
Revision history for this message
Karl-Philipp Richter (krichter722) wrote :
Revision history for this message
Rémi Denis-Courmont (rdenis) wrote :

You need --disable-binreloc to cross-compile versions 1.2.x. This was already fixed in HEAD for a while.

Changed in miredo:
assignee: nobody → Rémi Denis-Courmont (rdenis)
importance: Undecided → Low
milestone: none → 1.3.0
status: New → Fix Released
Revision history for this message
Karl-Philipp Richter (krichter722) wrote :

If this is causes by a specific missing option, I guess it would make sense to improve the output, then telling everybody directly the thing you just told here :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.