RPM targets

[Michael Bletzinger]

Hello,
Is anyone working on creating rpm targets similar to "make dist". I was
thinking that automake could for example generate the spec file from a
template.

Michael

Re: RPM targets

[Tom Tromey]

> "Michael" == Michael Bletzinger <[EMAIL PROTECTED]> writes:

Michael> Is anyone working on creating rpm targets similar to "make
Michael> dist". I was thinking that automake could for example
Michael> generate the spec file from a template.

I occasionally hear about people wanting this, but I don't recall
seeing any implementation.

Tom

Re: RPM targets

[Michael T. Babcock]

I was just about to compose that message today myself.

project.spec.am/in ...

All I want is to be able to "make i386.rpm; make i686.rpm"

Michael Bletzinger wrote:

> Is anyone working on creating rpm targets similar to "make dist". I was
> thinking that automake could for example generate the spec file from a
> template.

--
   _/~-=##=-~\_
   -=+0+=-< Michael T. Babcock >-=+0+=-
   ~\_-=##=-_/~
http://www.linuxsupportline.com/~pgp/ ICQ: 4835018

Re: Automake with different compilers

[Erik Mouw]

On Sat, 04 Mar 2000 23:16:09 +0200 (SAST), Carl van Schaik wrote:
> Also, there any way to get automake to compile a .c file to .o and not
> make a library or program out of it?
> I'm doing some cross-compiling stuff that only seems to work if I compile
> files to .o and use the linker to create a binary... this is a pain in
> automake ...
> 
> ie. what I do at the moment
> 
> - Makefile.am -
> all: led_blink.c
> $(CC) -Wall -DAT91M40400 -I$(top_srcdir)/src/include \
> -c $(srcdir)/led_blink.c -o led_blink.o; \
> $(LD) -Ttext 0x2018000 -e 0x2018000 -o led_blink.bin \
> ../../library/init/lib32/in_main.o led_blink.o \
> ../../library/init/lib32/in_eb01.o \
> ../../library/init/lib32/in_reset.o \
> ../../angel-lib/libangel.arm \
> ../../library/lib32/lib32.arm \
> $(prefix)/arm-AT91-elf/lib/libc.a \
> $(prefix)/lib/gcc-lib/arm-AT91-elf/2.95.2/libgcc.a

This is quite a complicated way of getting things compiled. It can be done
much easier by just passing the correct flags to gcc. I wrote a bootloader
for our StrongARM SA1100 board (see .signature for more info) using
autoconf+automake. Here is my Makefile.am (slightly edited): 

 Makefile.am 
bin_PROGRAMS = blob-elf32 blob

blob_elf32_SOURCES = start.S command.c main.c flash.c serial.c time.c \
util.c uucodec.c 

blob_SOURCES = 

EXTRA_DIST = ld-script

blob_elf32_LDFLAGS += -Wl,-T,ld-script

BLOB_elf32_LDADD = -lgcc

blob: blob-elf32
$(OBJCOPY) $(OCFLAGS) $< $@
 Makefile.am 

In short, this Makefile.am first builds an elf32 "binary", and then uses
objcopy to create a "real" (i.e., without ELF info) binary image. The key
trick is to hide the linker details in a linker script which you just pass
to gcc (and the configure script also sets some compiler flags). Have a
look at BLOB[1] the bootloader at:

  http://www-ict.its.tudelft.nl/~erik/open-source/blob/

If you have a gcc cross compiler to armv4l-unknown-linux, you should be
able to compile BLOB straight out of the box.


Erik

[1] Boot Loader OBject

-- 
LART. 250 MIPS under one Watt.
http://www-ict.its.tudelft.nl/~erik/open-source/LART/

Re: RPM targets

[Hans Ulrich Niedermann]

Michael Bletzinger <[EMAIL PROTECTED]> writes:

>   Is anyone working on creating rpm targets similar to "make dist". I was
> thinking that automake could for example generate the spec file from a
> template.

I've implemented "make rpm" in my experimental automake-based
package called "xtestsuite". It was more intended for myself to
somehow get into the the automake/autoconf thing so the C/C++ sources
are not very interesting.

However, the "make rpm" feature seems to work quite well - it even
lets you build RPM and SRPM packages without being root or modifying
the user's ~/.rpmrc file.

The packaging macros use the PKG_ prefix. If someone wants to improve
my macros and scripts and transform it into a generic
automake/autoconf macro collection for packaging I'd be happy to
assist.

Please note that the some of the programs contained in the package
require SDL (Simple Direct Media Layer
) so if you don't have that,
you will have to comment out some lines. Also note that I only have
only tested and used this package on Intel-based maschines running
Redhat Linux so far.

You can get the package from

   

If you still have questions, don't hesitate to contact me via personal
mail or on the automake or autoconf lists if on-topic.

Cheers,

Uli

Re: tar command executed during make dist

[Olly Betts]

In article <[EMAIL PROTECTED]>, Tom Tromey wrote:
>> "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes:
>Lars> Any point in using the f flag at all in such cases?
>Lars> => $(TAR) cho $(distdir) | $(GZIP) -c > $(distdir).tar.gz   
>
>I thought some versions of tar defaulted to something like /dev/rmt8
>(or some other equally obscure device).  It's hard to remember.

Indeed, I've also encountered such versions of tar.

Also note that with GNU tar, `tar --help' says:

  "*This* `tar' defaults to `-f- -b20'."

Note the stress on the word `This'.

Cheers,
Olly