top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Crosscompiled native compler lack default include/lib path

+1 vote
319 views

I'm crosscompiling a native 4.7.3 compiler for ARM target, host is CentOS x86, using CROSSTOOLS-NG. It works on the ARM, but no default include path, cpp -v gives empty list and linker (ld) looks for crt1.o, etc. in current folder, no default library search path.

After reading docs, searching still don't know what is missing during build. Help is appreciated. See my build script below.

    export PATH="${PATH}:/xtbin"
    export CFLAGS="-march="armv6 -mfpu=vfp -mfloat-abi=hard"
    export CXXFLAGS="-march="armv6 -mfpu=vfp -mfloat-abi=hard"

# Configure

../gcc-4.7.3/configure 
--build=i686-pc-none 
--host=armv6l-picore-linux-gnueabi 
--target=armv6l-unknown-linux-gnueabihf 
--enable-clocale=gnu 
--enable-threads=posix 
--enable-__cxa_atexit 
--with-sysroot 
--with-gmp=/xtsysroot/usr/local 
--with-mpfr=/xtsysroot/usr/local 
--with-mpc=/xtsysroot/usr/local 
--prefix=/usr/local 
--enable-languages=c,c++ 
--with-pkgversion=piCore 
--enable-shared 
--disable-multilib 
--disable-bootstrap 
--enable-lto 
--enable-cloog-backend=isl 

# Build
make
posted Sep 1, 2013 by Jagan Mishra

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+1 vote

In place of --with-sysroot= try --with-build-sysroot=

answer Sep 2, 2013 by anonymous
Similar Questions
+1 vote

Our company make and sell some measurement system controlled by Server. There is no technical issue but we don't have enough information about license.

We will do the following,
1) We make the DVD image which include CentOS and our application.
2) Sell DVD to our customer.
3) Customer installs this image (CentOS and our applications) on the Server.

Question 1: Is there no problem from the view point of CentOS license?
Question 2: We'd like to know what we should do to CentOS community? e.g. contract, donate

Any comment...

+1 vote

I want to install path.py in my Python 3.4 environment on a Centos 5 box. My /usr/local/bin/ contains:

easy_install-3.4 
python3.4  
etc. 

We are behind a proxy server and I tried this:

# /usr/local/bin/easy_install-3.4 path.py 

Searching for path.py 
Reading https://pypi.python.org/simple/path.py/ 
Download error on https://pypi.python.org/simple/path.py/: hostname '172.29.68.1  
' doesn't match either of 'www.python.org', 'python.org', 'pypi.python.org',  
'docs.python.org', 'testpypi.python.org', 'bugs.python.org', 'wiki.python.org',  
'hg.python.org', 'mail.python.org', 'packaging.python.org', 'pythonhosted.org',  
'www.pythonhosted.org', 'test.pythonhosted.org', 'us.pycon.org', 'id.python.org' --  
Some packages may not be found! 

Couldn't find index page for 'path.py' (maybe misspelled?), Am I best to use pip or easy_install? also if easy_install, how can I fix the above error?

+1 vote

Apache/Tomcat (by default) does not allow symbolic linking (nice as it can cross mounted file systems) except in the top apache/lib directory. I use hard links in the Application/WEB-INF/lib directories to reduce copying and help me manage things.

HOWEVER, some applications have special needs - e.g. pictures. You don't want to always distribute these with the release of the application (Application.war file), so symbolic links are the way to go (except for MS land, sorry). The nice solution to this is:

.../webapps/Application/WEB-INF/context.xml
which must contain at least the two below lines:

However this allows ALL symbolic linking in the Application directory. I agree with the developers that this is dangerous.

Is there some way to allow linking in just ONE sub-directory of the Application?
- e.g. .../webapps/Application/images

This would allow all I need to have local images for the application without endangering other things using a symbolic link.

+1 vote

My code compiles even without inclusion of stdio.h, any suggestion on best practices?

...