Title: Fwd: RE: [Sisuite-devel] Building on Red Hat
Brian, does your Red Hat server have access to the SVN tree and that's where you're building from?  Or did you create a tarball on a Debian server and then try to build it on the Red Hat server?
 
I have never encountered your problem before, as I always run 'make source_tarball' and build on Red Hat systems.  In fact what I usually do is just 'make source_tarball', copy the tarball to the target build system, then execute 'rpmbuild -ta systemimager-<version>.tar.bz2'.
 
BTW, I don't think it's necessary to create an empty config.inc, my RPM builds always have that error message and it builds successfully, see the following snippet of my build on x86_64:
 
+ make -j11 get_source
Makefile:107: config.inc: No such file or directory
./configure
checking for g++... g++
checking for C++ compiler default output file name... a.out
checking whether the C++ compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
 
Cheers,
 
Bernard


From: [EMAIL PROTECTED] on behalf of Brian Elliott Finley
Sent: Mon 27/03/2006 22:52
To: Sisuite-Dev
Subject: Fwd: RE: [Sisuite-devel] Building on Red Hat

----- Forwarded message from Jerry DeLapp <[EMAIL PROTECTED]> -----

Date: Sun, 26 Mar 2006 15:40:17 -0700
From: Jerry DeLapp <[EMAIL PROTECTED]>
To: 'Brian Elliott Finley' <[EMAIL PROTECTED]>
Subject: RE: [Sisuite-devel] Building on Red Hat

No problem.

-----Original Message-----
From: Brian Elliott Finley [mailto:[EMAIL PROTECTED]] On Behalf Of Brian
Elliott Finley
Sent: Saturday, March 25, 2006 7:40 PM
To: Jerry DeLapp
Subject: Re: [Sisuite-devel] Building on Red Hat

Thanks, Jerry,

Mind if I forward this to the list?

-Brian


Thus spake Jerry DeLapp ([EMAIL PROTECTED]):
>When I was beating my head against 3.4.x builds, this sort of error message
was almost always caused by a delta between SI source tarballs and installed
development packages.  That is, source configure scripts quite often
mistakenly go out and grab bits from the host system distro, even when you
try and tell it to use the SI source trees.  I found it more useful to
*remove* -devel packages from the build host in order to better detect the
myriad number of places this was happening.  Since SI uses source for
everything in the boot image, I think that a "discovery" that you need to
add a -devel package which is the same as a source tarball indicates that
you are going outside the build tree for something.
>
>In this case, however, I think the big problem is the first error message.
I got this sort of foo until I created an empty config.inc file.
>
>-----Original Message-----
>>From: Brian Elliott Finley <[EMAIL PROTECTED]>
>>Sent: Mar 24, 2006 10:21 AM
>>To: Sisuite-Dev <sisuite-devel@lists.sourceforge.net>
>>Subject: [Sisuite-devel] Building on Red Hat
>>
>>So,
>>
>>After a nice long hiatus, I once again have a Red Hat build system
>>installed in my lab.  I'd like to use it to be sure that things build
>>properly on Red Hat as well as on Debian/Ubuntu, where I do my primary
>>development.
>>
>>And, as many of you do SystemImager builds on Red Hat machines, rather
>>than try and re-solve problems that I run into, I'm going to post them
>>here, expecting that one of you will have already solved them.
>>
>>As such, I've encountered my first problem, and Bernard pointed out what
>>is at least a partial solution:  build dependencies.  I got them from
>>the BuildRequires bit in the spec file, and have installed them all.
>>
>>I am now getting the following, which is hopefully just a missing build
>>requirement.  This is an old ia64 box running RHEL 4 ES:
>>
>>    $ make
>>    Makefile:107: config.inc: No such file or directory
>>    ./configure
>>    checking for g++... no
>>    checking for c++... no
>>    checking for gpp... no
>>    checking for aCC... no
>>    checking for CC... no
>>    checking for cxx... no
>>    checking for cc++... no
>>    checking for cl... no
>>    checking for FCC... no
>>    checking for KCC... no
>>    checking for RCC... no
>>    checking for xlC_r... no
>>    checking for xlC... no
>>    checking for C++ compiler default output file name... configure:
>>    error: C++ compiler cannot create executables
>>    See `config.log' for more details.
>>    make: *** [config.inc] Error 77
>>
>>
>>
>>--
>>Brian Elliott Finley
>>Mobile:  630.631.6621
>>
>>
>>-------------------------------------------------------
>>This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
>>that extends applications into web and mobile media. Attend the live
webcast
>>and join the prime developer group breaking into this new coding
territory!
>>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>>_______________________________________________
>>Sisuite-devel mailing list
>>Sisuite-devel@lists.sourceforge.net
>>https://lists.sourceforge.net/lists/listinfo/sisuite-devel
>

--
Brian Elliott Finley
Mobile:  630.631.6621



----- End forwarded message -----

--
Brian Elliott Finley
Mobile:  630.631.6621


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Sisuite-devel mailing list
Sisuite-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

Reply via email to