headers
Jeremy C. Reed | 1 Sep 2004 07:08

installing many files in subdirectories ... and cpio

pkgsrc has use of cpio for installing files. Example:
emulators/linux-locale/Makefile
cross/i386-linuxglibc1/Makefile

I thought I saw a use of pax to install cpio files. But I don't see now.

And pax is used to extract cpio distfiles. Example:
devel/sfio/Makefile
sysutils/storage-manager/Makefile
fonts/chkfontpath/Makefile

And cpio is used to extract cpio distfiles. Example:
fonts/ko-mizi/Makefile
cross/i386-linux/Makefile

Variable CPIO does not exist.

Should we define CPIO? Should we get rid of all cpio use and just use PAX
since it supports same?

I am using for a new package (openclipart):

CPIO?=                  /usr/bin/cpio
...

        cd ${WRKSRC} && ${FIND} [a-z]* \! -name "*.png" |       \
                ${CPIO} -p ${PREFIX}/share/openclipart

Should I use cpio? Or what is the recommended way to pass through?
(Continue reading)

Permalink | Reply | 0 comments |
headers
Johnny C. Lam | 1 Sep 2004 09:39
Picon

Re: fluxbox and -funroll-loops

On Tue, Aug 31, 2004 at 10:30:12AM -0400, Jan Schaumann wrote:
> 
> I don't think that's necessary.  I don't believe that our packages
> should try to compile every package with every possible CFLAG and then
> add the necessary transforms just in case the user chooses to add that
> CFLAG manually.
> 
> <strawm?n>
> Are we going to add
> 
> BUILDLINK_TRANSFORM+=	rm:-illegal-flag
> 
> on the off chance that the user adds "-illegal-flag" to his/her CFLAGS?
> </strawman>
> 
> ,-)

Imagine this conversation:

       User: Is it okay to add -funroll-loops to my CFLAGS in
             /etc/mk.conf?
  Developer: Yeah... but some packages will break.
       User: Well, how do I know which ones?
  Developer: Well, if it breaks when you're building, you know.  Or
             sometimes we document it in the package Makefile.  Or you
             could go search the Internet for some answers.
       User: Uh... that sounds kind of time-consuming.  I was just
             hoping to make a bunch of packages overnight because it
             takes a while to build these packages.
  Developer: Oh, well... tough break, kiddo.
(Continue reading)

Permalink | Reply | 3 comments |
headers
David Brownlee | 1 Sep 2004 10:57
Picon

Re: fluxbox and -funroll-loops

On Wed, 1 Sep 2004, Johnny C. Lam wrote:

> On Tue, Aug 31, 2004 at 10:30:12AM -0400, Jan Schaumann wrote:
>>
>> I don't think that's necessary.  I don't believe that our packages
>> should try to compile every package with every possible CFLAG and then
>> add the necessary transforms just in case the user chooses to add that
>> CFLAG manually.
>>
>> <strawm?n>
>> Are we going to add
>>
>> BUILDLINK_TRANSFORM+=	rm:-illegal-flag
>>
>> on the off chance that the user adds "-illegal-flag" to his/her CFLAGS?
>> </strawman>
>>
>> ,-)
>
[...]
> Basically, I can't think of a compelling reason not to do this, since
> it's so easy to do.  I think it's worthwhile because then we're not
> basically restricting users to setting CFLAGS in /etc/mk.conf to some
> lowest common denominator of compiler optimization options across all
> packages he might wish to build.  We don't have to go out of our way
> to hunt down these bad option/package pairs, but when we notice them,
> it's rather easy to just fix it.
>
> We could probably do a better job of organizing some of this material.
> Right now, we stick all of this stuff in the package Makefiles
(Continue reading)

Permalink | Reply | 0 comments |
headers
MASUDA Hideo | 1 Sep 2004 14:46
Picon

pkgsrc on Tru64 UNIX(OSF1 V5.1)

Hi, all.

 I make a following patch of bootstrap-pkgsrc for Tru64 UNIX
including changes of mk/compiler.mk for gcc without GNU ld.
On "PKGSRC_COMPILER=compaqc gcc" in /etc/mk.conf, builtin cc
is used.

[Problems]
- Tru64 UNIX has shared library function, but shlib-handling on pkgsrc
  does not work appropriately. Now ignoring the errors is not serious.
- Tru64 UNIX has X11 based R6.3 (X server says), but directory hierarchy
  seems to be R5-like ( /usr/bin/X11, /usr/lib/X11 ... ), so X11BASE can
  not be set.
  Work around: Make directories and symbolic links as follows:
	mkdir -p /usr/X11R6 /usr/X11R6/lib /usr/X11R6/include
	ln -s /usr/bin/X11 /usr/X11R6/bin
	ln -s /usr/lib/X11 /usr/X11R6/lib/
	ln -s /usr/include/X* /usr/X11R6/include/
  But installing problem by xmkmf still unsolves.
- more problems, may be.

 Please test, comment and enhance if you have Tru64 UNIX system.

Cheers.
--
MASUDA Hideo	May the pkgsrc be with you :)

Index: bootstrap/bootstrap
===================================================================
RCS file: /cvs/cvsroot/pkgsrc/bootstrap/bootstrap,v
(Continue reading)

Permalink | Reply | 5 comments |
headers
Laurent DAVERIO | 1 Sep 2004 15:08
Picon
Favicon

Re: AIX 5.1 / pkgsrc

Hi Johnny,

> Thanks for providing the build log -- it'll be invaluable for tracking
> down compiler warnings.  I've committed some changes to some of the
> bootstrap packages that should fix the problems that you're seeing.
> Please cvs update your pkgsrc and try running the bootstrap again.

