Bug 1675 - GMP Error during buildroot make process
Summary: GMP Error during buildroot make process
Status: RESOLVED WORKSFORME
Alias: None
Product: buildroot
Classification: Unclassified
Component: Other (show other bugs)
Version: 2010.02
Hardware: PC Linux
: P5 blocker
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-01 11:31 UTC by Sameer
Modified: 2010-07-27 22:11 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:


Attachments
configuration files (56.50 KB, application/x-gzip)
2010-05-02 20:08 UTC, Sameer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sameer 2010-05-01 11:31:20 UTC
Hi,

I am trying to build the Linux Kernel 2.6 for i386 core 2.

I gave make command after configuration and during the process of gmp following error came:


configure: WARNING: you should use --build, --host, --target
configure: WARNING: you should use --build, --host, --target
configure: error: --target is not appropriate for GMP
Use --build=CPU-VENDOR-OS if you need to specify your CPU and/or system
explicitly.  Use --host if cross-compiling (see "Installing GMP" in the
manual for more on this).
make: *** [/home/Sameer/buildroot-2010.02/output/toolchain/gmp-4.2.4-host/.configured] Error 1




Please tell me how to work around...
Comment 1 Thomas Petazzoni 2010-05-01 13:24:15 UTC
Could you please attach your Buildroot .config file so that we could reproduce ?
Comment 2 Sameer 2010-05-02 20:08:19 UTC
Created attachment 1615 [details]
configuration files
Comment 3 Thomas Petazzoni 2010-05-21 13:04:58 UTC
Sorry but the tarball that you attached does not contain your own configuration. Your own configuration is available as the file ".config" in the main directory of the Buildroot sources.
Comment 4 Thomas Petazzoni 2010-07-27 22:11:10 UTC
Building GMP for the host is something that happens every time someone builds a toolchain with Buildroot, so it's something that works, at least in the common configurations that we test. Since the bug was reported more than two months ago, the reporter hasn't posted the Buildroot configuration, so we have no way of reproducing the issue.

Therefore, let's mark it as WORKSFORME. Sameer, if you can still reproduce the issue, please reopen the bug and attach your Buildroot configuration.