I'm happy to report that the new bootstrap script ran fine. Thank you 
for this fine job ! :-) I'm now encountering several other problems, 
which I'm tackling one after the other :

- All the packages that I want to install seem to have a dependency with 
gcc (/usr/ports/lang/gcc, not gcc3), even the "low-level" ones (gettext, 
gmake, libiconv, ...). So, I'm beginning with gcc-2.95.3. As before, I'm 
using IBM's gcc 2.95 for the job.

- gcc-2.95.3 didn't want to compile because it couldn't find 
/usr/pkg/bin/zcat. So, I created a symlink from /usr/bin/zcat to 
/usr/pkg/bin/zcat, but it didn't help. This is because the original AIX 
zcat only handles compressed (.Z), not gzipped files. Fortunately, I 
managed to find another zcat on the system, /opt/freeware/bin/zcat 
(maybe coming from IBM's collection of Linux tools ?). A new symlink 
solved the problem.

- Then it complained about a missing /usr/pkg/bin/gpatch. Again, I 
managed to find a remplacement in /opt/freeware/bin/patch, and symlink 
from it.

- Then it complained about a missing /usr/pkg/bin/gmake. (But I can't 
install gmake if I don't have gcc first...). Rather than create a
(Continue reading)

Permalink | Reply | 2 comments |
headers
Laurent DAVERIO | 1 Sep 2004 15:10
Picon
Favicon

Re: pkgsrc on Tru64 UNIX(OSF1 V5.1)

Hi,

>  I make a following patch of bootstrap-pkgsrc for Tru64 UNIX
> including changes of mk/compiler.mk for gcc without GNU ld.
> On "PKGSRC_COMPILER=compaqc gcc" in /etc/mk.conf, builtin cc
> is used.

Shouldn't this be /usr/pkg/etc/mk.conf instead of /etc/mk.conf ?

--

-- 

     Laurent DAVERIO
     Centre de Recherche en Informatique
     de l'École Nationale Supérieure des Mines de Paris (CRI-ENSMP)
     35, Rue Saint-Honoré
     77305 FONTAINEBLEAU CEDEX
     FRANCE                               Tel:    (+33|0) 1.64.69.48.37
                                          Fax:    (+33|0) 1.64.69.48.47
                                          E-mail: laurent <at> daverio.net
                                          http://daverio.net/
					 La Page Trad : http://trad.org/
Permalink | Reply | 2 comments |
headers
Jan Schaumann | 1 Sep 2004 15:27
Favicon
Gravatar

Re: fluxbox and -funroll-loops

"Johnny C. Lam" <jlam <at> NetBSD.org> wrote:
> On Tue, Aug 31, 2004 at 10:30:12AM -0400, Jan Schaumann wrote:
> > 
> > I don't think that's necessary.  I don't believe that our packages
> > should try to compile every package with every possible CFLAG and then
> > add the necessary transforms just in case the user chooses to add that
> > CFLAG manually.

[...]

> We don't have to go out of our way to hunt down these bad
> option/package pairs, but when we notice them, it's rather easy to
> just fix it.

I guess so.  It just felt like we're trying too hard to prevent the user
from shooting him/her in the foot.  This might lead to more and more
complex Makefiles.

Just a friendly warning. :-)

-Jan

--

-- 
Except most of the good bits were about frogs, I remember that.
You would not believe some of the things about frogs.
Permalink | Reply | 1 comment |
headers
Julio M. Merino Vidal | 1 Sep 2004 15:21

Re: fluxbox and -funroll-loops

On Wed, 1 Sep 2004 09:27:44 -0400
Jan Schaumann <jschauma <at> netmeister.org> wrote:

> I guess so.  It just felt like we're trying too hard to prevent the user
> from shooting him/her in the foot.  This might lead to more and more
> complex Makefiles.

Then the addition of a hacks.mk along the package sounds like a good idea,
isn't it? ;-)

Cheers

--

-- 
Julio M. Merino Vidal <jmmv <at> menta.net>
http://www.livejournal.com/users/jmmv/
The NetBSD Project - http://www.NetBSD.org/
Permalink | Reply | 0 comments |
headers
Chris Pinnock | 1 Sep 2004 15:22
Picon

Re: pkgsrc on Tru64 UNIX(OSF1 V5.1)

On Wed, Sep 01, 2004 at 03:10:31PM +0200, Laurent DAVERIO wrote:
> Hi,
> 
> > I make a following patch of bootstrap-pkgsrc for Tru64 UNIX
> >including changes of mk/compiler.mk for gcc without GNU ld.
> >On "PKGSRC_COMPILER=compaqc gcc" in /etc/mk.conf, builtin cc
> >is used.
> 
> Shouldn't this be /usr/pkg/etc/mk.conf instead of /etc/mk.conf ?

This file is for configuration options for make(1) so it sits better
in /etc.

Regards,
Chris
Permalink | Reply | 0 comments |
headers
Jeremy C. Reed | 1 Sep 2004 17:10

Re: CVS commit: pkgsrc/fonts/xorg-fontsTruetype

On Wed, 1 Sep 2004, Marc Recht wrote:

> Log Message:
> Remove the confict with vera-ttf since, even though this package installs
> the same fonts, they're installed in a different location. This allows
> the gnome meta-package to be installed with x.org's X11.

> cvs rdiff -r1.5 -r1.6 pkgsrc/fonts/xorg-fontsTruetype/Makefile

Thanks for working on this.

I think this should be done by checking the X11ROOT and/or X11ROOT_PREFIX.
Just in case, some defines their X11ROOT_PREFIX to "X11" for example.

These checks should also be done for other xorg packages too.

 Jeremy C. Reed

 	  	 	 BSD News, BSD tutorials, BSD links
	  	 	 http://www.bsdnewsletter.com/
Permalink | Reply | 0 comments |

Gmane